The phpWordPress 3.2 plug-in manager (2006) was fully revamped to let third-party scripts be integrated easily, with a central dump manager for notification, error and warning messages. Modern CMSs rely on directories and package tools: WordPress hosts GPL-compatible plugins, and Drupal documents installing modules with Composer.
The new plug-in manager was the fifth of six features on the phpWordPress 3.2 What’s New page. phpWordPress was a commercial PHP article manager from Spoonlabs, renamed Vivvo in 2006, and it was unrelated to the open-source WordPress project. The release history lists the other changes, and the changelog has the dated entries.
What did the plug-in manager do?
The archived page says: “Plug-in Manager has been fully revamped, allowing easy and hassle-free integration of 3rd party scripts, along with the centralized dump manager for all notification/error/warning messages.” It goes on to say that it would be “faster and easier to build on foundation of phpWordPress and customize the software to meet any specific requirements, including building up a full custom portal CMS system”. It ends: “Specific developer documentation will follow up.” No demo movie was offered for this feature.
So two things shipped together: a way to plug in scripts, and a single place to read what those scripts reported.
What does the changelog show?
The work ran through March and April 2006. On 28 March the Poll plugin was fixed to support the new manager. The “Plug-in manager system with the Dump manager” is dated 8 April. On 11 April the LinkDirectory plugin was rewritten for it. The dump manager kept changing: “Die” logging was embedded on 30 March, a notification info box was added on 13 April and the admin notification box was changed on 17 April.
The pattern says something. Existing plugins had to be rewritten for the new manager, so the change was not backwards compatible.
How were plugins obtained?
The archive shows plugins as part of the licence package. On 30 May 2006 a customer who bought the Developer package asked where to find the Contact Builder, the automatic Google SiteMap module and the automatic Link directory module. Staff said they should be in the bundle, or the customer could email support for download links. We found no public directory of third-party plugins in the archived material.
How do modern CMSs manage extensions?
The answer now is mostly a directory plus a package tool. The WordPress Plugin Directory describes itself as “the largest directory of free and open source WordPress plugins”. WordPress.org offers free hosting to plugin developers, and plugins “must be compatible with the GNU General Public License v2 or later”.
Drupal takes a different route. Its user guide tells site owners to download a contributed module with Composer, then install it through the administrative interface or Drush. See the WordPress and Drupal profiles for each project.
Both are statements from official documentation, and we have not installed extensions for this page.
What should a publisher ask about extensions?
- Where do extensions come from, and who reviews them?
- What licence terms apply?
- How are updates delivered, and what happens when an extension is abandoned?
- Does an upgrade break extensions? In 2006 the manager change forced rewrites.
- Where do extension errors appear?
That last question is the dump manager’s idea, and it still matters. A site with ten extensions needs one place to see what is failing.
The previous feature was improved search, and the last is ContactBuilder.
Questions people ask
What did the phpWordPress 3.2 plug-in manager do?
It let third-party scripts be integrated into the product, and it brought notifications, errors and warnings into one central dump manager. The archived page promised developer documentation later, and the changelog shows existing plugins rewritten for it.
Which plugins existed for phpWordPress?
The archive names Poll, LinkDirectory, Sitemap, Newsletter, ContactBuilder and a Google SiteMap module. A customer thread also mentions bundled free modules for the Developer package. We found no public plugin directory in the archive.
How are plugins distributed in modern CMSs?
It varies. WordPress.org hosts a directory of free, GPL-compatible plugins. Drupal's guide says to download contributed modules with Composer, then install them through the admin interface or Drush. Check each project's own documentation.
Sources
- The archived 3.2 feature page says the Plug-in Manager was fully revamped, allowing easy and hassle-free integration of 3rd party scripts, along with a centralized dump manager for all notification, error and warning messages. — source, checked 10 October 2026.
- The archived feature page says it would be faster and easier to build on the foundation of phpWordPress and customize it to meet specific requirements, including a full custom portal CMS system, and that specific developer documentation would follow. — source, checked 10 October 2026.
- The 3.2 changelog records 'Plug-in manager system with the Dump manager' on 08.04.2006, the Poll plugin fixed for the new plug-in manager on 28.03.2006, and the LinkDirectory plugin rewritten for the new plugin manager on 11.04.2006. — source, checked 10 October 2026.
- The 3.2 changelog records 'Die logging embedded into Dump manager' (30.03.2006), a new info box for Dump manager notifications (13.04.2006) and a changed admin notifications info box (17.04.2006). — source, checked 10 October 2026.
- On 30 May 2006 a customer asked where to get the Contact Builder, Automatic Google SiteMap generation and Automatic Link directory modules after buying the Developer package; staff said they should be in the bundle or available from support by email. — source, checked 10 October 2026.
- The WordPress Plugin Directory describes itself as the largest directory of free and open source WordPress plugins. — source, checked 10 October 2026.
- WordPress.org offers free hosting to anyone who wishes to develop a plugin in its directory, and says plugins must be compatible with the GNU General Public License v2 or later. — source, checked 10 October 2026.
- The Drupal User Guide's module installation page tells readers to first download a contributed module with Composer, then install it using either the administrative interface or Drush. — source, checked 10 October 2026.