phpWordPress 2.52 and its new template system (2004)

The first post in the archived forum is short. On 1 December 2004, phpWordPress staff wrote that version 2.52 was released, “featuring new template system, even more easy to use”, and pointed readers to the pricing page for a full feature list. That is all the thread says, so the rest of this page draws on the product’s own archived documentation.

phpWordPress was a commercial PHP article manager from Spoonlabs. It was renamed Vivvo in July 2006 and has no connection to the open-source WordPress project. The release history shows where 2.52 sits among later versions.

What was the 2.52 template system?

According to the archived documentation, templates lived in a /templates folder. They carried a .tpl extension but were ordinary HTML files, so anyone who could edit HTML could work on them in the editor of their choice. Special tags in curly braces marked where article data, such as an ID or a title, was inserted. The documentation warned editors not to rename or remove those tags.

A page was usually built from several templates. The documentation names separate ones for breadcrumbs, the full article, the short article view used on category pages, votes, comments and the calendar. Each template matched a specific action or event on the site.

What did it change for publishers in 2005?

Without a template layer, layout and logic can end up in the same PHP files, and a redesign means editing code that can also break the site. A template layer let a publisher hand the design to someone who knew HTML but not PHP.

The documentation also says templates could be controlled from the Administration area, where each one could be changed and saved without a third-party editor. That is a convenience for a small team, and it is also a risk. A typing mistake in a live template changes the live site, and the archived text does not describe any preview or versioning step.

How do publishers meet the same need today?

Current publishing systems keep the idea and add structure around it. Layout lives in a theme or a set of templates. Content lives in a database as fields. Most systems separate the two so that a redesign does not need a content migration.

The trade-offs have not gone away:

• Customisation versus upgrades. The more you change a template, the more work each update becomes.
• Who can edit. Letting editors change templates in the browser is quick, but it needs permissions and a way to roll back.
• Reuse. Splitting a page into many small templates makes parts reusable and makes the whole harder to read.

When comparing systems, ask where the templates live (files, database or both), who can change them and how a change is tested before readers see it. The guides cover that kind of question for current software.

Why does a one-line announcement still matter?

It dates a feature. Version 2.52 shows that the product treated design as separate from content from late 2004, a few months before the author and search updates described elsewhere in the Product Updates board. The News board lists the other announcements from the period.