Closed (fixed)
Project:
Wysiwyg
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
3 Nov 2008 at 10:28 UTC
Updated:
17 Nov 2008 at 21:22 UTC
Jump to comment: Most recent file
Comments
Comment #1
sunTrue. Attached patch should fix this issue.
Comment #2
smartinm commentedHi Sun,
this patch works only when input format has "Formatting guidelines". If no guidelines are available, the editor is not loaded yet.
Comment #3
sunWell, I'll look into fixing this. However, having one input format without any formatting guidelines indicates that there are no input filters for the default input format. This would equal to allowing Full HTML for anonymous users, which opens a can of worms on your site. You might want to reconsider your input format configuration. Read on here:
http://heine.familiedeelstra.com/input-formats-beware
http://www.nicklewis.org/drupal-news/why-full-html-input-format-dangerous
http://www.lullabot.com/articles/drupal_input_formats_and_filters
Comment #4
sunAttached patch should fix this edge-case. I already thought of outputting a warning message when this happens, but did not implement this yet.
Comment #5
smartinm commentedThanks sun.
I know the problems of allowing Full HTML for anonymous users, but there are some cases where only one rich text input is enabled when edit a node:
(Sorry my bad english)
Comment #6
sunThanks, committed.
I did not know of filterbynodetype module yet. After quickly scanning its code, I can tell you that it breaks Wysiwyg API, because it alters the input format widget in a way that leads to a form structure that differs from the one produced by filter_form(). Wysiwyg, however, requires that the internal form structure of the input format widget equals the structure produced by filter_form(). You probably want to open a new issue in filterbynodetype's queue, referencing to this issue, and asking the maintainer to fix this bug.