HTML Purifier

HTML Purifier 3.2.0 is an amalgamation of new features and fixes that have accumulated over a four month period. Some notable features include optional removal of empty elements, column tracking for tokens, proper support for the name attribute and ... [More] overridable behavior for alt text. There were also major improvements to the test suite interface, error collection output and the auto-formatter framework. The new configuration directives in this release are: See NEWS for a complete changelog. There are numerous new features not mentioned here. Along with this release, we would like to announce full disclosure on the two security vulnerabilities patched in 3.1.1. Please see the CSS Backslash and Shift_JIS full disclosure pages. [Less]

HTML Purifier 3.2.0 is an amalgamation of new features and fixes that have accumulated over a four month period. Some notable features include optional removal of empty elements, column tracking for tokens, proper support for the name attribute and ... [More] overridable behavior for alt text. There were also major improvements to the test suite interface, error collection output and the auto-formatter framework. The new configuration directives in this release are: See NEWS for a complete changelog. There are numerous new features not mentioned here. Along with this release, we would like to announce full disclosure on the two security vulnerabilities patched in 3.1.1. Please see the CSS Backslash and Shift_JIS full disclosure pages. [Less]

HTML Purifier 3.2.0 is an amalgamation of new features and fixes that have accumulated over a four month period. Some notable features include optional removal of empty elements, column tracking for tokens, proper support for the name attribute and ... [More] overridable behavior for alt text. There were also major improvements to the test suite interface, error collection output and the auto-formatter framework. The new configuration directives in this releases are: See NEWS for a complete changelog. There are numerous new features not mentioned here. Along with this release, we would like to announce full disclosure on the two security vulnerabilities patched in 3.1.1. Please see the CSS Backslash and Shift_JIS full disclosure pages. [Less]

If you're reading this news entry, you're probably a user of HTML Purifier. In fact, it wouldn't be too far fetched to say you're a power user of HTML Purifier. In fact, you probably know the ins-and-outs of the HTMLPurifier class, have used HTML ... [More] Purifier for multiple projects, and, doubtless, have some gripes about HTML Purifier. Well, now is the chance to let those latent feature requests, complaints of poor documentation, and gotcha's be heard. We gave you the source; it is time for you to use it. Today, we have launched a new forum, the “Internals” forum. This is the place for anyone interested in playing a part in HTML Purifier's open source development process; to display prototypes of new features, to discuss HTML Purifier's support of the upcoming versions of HTML, to ask for questions regarding internal components, and much more. If you've ever modified a portion of HTML Purifier's core code, or created an extension to it, dust it off and show it to the world. We've migrated to Git, so you can fork the main project, develop your new feature, and hopefully get it integrated back into the mainline. If you've never looked at HTML Purifier's source before, now is the time to start. This document on contributing will give you inside tips and tricks to getting started developing HTML Purifier. Thanks for reading! We look forward to seeing your contributions. [Less]

If you're reading this news entry, you're probably a user of HTML Purifier. In fact, it wouldn't be too far fetched to say you're a power user of HTML Purifier. In fact, you probably know the ins-and-outs of the HTMLPurifier class, have used HTML ... [More] Purifier for multiple projects, and, doubtless, have some gripes about HTML Purifier. Well, now is the chance to let those latent feature requests, complaints of poor documentation, and gotcha's be heard. We gave you the source; it is time for you to use it. Today, we have launched a new forum, the “Internals” forum. This is the place for anyone interested in playing a part in HTML Purifier's open source development process; to display prototypes of new features, to discuss HTML Purifier's support of the upcoming versions of HTML, to ask for questions regarding internal components, and much more. If you've ever modified a portion of HTML Purifier's core code, or created an extension to it, dust it off and show it to the world. We've migrated to Git, so you can fork the main project, develop your new feature, and hopefully get it integrated back into the mainline. If you've never looked at HTML Purifier's source before, now is the time to start. This document on contributing will give you inside tips and tricks to getting started developing HTML Purifier. Thanks for reading! We look forward to seeing your contributions. [Less]

You may have noticed some various improvements and changes to our news system; entries now get their own permalink pages and the most recent news entry shows up on the front page. These are some easily noticeable cosmetic changes demonstrating the ... [More] new News DOMFilter. This filter aggregates pages following the YYYY/MMDD-name.xhtml format in a folder and places the most recent contents on one page. This is opposed to what we previously did, which was stuff all the news contents on one page and have a scraper generate RSS for us (by the way, we still use the same scraper, which is due to the quite nice modularity of the two filters). There should be more improvements coming soon as we add the features and trappings of a standard “blog”; expect comments and improved navigation, for example. I also plan on launching a personal weblog for PHP and other development related things; stay tuned. As usual, this software is all free and can be accessed under the XHTML Compiler project at repo.or.cz. [Less]

