This plugin extends the HTML functionality of the Wordpress kses.php file, which states the allowable HTML that the post/page content editor will accept. It allows the site administrator to optionally enable support for currently disallowed HTML tags. Those tags include: object, embed, param, iframe and map. We also added additional support to the div and img tags.
Keep in mind, that by allowing a tag, you are making it acceptable to post said HTML and save it. If your users contribute to your blog, it is important that you make sure you are not enabling any HTML that could be malicious, wreaking havoc to your environment. If there is a tag that is missing or that you would like us to add and support, please drop us a note.
[...] I have found that the plugin Extend KSES works a whole lot [...]
Report this comment
[...] I have found that the plugin Extend KSES works a whole lot [...]
Report this comment
Hi – in order to get work the “Google Syntax Highlighter for WordPress” we have to change the kses.php after every update of Wordpress. The ‘pre’ array has to be extended to include the attributes ‘name’, ‘class’ and ‘lang’ (see http://wordpress.org/support/topic/276152). It would be a pleasure if your plugin would support ‘pre’ tag too. Thanks in advance.
Report this comment
@Ralf – I have just checked in version 2.2 to Wordpress. Once it shows, it will have support for Google Syntax Highlighter.
We’re running wpmu version 2.8.6 — sorry for the delay in replying!
Report this comment
Hi – I tried the plugin but it did not behave as expected in our WPMU installation. Users still saw their IFRAME tags disappear even after activation and configuration. I had modified our kses include to allow other tags — could that be the issue?
Report this comment
@Kevin Cooke – What version of WPMU are you currently running? I haven’t seen / experienced an issue with a custom kses.php file and the plugin conflicting, but we’re always looking for additional tags to add for greater support. If we’re missing some tags that you frequently use, feel free to let us know what they are. We’d love to add them. If you can also send along an example of the iframe code you’re using, perhaps we are missing one of the values that is set, which if so, will certainly kill off the iframe tag completely.