Edit administrator/components/com_content/models/forms/article.xml, replace the "metakey" field from
<field name="metakey" type="textarea"
label="JFIELD_META_KEYWORDS_LABEL" description="JFIELD_META_KEYWORDS_DESC"
rows="3" cols="30" />
to
<field name="metakey" type="editor"
label="JFIELD_META_KEYWORDS_LABEL" description="JFIELD_META_KEYWORDS_DESC"
filter="JComponentHelper::filterText" buttons="true" />
Try to insert an image in "Meta Keywords" field or article content field, the image popup is not closed after you click "Insert" button. If you check in browser's developer tool, there is an error , for Chrome it is "Uncaught RangeError: Maximum call stack size exceeded", for Firefox it is "too much recursion", the code causes this problem is
jModalClose = function() {
oldClose.apply(this, arguments);
tinyMCE.activeEditor.windowManager.close();
};
Image is inserted into TinyMCE editor and the image popup is closed, no matter how many TinyMCE editors are available on the page.
Image is inserted successfully but image popup is not closed.
@tranduyhung was the cursor set to the editor in position metakey (did you click inside the editor, before clicking the insert button) ?
This might happen with current code if the editor is not set as active and there are more than one instances (I can figure out that by reading the code above). There might be an easy solution for that, will check it this weekend
@brianteeman This problem doesn't exist in 3.5.x or older 3.x releases.
@dgt41 Yes the cursor was in the editor and the image was inserted at the cursor's position successfully. the only problem was the image popup was not closed after image was inserted into editor.
Labels |
Added:
?
|
Category | ⇒ | Fields |
This issue still exists in RC. My only solution for now is switching to another editor like JCE.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-07-07 21:20:36 |
Closed_By | ⇒ | dgt41 |
Set to "closed" on behalf of @dgt41 by The JTracker Application at issues.joomla.org/joomla-cms/10774
Is this new in 3.6 or did this problem exit before?
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/10774.