You may have noticed some various improvements and changes to our news system; entries now get their own permalink pages and the most recent news entry shows up on the front page. These are some easily noticeable cosmetic changes demonstrating the ... [More] new News DOMFilter. This filter aggregates pages following the YYYY/MMDD-name.xhtml format in a folder and places the most recent contents on one page. This is opposed to what we previously did, which was stuff all the news contents on one page and have a scraper generate RSS for us (by the way, we still use the same scraper, which is due to the quite nice modularity of the two filters). There should be more improvements coming soon as we add the features and trappings of a standard “blog”; expect comments and improved navigation, for example. I also plan on launching a personal weblog for PHP and other development related things; stay tuned. As usual, this software is all free and can be accessed under the XHTML Compiler project at repo.or.cz. [Less]

After several weeks of testing, HTML Purifier is proud to announce that it will be switching to Git as its source control management system. Git offers a number of advantages over Subversion: Superior support for branchy development. Subversion 1.5 ... [More] introduces merge-tracking which somewhat diminishes this benefit, but implementing that is entirely at the whimsy of Dreamhost, which I am not going to bother with. Increased possibility for user participation. Git makes it extremely easy to do local development and submit patches. Data redundancy. Every user has a complete copy of HTML Purifier's history, making it extremely difficult to lose data. This is opposed to our current setup, where htmlpurifier.org is a central point of failure, and backups are sent to only one other machine. Performance. Git is fast, both in terms of disk operations and network operations. Gone are the days of waiting several minutes for Subversion to finish committing. Currently, only htmlpurifier has been migrated to Git; htmlpurifier-web will be migrated after any kinks are worked out. There are number of features such as nightly snapshot generation and contributor documentation that needs to be written. We will be using repo.or.cz as our primary remote repository; push access will be administered there, and changes will be mirrored (courtesy of a script by aeruder at #git) to a repository hosted at git.htmlpurifier.org as well as GitHub. If you want to grab a development copy, use this command: git clone git://repo.or.cz/htmlpurifier.git Feel free to play around, and register comments and complaints at the forum. [Less]

After several weeks of testing, HTML Purifier is proud to announce that it will be switching to Git as its source control management system. Git offers a number of advantages over Subversion: Superior support for branchy development. Subversion 1.5 ... [More] introduces merge-tracking which somewhat diminishes this benefit, but implementing that is entirely at the whimsy of Dreamhost, which I am not going to bother with. Increased possibility for user participation. Git makes it extremely easy to do local development and submit patches. Data redundancy. Every user has a complete copy of HTML Purifier's history, making it extremely difficult to lose data. This is opposed to our current setup, where htmlpurifier.org is a central point of failure, and backups are sent to only one other machine. Performance. Git is fast, both in terms of disk operations and network operations. Gone are the days of waiting several minutes for Subversion to finish committing. Currently, only htmlpurifier has been migrated to Git; htmlpurifier-web will be migrated after any kinks are worked out. There are number of features such as nightly snapshot generation and contributor documentation that needs to be written. We will be using repo.or.cz as our primary remote repository; push access will be administered there, and changes will be mirrored (courtesy of a script by aeruder at #git) to a repository hosted at git.htmlpurifier.org as well as GitHub. If you want to grab a development copy, use this command: git clone git://repo.or.cz/htmlpurifier.git Feel free to play around, and register comments and complaints at the forum. [Less]

After several weeks of testing, HTML Purifier is proud to announce that it will be switching to Git as its source control management system. Git offers a number of advantages over Subversion: Superior support for branchy development. Subversion 1.5 ... [More] introduces merge-tracking which somewhat diminishes this benefit, but implementing that is entirely at the whimsy of Dreamhost, which I am not going to bother with. Increased possibility for user participation. Git makes it extremely easy to do local development and submit patches. Data redundancy. Every user has a complete copy of HTML Purifier's history, making it extremely difficult to lose data. This is opposed to our current setup, where htmlpurifier.org is a central point of failure, and backups are sent to only one other machine. Performance. Git is fast, both in terms of disk operations and network operations. Gone are the days of waiting several minutes for Subversion to finish committing. Currently, only htmlpurifier has been migrated to Git; htmlpurifier-web will be migrated after any kinks are worked out. There are number of features such as nightly snapshot generation and contributor documentation that needs to be written. We will be using repo.or.cz as our primary remote repository; push access will be administered there, and changes will be mirrored (courtesy of a script by aeruder at #git) to a repository hosted at git.htmlpurifier.org as well as GitHub. If you want to grab a development copy, use this command: git clone git://repo.or.cz/htmlpurifier.git Feel free to play around, and register comments and complaints at the forum. [Less]