Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I realize that FCKEditor support w/ WYSIWYG is still immature and buggy. From this thread (http://drupal.org/node/414686), it looks like this used to work and I cannot figure out how to fix it. Same problem description.
How to get this:
<p>Text here</p><ul><li>Bullet 1</li><li>Bullet 2</li></ul>
to look like this when directly editing HTML source:
<p>
Text here
</p>
<ul>
<li>
Bullet 1
</li>
<li>
Bullet 2
</li>
</ul>
I've tried various combination of input filter formatting options, WYSIWYG configuration options, etc. TinyMCE works with no problems. Has anyone run across this and can point me in the right direction?
Comment | File | Size | Author |
---|---|---|---|
#3 | wysiwyg-HEAD.fck-dataprocessor2.patch | 2.56 KB | TwoD |
#2 | wysiwyg-HEAD.fck-dataprocessor.patch | 4.94 KB | sun |
Comments
Comment #1
stacysimpson CreditAttribution: stacysimpson commentedOh yeah, FCK2.6.4
Comment #2
sunThis seems to happen, because we wrap/replace the original DataProcessor with a custom one. Commenting out the line where it overrides the original makes it work again.
Played around with this a bit and tried to invoke the original DataProcessor in a few other ways, also tried to just alter the original one, but all without luck. Latest approach leads to other JS errors.
uhm, to summarize: It looks like the original DataProcessor does no longer get the configuration values passed, so the configuration settings don't apply at all.
Attaching my mess of a patch, only for reference.
Comment #3
TwoDLooks like I had missed a couple of function arguments.
Comment #4
sunWorks as advertised. Fixed a tiny coding-style glitch and also removed that setting for 'preformatted', since I couldn't find an equivalent in FCKeditor's docs.
Thanks for reporting, reviewing, and testing! Committed to all branches.
A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.
Comment #6
ron_s CreditAttribution: ron_s commentedJust curious, I tried to apply this patch to 5.x-2.0 and did not seem to work. I cleared all the cache, removed all previous WYSIWYG profiles, and tried to re-apply but no success.
I also downloaded 5.x-2.x-dev since I know this patch was applied to it, and I can't even get the development version operational. Whenever I attempt to add a new WYSIWYG profile using 5.x-2.x-dev, I get a blank white page (no formatting, nothing). Using FCKeditor 2.6.4.1.
Comment #7
MissyM CreditAttribution: MissyM commentedI can't get this working using the latest dev version and Dru 6 either.
Subscribe.
Comment #8
TwoDron_s, any errors when patching 2.0? If you get white-pages with 2.x-dev please check your PHP logs for errors and report that in a new issue if it persists.
MissyM, I just tested the 6.x-2.x-dev version on two sites and the source gets formatted in FF with FCKeditor 2.6.4.1.
Please look through the FAQ (linked from project page) and, if you can, try debugging to see if the formatting options get included in the settings sent from the server via Drupal.settings.wysiwyg.configs.fckeditor. If there are still problems, please re-open this issue.