Closed (fixed)
Project:
Wysiwyg
Version:
6.x-2.0
Component:
Editor - FCKeditor
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
23 Nov 2009 at 15:16 UTC
Updated:
7 Dec 2009 at 20:20 UTC
I just discovered that for some reason new nodes with Filtered HTML content are saving & displaying the HTML editor tags, instead of the rendered HTML tags. So, my content ends up looking like:
This is a [b]test[/b].
The content displays fine if I edit it and change to Full HTML type. The content also displays correctly in the editor box, but I can see in the database that its saving as [b] instead of . I have WSYIWYG w/ FCK installed, but it was all working not long ago. I dont think I changed anything other than installing Mollom, of which I disabled to test this without success. Anyone have any ideas what might be wrong?
Comments
Comment #1
twodPlease disable the BBCode plugin for your editor profiles, or enable a BBCode interpreting filter for your input formats.
This is explained in the FAQ entry: When looking at the source code of the final page, I see tags like [img]...[/img] or [color=#123456]...[/color] instead of the expected HTML
Comment #2
hornetnz commentedWell, that would make sense...but I dont have the BBCode module installed. Content creation with FCK worked fine when I installed it (as far as I remember), which makes me wonder why I would have to add a bbcode filter now. Obviously, something changed...I just dont know what =/.
Doesnt WYSIWYG/FCK create/handle the bbcodes it generates on its own? If not, I'm not finding a bbcode input filter, only the module.
Comment #3
hornetnz commentedI found a BBcode checkbox in the filtered html buttons & plugins section. TOTALLY overlooked it the other 5 times I was on that page.
Comment #4
twodRead the FAQ entry and my post again. Since you do not have a BBCode module (which provides a BBCode filter), you need to disable the BBCode plugin on the editor profile.
If you did intend to store BBCode rather than regular tags in the DB, you should have enabled a BBCode filter provided by some otheer module module instead. I only mentioned that to show how FCKeditor's plugin is intended to be used, ie with a 3rd party tool/module written to run on your CMS, which in our case could be the BBCode.module.
Wysiwyg module does not do anything to your rendered node, it only takes care of loading the clientside editor along with any enabled plugins. If the editor has a BBCode plugin - which FCKeditor does - and it's enabled it will only make the editor itself output BBCode instead of regular tags. If you disable the editor while editing your node (Disable rich editing toggle-link or switch to another format without an editor), you will see the exact contents which get submitted to the server. No editor plugin can change what happens to it after it has been submitted, only the filters do that. If FCKeditor or Wysiwyg module would handle the display of the BBCode itself, they would indeed need to implement a Drupal input filter, which is out of the scope for both the Wysiwyg module and the FCKeditor library.