search

enonic / xp-apps

Enonic XP bundled applications.
GNU General Public License v3.0
1 stars 3 forks source link

Implement a setting in config file of Content Studio to switch HtmlArea to CKEditor #743

Closed alansemenov closed 6 years ago

alansemenov commented 6 years ago

@alansemenov commented on Wed Mar 28 2018

We need to have a transition phase during which we will support both TinyMCE and CKEditor. This will allow users to a) test the new editor and b) try switching their content types from one to another and see how that works out.

To do that we will implement a new setting in the config file of Content Studio (com.enonic.xp.contentstudio.cfg):

htmlarea=ckeditor

When this setting is present in the file with this value, we will use CKEditor instead of TinyMCE in the HtmlArea.

We can pass value of the config setting from the controller via CONFIG object, like we do with tourDisabled setting in app-admin-home.

@sigdestad commented on Wed Mar 28 2018

Hmm.. could we try using a property to switch instead? Then we can test all of our existing content types and data?

@alansemenov commented on Thu Mar 29 2018

Good idea, let's do this via config property of HtmlArea input type:

<config>
  <new>true</new>
</config>

@ashklianko commented on Thu Mar 29 2018

Ok, will update

@sigdestad commented on Fri Mar 30 2018

Still not a good solution, then we need to modify apps. I was thinking of a config file i.e. com.enonic.xp.contentstudio.cfg htmlarea=ckeditor

@alansemenov commented on Fri Mar 30 2018

Not sure if that’s a good idea - will make it impossible to test both editors side by side with the same content

@sigdestad commented on Fri Mar 30 2018

Do we need that? Much more important to be able to test it at scale... We could even let partners test it with this property, and say it is beta mode.