Closed (fixed)
Project:
Whizzywig - A complete WYSIWYG Editor
Version:
5.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Oct 2007 at 10:07 UTC
Updated:
25 Oct 2007 at 07:52 UTC
Checking filter default format gives false positives and puts annoying and insufficient info about the problem
Comments
Comment #1
heine commentedCan you please elaborate?
Comment #2
westwesterson commentedI have run into this too.
There are modules which enable users to pick certain default filters for certain users. If you have Filtered HTML the default for some users (for security issues), but then have other users use a format which isn't filtered lets say the site admin, which has a less secure filter like the rich text editor suggested in the documentation, you still get an error saying that the default filter is enabled.
Here are a couple of solutions:
1) This could be changed from a critical error, to a more friendly feedback option.
2) Put this in the documentation, and take out the error message.
I'm more inclined to just changing from an error to a status message AND putting it in the documentation. This may have weird effects for people who expect it to work out of the box without a filter change and who don't heed the warning, but there are some use cases where people intentionally leave the sitewide default filter as Filtered HTML.
Comment #3
heine commentedThanks.
This piece should go, HTML filters should never be disabled.
Comment #4
sdecabooter commentedYou're right... my bad.
I removed the errormessage altogether, and updated the README.txt to make the instructions more clear on this matter.
I also added a descriptive message on top of the Whizzywig settings page, which is less 'harsh' then an error message.
Comment #5
sdecabooter commentedComment #6
(not verified) commented