Word & Press · 24 publishing platforms profiled Updated 11 October 2026

History

phpWordPress changelog: versions 3.11, 3.2 and 3.25

The archived phpWordPress changelog for 3.11, 3.2 and 3.25 (January to June 2006), set out by version, with notes on writing CMS release notes today.

By Word & Press Published 10 October 2026 Facts verified 10 October 2026 Read 5 min

The short answer

The archived phpWordPress changelog covers three versions: 3.11 (4 January to 6 February 2006), 3.2 (9 March to 3 May 2006) and 3.25 (17 May to 4 June 2006). Entries are dated and tagged NEW, ENH, CHG or BUG. Modern guidance asks for a curated, human-readable list per version.

CHANGELOG

This is the changelog Spoonlabs published for phpWordPress, a commercial PHP article manager that was renamed Vivvo in July 2006 and is unrelated to the open-source WordPress project. It records three versions in the archive. The release history puts them in context, and the news timeline covers the announcements. Entries below are shortened but keep the original tags: NEW (feature added), ENH (enhancement), CHG (change) and BUG (fix).

Which versions does the changelog cover?

Version Date range Headline changes
3.25 17 May to 4 Jun 2006 AJAX calendar, collapsable categories, newsletter import filter
3.2 9 Mar to 3 May 2006 Tabbed articles, live preferences, advanced search, plug-in manager, ContactBuilder, template manager
3.11 4 Jan to 6 Feb 2006 SEO fields on articles, comment CAPTCHA, new editor, CSV mailing list import

What changed in 3.25?

Date Changes
17 May BUG fixed MySQL 3.x advanced search. ENH AJAX calendar replaced the standard one. BUG rotating headlines failed with author or date fields off.
18 May BUG error_reporting(0) for Ajax frames. CHG rotation of rewrite rules in .htaccess. BUG RSS validation fix for images.
23 May BUG AJAX rotation now escapes ampersands. CHG “author by” tag moved to the headlines.xml.tpl template.
30 May BUG HTML_Featured_Author() pulled an image URL, not a local path. ENH JavaScript tags stripped in the WYSIWYG editor.
3 Jun NEW collapsable categories.
4 Jun NEW import filter in the Newsletter plugin for third-party email addresses.

What changed in 3.2?

Date Changes
9 Mar BUG missing $pattern in an empty new_requests mail list.
26 Mar ENH AJAX headline rotation amended to support a Flash front end.
28 Mar CHG Poll plugin fixed for the new plug-in manager. CHG default flag for published articles is Active, not Pending. ENH CAPTCHA setting (on/off) in Preferences.
30 Mar NEW Google XML Sitemap added to the Sitemap plugin. ENH “Die” logging embedded in the Dump manager.
31 Mar ENH W3C validation on the template.
1 Apr ENH tabbed browsing for Article Management.
2 Apr NEW AJAX in Preferences: live editing. ENH article management gains Search Engine options. CHG preg_replace() swapped for str_replace() in HTML_Function.php.
8 Apr NEW advanced search. BUG date search timestamp problem. NEW plug-in manager with the Dump manager.
9 Apr NEW ContactBuilder plug-in.
10 Apr NEW Template manager supporting global tags and positioning.
11 Apr CHG LinkDirectory plugin rewritten for the new plug-in manager.
12 Apr BUG various PHP 5.x notice fixes.
13 Apr NEW Arabic language file. ENH info box for Dump manager notifications.
14 Apr BUG mysql_close added to full-text search.
15 Apr ENH template editor can edit plugin templates.
17 Apr CHG admin notification info box changed. ENH upgrader sniffer.
26 Apr ENH meta name generator in META tags.
2 May CHG advanced search register globals on. NEW Swedish language file. NEW category-based private/public access for the membership system.
3 May ENH multi-language support amended for the new template system.

What changed in 3.11?

