TinyMCE in Plone 6

[janet.dura (Janet Durà Pipó)]

We are in the process of migrating about 500 websites made on a plone 4.2 platform to another in plone 6.0.2. We want to focus on improving the experience with the user edition and we have the following doubts regarding the tinyMCE that is already integrated in the core of Plone 6.0.2:

• Why are unnecessary tags added, such as the tag, when adding a

  paragraph. We have seen that TinyMCE does not, but Plone does?

• How to translate the literals of the new styles titles that we added in the configuration of tinymce @@tinymce-controlpanel. In Plone 4 you could create a file plone.tinymce.po with the translations, but this doesn't work anymore

• We have seen that there is a paid version of TinyMCE that incorporates features and plugins that interest us a lot, related to accessibility among others, but we do not know if we could include this version instead of or in addition to the core one and also add payment extensions like

TinyMCE | Accessibility Checker plugin

Tinymce Bootstrap Plugin Bootstrap 5 Demo

• We also wonder if we could keep the plonelink and ploneimage plugins? We have seen that the plonelink and ploneimage are currently integrated and configured in the context menu, but right-clicking does not show their icons to use these features. /Products/CMFPlone/patterns/tinymce.py

Thank you!

[stevepiercy]

I don't know anything about the TinyMCE issues. However please see the Plone Upgrade Guide. Perhaps there is something in there?

[janet.dura (Janet Durà Pipó)]

We will do it. Thank you!

[thet (Johannes Raggam)]

@janet.dura there is yet no upgrade guide for TinyMCE for Plone 6. But I‌ started one:

TinyMCE upgrade to Plone 6, Pt. 1.

Regarding your questions:

• Can you give an example where TinyMCE adds unnecessary tags and how that differs from Plone 4?

• The TinyMCE controlpanels are now defined plone.base, e.g.: plone.base/controlpanel.py at main · plone/plone.base · GitHub
  You can see the gettext message ids, which are already the english translations.
  The translations are defined in: plone.app.locales
  E.g.: plone.app.locales/plone.po at master · collective/plone.app.locales · GitHub
  You should be able to override them. Just make sure your custom .po file is loaded before the default one.
  Also see: Translating text strings — Plone Documentation v5.2

• For the custom plugins, are they TinyMCE 5 or 6 plugins? In Plone 6.0 we ship TinyMCE 5 but there are discussions to update to TinyMCE 6 for future Plone versions.
  However, you should be able to provide custom plugins. Make them available via a browser resource directory and add those plugins to the TinyMCE configuration. Here is an example registry.xml snippet:

  <records interface="Products.CMFPlone.interfaces.controlpanel.ITinyMCESchema"
           prefix="plone">
    <value key="custom_plugins" purge="False">
      <element>exampleplugin|++plone++my.site/example-plugin/plugin.js</element>
    </value>
  </records>