Open BobRay opened 12 years ago
A number of users reported this and I can now confirm it.
In NewsPublisher, with multiple richtext textareas (all with class="modx-richtext"), only the first one gets the editor.
I did not see this until the 2.2-compatible version, but other users reported it with earlier versions.
The easiest way to reproduce it is with this NewsPublisher tag:
[[!NewsPublisher? &initrte=1 &rtcontent=1 &rtsummary=1 &show=pagetitle,introtext,content ]]
1
pagetitle,introtext,content
Only the introtext field will get the editor. If you reverse 'introtext' and 'content' in the &show property, the content field will get the editor.
It works fine for me with TinyMCE 4.3.0 in MODX 2.1.5. Fails with TinyMCE 4.3.1 in MODX 2.2.0.
It may be related to this change (or not) in September (sorry, I don't know the which commit):
if not 'mode' in mce_config: mce_config['mode'] = 'exact' if mce_config['mode'] == 'exact': mce_config['elements'] = final_attrs['id']
A number of users reported this and I can now confirm it.
In NewsPublisher, with multiple richtext textareas (all with class="modx-richtext"), only the first one gets the editor.
I did not see this until the 2.2-compatible version, but other users reported it with earlier versions.
The easiest way to reproduce it is with this NewsPublisher tag:
[[!NewsPublisher? &initrte=
1
&rtcontent=1
&rtsummary=1
&show=pagetitle,introtext,content
]]Only the introtext field will get the editor. If you reverse 'introtext' and 'content' in the &show property, the content field will get the editor.
It works fine for me with TinyMCE 4.3.0 in MODX 2.1.5. Fails with TinyMCE 4.3.1 in MODX 2.2.0.
It may be related to this change (or not) in September (sorry, I don't know the which commit):
if not 'mode' in mce_config: mce_config['mode'] = 'exact' if mce_config['mode'] == 'exact': mce_config['elements'] = final_attrs['id']