In-place editing in phpWordPress 3.2 (2006) applied changes to Preferences instantly, with no need to submit and reload. The changelog calls it AJAX embedded into Preferences for live editing. WordPress later documented a Customize API for live-previewing changes, which previews first and publishes afterwards.
The third of the six features on phpWordPress 3.2’s What’s New page was “In-place editing for Preferences”. 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 in-place editing do?
The archived page is two sentences long: “All the changes made to the website are applied instantly and on the fly. There is no more need to submit, and reload to apply the changes.” A 2,689 KB QuickTime movie followed, which is not archived as text, so we cannot describe the controls.
The changelog narrows it down. On 2 April 2006 it records “AJAX embedded into Preferences section - live editing”. The feature page’s heading says Preferences, the settings area, rather than articles. The wording “changes made to the website” could suggest more, but the dated entry points only at Preferences.
How did AJAX fit into the release?
AJAX was already in the product. Version 3.0.1 in December 2005 added AJAX rotation of headlines on the home page and auto-complete search. For 3.2, the release announcement said the product brought “a desktop-like experience to the article administration” and used AJAX to update page elements without reloading the entire page.
The announcement presented it as a selling point. It also introduced new failure modes. The 3.2 changelog contains AJAX fixes, such as an error for Ajax frames and a JavaScript error when there was no featured article. Instant updates meant instant bugs.
How do CMSs handle live changes now?
Most admin interfaces update without reloads, so the plain feature is no longer notable. What differs is whether you can review a change before the public sees it.
WordPress documents a Customize API described as “a framework for live-previewing any change to WordPress”. The key word is previewing: you see the effect first, and publishing is a separate step. The block editor documentation likewise lists “Save draft”, which saves a post without publishing it, and “View”, which shows the post with current changes applied.
So the modern pattern is closer to preview then publish than to the 2006 idea of changes applied instantly. Both are documented behaviours, not tested by us. The WordPress profile has more on how the editor is assessed.
What should an editor check?
Ask what happens when you change a setting. Does it go live at once, wait for a save, or preview first? For a newsroom the safest answer is preview first, with the ability to undo. Instant application suits low-risk preferences, such as a display option. It suits a navigation or a template setting much less.
Also check how errors are reported. A screen that updates without reloading should still tell you when a change failed.
The previous feature was membership-based access, and the next is improved search.
Questions people ask
What was in-place editing in phpWordPress 3.2?
A change to the Preferences screen. The archived page says changes applied instantly and on the fly, with no need to submit and reload. The changelog says AJAX was embedded into Preferences for live editing, dated 2 April 2006.
Did in-place editing apply to articles?
The archived page names Preferences, which are site settings. It does not say articles could be edited in place. The 8 May announcement describes updating page elements without a full reload in article administration.
Is applying changes instantly always better?
No. Instant changes save time but remove the chance to review before visitors see them. WordPress documents both a live preview in its Customize API and a separate save-draft step, which suggests the review step still matters.
Sources
- The archived 3.2 feature page says all the changes made to the website are applied instantly and on the fly, and that there is no more need to submit and reload to apply the changes. — source, checked 10 October 2026.
- The archived feature page offered a 2,689 KB QuickTime movie. — source, checked 10 October 2026.
- The 3.2 changelog records 'AJAX embedded into Preferences section - live editing' on 02.04.2006. — source, checked 10 October 2026.
- The 8 May 2006 announcement said 3.2 brought a desktop-like experience to article administration, using AJAX to update various page elements without reloading the entire page. — source, checked 10 October 2026.
- Version 3.0.1 (8 December 2005) added AJAX rotation of headlines on the home page and auto-complete search. — source, checked 10 October 2026.
- The WordPress Customize API documentation describes a framework for live-previewing any change to WordPress, with a unified interface for users to customize aspects of their theme and site. — source, checked 10 October 2026.
- The WordPress block editor offers 'Save draft' to save a post without publishing it, and a 'View' option to see how the post looks on the site with the current changes applied. — source, checked 10 October 2026.