Date Changes
4 Jan BUG sign-up status fixes for unconfirmed activation emails. NEW language strings for confirm password and sign-up message. BUG newsletter broadcast to multiple users fixed. CHG admin .htaccess RewriteEngine off.
5 Jan CHG RTE editor introduced instead of SPAW. NEW popup calendar. ENH show_calendar preference.
6 Jan BUG privileges check in the category class. CHG article date format Y-m-d H:i.
13 Jan BUG poll vote ID check. ENH link redirect field length expanded.
16 Jan ENH article comments timestamp.
25 Jan BUG rss.php “$this not an object” fixed.
26 Jan ENH database columns for article keywords, description and robots index/follow.
27 Jan ENH RSS feed supports SE-friendly URLs. ENH spaces in usernames become dashes. ENH “cat/” prefix fix in category URLs. BUG admin menu show/hide fix.
28 Jan NEW Search Engine Friendly options: name, META keywords, description, robots. ENH spaces in picture and document names become dashes. BUG AJAX JS error with no featured article.
30 Jan ENH RSS and web feed UTF-8 support. BUG image path for author usernames. ENH comment management with multiple-select check-boxes. CHG .htaccess checks for static .html pages.
1 Feb ENH newsletter plug-in pagination.
2 Feb NEW CSV import of mailing list addresses. ENH friendly_path regular expression. BUG FindCategoryId return value.
3 Feb BUG restore-backup SQL count error.
6 Feb (3.11) NEW category name in meta title tag. NEW CAPTCHA image on comments. NEW custom pagination in category management. BUG email-exists check on user management. ENH PDF friendly URL path.

What does the changelog tell us about the product?

Most entries are small. A day’s work was often one bug fix, which suggests a changelog assembled from a developer’s commit notes. Tags are the only grouping, and versions are given a number only at the top of each block. Several entries assume the reader knows the code, such as the .htaccess and preg_replace() items.

How should CMS release notes be written today?

Keep a Changelog describes a changelog as “a curated, chronologically ordered list of notable changes for each version”. It says changelogs are for humans, that every version should have an entry, and that the latest version comes first with its release date shown. It recommends grouping by Added, Changed, Deprecated, Removed, Fixed and Security, with ISO 8601 dates and an Unreleased section at the top.

Measured against that, the archived page does well on newest-first order and dates. It falls short on curation, since internal fixes sit beside features, and on security, which has no tag. For a publisher deciding whether to upgrade, a separate Security group matters most. Version labels are also easy to miss: 3.25 appears as a heading, but 3.11 is marked only on its last line.

When you evaluate a CMS, read its release notes for the same things: dated releases, a clear security section and a plain statement of what breaks. The guides explain how we judge such evidence.

Questions people ask

What did the tags BUG, ENH, CHG and NEW mean in the phpWordPress changelog?

The page does not define them. From usage, NEW marks added features, ENH enhancements to existing ones, CHG changes in behaviour and BUG fixes. That reading is our inference from the entries, not a statement by Spoonlabs.

Which phpWordPress versions does the archived changelog cover?

Three: 3.11 (4 January to 6 February 2006), 3.2 (9 March to 3 May 2006) and 3.25 (17 May to 4 June 2006). Earlier versions are documented only in forum announcements, not in this changelog.

How should a CMS write release notes today?

Keep a Changelog recommends a curated list per version, newest first, with release dates and changes grouped by type such as Added, Changed, Fixed and Security. It says changelogs are for humans, not machines.

Sources

  1. The archived phpWordPress changelog page lists three versions, 3.25, 3.2 and 3.11, with dated entries each tagged BUG, ENH, CHG or NEW. — source, checked 10 October 2026.
  2. The 3.25 section runs from 17.05.2006 to 04.06.2006 and includes an AJAX calendar replacing the standard one, collapsable categories and an import filter for the newsletter plugin. — source, checked 10 October 2026.
  3. The 3.2 section runs from 09.03.2006 to 03.05.2006 and includes tabbed browsing for Article Management, live AJAX editing in Preferences, advanced search, a plug-in manager with a Dump manager, ContactBuilder, a new Template manager and category-based private/public access. — source, checked 10 October 2026.
  4. The 3.11 section runs from 04.01.2006 to 06.02.2006 and includes Search Engine Friendly options on articles, a CAPTCHA image on comments, a switch from the SPAW editor to an RTE editor, and CSV import of mailing list addresses. — source, checked 10 October 2026.
  5. The archived page's news box, dated 12 July 2006, says phpWordPress will live under a new name, Vivvo, which inherits the v3.25 release. — source, checked 10 October 2026.
  6. Keep a Changelog defines a changelog as a file containing a curated, chronologically ordered list of notable changes for each version of a project. — source, checked 10 October 2026.
  7. Keep a Changelog's guiding principles include: changelogs are for humans, an entry should exist for every version, the same types of change are grouped together, the latest version comes first and the release date of each version is displayed. — source, checked 10 October 2026.
  8. Keep a Changelog groups changes as Added, Changed, Deprecated, Removed, Fixed and Security, recommends ISO 8601 (YYYY-MM-DD) dates and an Unreleased section at the top. — source, checked 10 October 2026.