You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 10, 2023. It is now read-only.
The workaround proposed on trac works (and used in production in some of my websites as an upgradeStep
that manually sets json TinyMCE options to css classes (http://www.tinymce.com/wiki.php/Configuration:formats)), but I think that having an option in control panel of activating strikethrough (and underline) of TinyMCE's editor and not working is a bug (actually, any of TinyMCE options that can be activated in the user's interface that doesn't work is a bug to me). The workaround should somehow be integrated in a new release of Products.TinyMCE IMHO.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is related to plone/Products.CMFPlone#331 (before Issues was activated in Products.TinyMCE) and http://web.archive.org/web/20131025234758/https://dev.plone.org/ticket/13715.
The workaround proposed on trac works (and used in production in some of my websites as an upgradeStep
that manually sets json TinyMCE options to css classes (http://www.tinymce.com/wiki.php/Configuration:formats)), but I think that having an option in control panel of activating strikethrough (and underline) of TinyMCE's editor and not working is a bug (actually, any of TinyMCE options that can be activated in the user's interface that doesn't work is a bug to me). The workaround should somehow be integrated in a new release of Products.TinyMCE IMHO.
The text was updated successfully, but these errors were encountered: