Closed (won't fix)
Project:
CKEditor 4 - WYSIWYG HTML editor
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 Mar 2010 at 03:38 UTC
Updated:
30 Sep 2010 at 07:49 UTC
Actually CKEditor use a big and complicated exclude mode rules to disabling/enabling. So CKEditor can be automatically enabled on the admin and add html balise in textarea used for configuration.
This is really a problem on collapse field or empty field (CKEditor can add a "p" html tags) and no html field...
This is critical because with any change from the user but only save settings or node CKeditor change the content.
I propose to change to include mode with this rule:
node/*.edit-body
Comments
Comment #1
wwalc commentedComment #2
gagarine commentedDefault settings need to be right and safe. I think if a module destroy data is not a feature request... and is easy to fix.
to be clear: your content is "tada" after saving with no change is "< p >tada< / p >". Than can break you design if it's the settings for the footer message.
Comment #3
gagarine commentedComment #4
jcisio commented#2 if you don't want it, simple switch to the plaintext mode, then later add the exception in the settings page.
That said, I think that it need an option for that.
Comment #5
gagarine commentedI mean in admin/settings/ckeditor/editg
Comment #6
jcisio commentedOh sorry, I didn't see that the Include/Exclude mode is already availble. So the new title doesn't make any sense.
I leave it for the maintainers to decide. However, I don't understand why it makes trouble, because anything in the admin page will be disabled be default (the first exclude rule is "admin/*"). And by default, too, there is a textlink below the editor to turn it on/off.
Comment #7
dczepierga commentedI don't uderstand why it makes trouble too... So i don't think we change it.