Update docs on index, also fix xhtml-compiler boo-boo.
[htmlpurifier-web.git] / news / 2008 / 0508-3.1.0-released.xhtml
bloba12fe788d487d4b74899646f1aff50d55fcb148a
1 <?xml version="1.0" encoding="UTF-8"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
3 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
4 <html
5 xmlns="http://www.w3.org/1999/xhtml"
6 xmlns:xi="http://www.w3.org/2001/XInclude"
7 xmlns:xc="urn:xhtml-compiler"
8 xc:news="yes"
9 xml:lang="en">
10 <head>
11 <title>HTML Purifier 3.1.0 released - News - HTML Purifier</title>
12 <xi:include href="common-meta.xml" xpointer="xpointer(/*/node())" />
13 <meta name="Date" content="Sun, 08 May 2008 14:04:00 EST" />
14 </head>
15 <body>
17 <xi:include href="common-header.xml" xpointer="xpointer(/*/node())" />
19 <div id="main">
20 <h1 id="title">HTML Purifier 3.1.0 released</h1>
22 <div id="content">
23 <p>
24 HTML Purifier 3.1.0 is the first offical stable release for 3.1 series.
25 It improves HTML Purifier's integration with <abbr>PHP</abbr> 5, mainly
26 through the new use of autoloading.
27 It also includes support for the !important CSS modifier,
28 display and visibility CSS properties with %CSS.AllowTricky, marquee with
29 %HTML.Proprietary (had you scared for a moment, hmm?), a kses() wrapper,
30 %CSS.AllowedProperties, %HTML.ForbiddenAttributes and
31 %HTML.ForbiddenElements and a totally revamped ConfigDoc system. Since the
32 release candidate, there have also been a number of stability fixes such as
33 improved URI escaping, a change in serializer ID format, and a relaxed
34 format for %HTML.Allowed. And as always, numerous bugfixes.
35 </p>
36 <p>
37 <strong>Important:</strong> HTML Purifier 3.1.0 also fixes a
38 security vulnerability. Please upgrade your libraries as quickly as
39 possible. The vulnerability was discovered internally, and no known
40 exploits have been found in the wild.
41 </p>
42 <p>
43 For a detailed migration guide, please see the
44 <a xc:absolute="href" href="news/2008/3.1.0-released.html">3.1.0 release page</a>. If
45 you had been using the release candidate, you do not need to worry
46 about this.
47 </p>
48 </div>
49 </div>
50 </body>
51 </html>