Quote by: DirkAs far as content coming from your users is concerned, it's really in your own best interest that these things are filtered ...
I can understand your frustration from an Admin's point of view, though. That's why there's the "Skip HTML Filter for Root?" option ...
Inline CSS isn't going to work with kses. That's a bug / limitation of kses. For missing tags and attributes, maybe someone could write an "import" script that makes it easier to get a working set of HTML tags and attributes into the configuration?
bye, Dirk
To me, this is a fundamental flaw in logic.
On the one hand, you take the position that it's in my own best interests that content from ALL users – even users I happen to deem safe – is filtered. Yet on the other hand, you are providing access to the FCKeditor to *all* users when it is enabled! Either you want Geeklog users to enjoy FCKeditor, or not - you can't have it both ways. If you try to have it both ways, you end up with this very frustrating scenario where something that could be excellent is crippled / broken instead. At best, you're setting up FCKeditor for failure with this logic, which is, like it or not, a bad user experience for Geeklog users and administrators.
What you seem to be telling me is my only recourse is to:
a. Give all story admins access to the root account so that they can use FCKeditor the way it is designed to be used. I refuse to do this. Why have the
story admin group at all then?
-or-
b. Disable FCKeditor completely, since there is no way to get it working correctly for all story editors.
I'd hate to do that, because the alternative
Plain Text and
HTML editors pretty much suck.
Neither is an acceptable answer to this problem, to me. I don't see the point in offering FCKeditor to your users if half of its features are, in effect, hopelessly broken.
Please reconsider your position on this. This is not good for the Geeklog community as it stands. You might as well remove FCKeditor completely, IMO. It's a bad user experience.
-mono