I am using HTML Purifier (http://htmlpurifier.org/)

I just want to remove `&lt;script&gt;` tags only. 
I don&#39;t want to remove inline formatting or any other things.

How can I achieve this?

One more thing, it there any other way to remove script tags from HTML

remove script tag from HTML content

Is there a simple approach to add a HTML5 ruleset for HTMLPurifier?

HP can be [configured to](http://htmlpurifier.org/docs/enduser-customize.html) recognize new tags with:
 
    // setup configurable HP instance
    $config = HTMLPurifier_Config::createDefault();
    $config-&gt;set(&#39;HTML.DefinitionID&#39;, &#39;html5 draft&#39;);
    $config-&gt;set(&#39;HTML.DefinitionRev&#39;, 1);
    $config-&gt;set(&#39;Cache.DefinitionImpl&#39;, null); // no caching
    $def = $config-&gt;getHTMLDefinition(true);

    // add a new tag
    $form = $def-&gt;addElement(
      &#39;article&#39;,   // name
      &#39;Block&#39;,     // content set
      &#39;Flow&#39;,      // allowed children
      &#39;Common&#39;,    // attribute collection
      array(       // attributes
      )
    );

    // add a new attribute
    $def-&gt;addAttribute(&#39;a&#39;, &#39;contextmenu&#39;, &quot;ID&quot;);


However this is clearly a bit of work. Since there are a lot of new HTML5 tags and attributes that had to be registered. And new global attributes should be combinable even with existing HTML 4 tags. (It&#39;s difficult to judge from the docs how to augment core rules). So, is there a more useful config format/array structure to feed new *and* updated tag+attribute+context configuration (inline/block/empty/flow/..) into HTMLPurifier?


    # mostly confused about how to extend existing tags:
    $def-&gt;addAttribute(&#39;input&#39;, &#39;type&#39;, &quot;...|...|...&quot;);

    # or how to allow data-* attributes (if I actually wanted that):
    $def-&gt;addAttribute(&quot;data-*&quot;, ...


And of course not all new HTML5 tags are fit for unrestricted allowance. HTMLPurifier is all about content filtering. Defining value constraints is where it&#39;s at. -- `&lt;canvas&gt;` for example might not be that big of a deal when it appears in user content. Because it&#39;s useless at best without Javascript (which HP already filters out). But other tags and attributes might be undesirable; so a flexible configuration structure is imperative for enabling/disabling tags and their associated attributes.

(*Guess I should update some research...*). But there&#39;s still no practical compendium/specification (no, XML DTDs aren&#39;t) that suits a HP configuration.

- http://simon.html5.org/html-elements
- http://www.w3.org/TR/html5-diff/#new-elements
- http://www.w3.org/TR/html5-diff/#new-attributes

(Uh, and HTML5 is no longer a draft.)


All Htmlpurifier Solutions on Gang of Coders

Total of 2 Htmlpurifier Solutions

remove script tag from HTML content

HTML filter that is HTML5 compliant