Upgrade in place when your CMS documents a supported path from your exact version, and rebuild when it says content must be migrated to a new site. Either way, back up the database and files, rehearse on a copy, check every extension and theme for compatibility, then upgrade production.
From the original phpWordPress forum · archived copy
a forum member ·
Hi, Few questions - only just noticed this was released today. Is 3.2 only available as an upgrade? Will it ruin my existing templates? I still have sites on 3.0 that I'm waiting for you to upgarde (I know you've been busy ) - can you upgrade these for me, please?
phpWordPress staff (Moderator) ·
a forum member, you can get 3.2 either as an upgrade (you'll see download link in your Administration panel) or you can install it from the scratch. For a clean install contact support to obtain download link. As for templates - yes, it will make a partial mess that can be easily fixed (new tags, new templates...). We can assist you in migration of your sites. For upgrading sites - no problem, just contact support
a forum member ·
Thanks, a forum member. I'll email support, as I could probably do with having my hand held a bit. I've also got to do a new site with one of the template packs I bought from you, so just want to check that, too.
a forum member ·
I haven't tried the new 3.2 But I really like to know about these 2 feature in details. # Easy Google AdSense integration # Easy configurable and swapable skins Any support person like to give some details on these 2 new feature? Thank you.
phpWordPress staff (Moderator) ·
Those features are not specific to 3.2 version, they were only made more accessible. v3.2 features are in What's New section. http://www.word-press.net/whatsnew/. # Easy Google AdSense integration: allows you to easily copy/paste your AdSense inside any of the main templates (index.tpl, article_Full.tpl) and manipulate place and position. AdSense instantly shows on site. # Easy configurable and swapable skins: you can have more than one skin (template) if desired. They can be easily switched - example of this is our official demo: [link removed] This creates a possibility of being able to serve different layouts for different visitors.
View the archived thread on the Wayback Machine. Usernames and contact details have been removed.
In 2006 a customer asked whether a new release was upgrade-only and whether it would ruin existing templates. Those two questions still decide how a major CMS upgrade goes: which route the vendor supports, and what happens to the theme and extensions you depend on.
Upgrade in place or rebuild?
Start with the vendor’s own upgrade guide for your exact version. It tells you which of three routes you are on.
| Situation | Route | Example from the documentation |
|---|---|---|
| Your version has a documented successor | In-place upgrade, rehearsed on a copy | Drupal 10 to 11 requires the site to be on Drupal 10.3.0 or later and PHP 8.3.0 or later |
| Your version is too old for a direct path | Move to a supported intermediate version first | Joomla’s guide assumes you start from Joomla 5.4.x and says to update to it first |
| The architecture changed | Rebuild and migrate content | Drupal says a Drupal 6/7 site cannot simply be updated; content and configuration are migrated to a new site |
A migration is not a failure. It gives you a clean theme, a chance to drop extensions you no longer use, and a rehearsal you can repeat until the content looks right. It costs more time up front. An in-place upgrade is quicker when the path exists, but it carries every bit of old customisation forward, including the parts that no longer work.
What happens to my theme and templates?
The 2006 vendor answer was that templates would need some fixing after the upgrade. The modern version is the same: themes are tightly coupled to the CMS’s template system, so a major version often needs theme changes.
The documentation of the big systems is consistent on how to find out in advance:
- Drupal recommends the Upgrade Status module to identify compatibility gaps in contributed extensions.
- Joomla’s 5 to 6 guide says to check all extensions for compatibility with Joomla 6, and that its Behaviour - Backward Compatibility plugin must be disabled to upgrade. Anything that only works because of that plugin needs an update first.
- WordPress warns that updating replaces core files, so modifications made to core are lost. Custom work belongs in a child theme or plugin, not in core.
If your theme is custom, ask the developer what the new major version changes. If it came from a vendor, ask for a statement of compatibility with the target version in writing.
Why upgrade at all?
Unmaintained software is a risk to a publisher. PHP.net says each branch gets two years of full support and two more of security fixes only, and that an end-of-life release may be exposed to unpatched vulnerabilities. A CMS that needs a retired PHP version is already on a clock. Major CMS releases also raise their minimum PHP version, as the Drupal 11 documentation shows.
How do I back up properly?
WordPress documentation says a backup has two parts, the database and the files, and that you need both to restore a typical site. The files include core, themes, plugins, uploads, wp-config.php and .htaccess. It also says to back up before an upgrade or a move.
Joomla’s guide adds the step people skip: test your backup to make sure it restores. A backup you have never restored is a hope, not a backup. Keep a copy off the server.
How do I rehearse an upgrade?
Drupal and Joomla both steer you away from upgrading directly on production. Drupal suggests doing the update locally first and then deploying; Joomla suggests a subdomain or a local copy.
- Copy production files and database to a staging environment, ideally with the same PHP version.
- Disable anything on the copy that sends email, charges cards or pings third parties.
- Run the upgrade exactly as you intend to on the day, and time it.
- Note every error, then fix or replace the extension responsible.
- Repeat until it runs clean, then schedule the live upgrade for a quiet period.
Our installation notes and the self-hosted guide cover setting up a copy.
What should I test after the upgrade?
For a news or article site, test the parts that earn money and traffic, not only the home page.
| Area | Check |
|---|---|
| Publishing | Create, schedule and edit an article with images and embeds |
| URLs | Old article URLs still resolve; redirects and canonical tags are unchanged |
| Templates | Article, category, author and search pages render on desktop and phone |
| Feeds and sitemaps | RSS feed and XML sitemap load and list recent articles |
| Extensions | Each plugin or module from your pre-upgrade list still works |
| Forms and email | Contact, newsletter and comment forms deliver |
| Logs | Watch error logs while browsing; Drupal’s guide lists log monitoring as a post-upgrade task |
| Rollback | You know how to restore the backup and how long it takes |
WordPress documentation adds a useful diagnostic: if problems appear, deactivate the plugins that do not ship with WordPress and re-activate them one by one to find the culprit.
When should I ask for help?
The 2006 customer asked the vendor to upgrade their sites. That is still a reasonable request, but agree the scope and price first. See working with vendors and agencies for what to put in writing. Version gaps are the other usual trouble: if you are several releases behind, read sequential upgrade paths before you start.
This page summarises vendor documentation; Word & Press has not run these upgrades. Our method explains what we do and do not test.
Questions people ask
Should I upgrade my CMS in place or start a fresh install?
Follow what your CMS documents for your version. If it offers a supported upgrade path, an in-place upgrade on a tested copy is usually less work. If it says content must be migrated to a new site, as Drupal does from version 7, plan it as a rebuild.
Will a major upgrade break my theme?
It can. Themes and templates are the part most likely to need changes, because template tags and APIs change between major versions. Check the theme vendor's compatibility notes and test the upgrade on a copy before touching the live site.
What should I back up before upgrading a CMS?
The database and every file that matters: core, themes, plugins or extensions, uploads and configuration files. WordPress documentation says you need both database and files to restore a typical site. Test that the backup restores before you start.
Do I need a staging site for a CMS upgrade?
Yes, for any major version. Both Drupal and Joomla documentation recommend rehearsing the upgrade away from production, locally or on a subdomain. A copy of production lets you find broken extensions without readers seeing errors.
Sources
- Drupal's Drupal 10 to 11 upgrade guide states the site must be running Drupal 10.3.0 or later, and that the hosting environment needs PHP 8.3.0 or later. — source, checked 10 October 2026.
- The same guide recommends the Upgrade Status module to identify compatibility gaps in contributed extensions, and recommends performing the update locally (in DDEV) first and then deploying to the server. — source, checked 10 October 2026.
- The same guide lists running automated tests and monitoring logs while browsing as post-upgrade tasks. — source, checked 10 October 2026.
- Drupal's documentation states that an update cannot simply be applied to an existing Drupal 6/7 site; the content and configuration must be migrated to a new Drupal 10 (or later) site, using the Migrate modules in core. — source, checked 10 October 2026.
- Joomla's 5 to 6 upgrade guide assumes you are starting from Joomla 5.4.x and says that if you are on an earlier version you should update to 5.4.x before upgrading to Joomla 6.x. — source, checked 10 October 2026.
- Joomla's 5 to 6 upgrade guide says to back up the website and to test the backup to make sure it restores. — source, checked 10 October 2026.
- Joomla's guide recommends testing the upgrade on a subdomain or locally, says to check all extensions for compatibility with Joomla 6, and says the Behaviour - Backward Compatibility plugin needs to be disabled in order to upgrade to Joomla 6. — source, checked 10 October 2026.
- WordPress documentation says a backup has two parts, the database and the files (core, themes, plugins, uploads, wp-config.php, .htaccess), that both are needed to fully restore a typical site, and to back up always before an upgrade or a move. — source, checked 10 October 2026.
- WordPress's extended upgrade instructions say that if layout problems appear after upgrading, you should deactivate all plugins that do not come with WordPress and re-activate them one by one. — source, checked 10 October 2026.
- WordPress's update documentation warns that the upgrade affects all core files and that any modifications made to core files will be lost. — source, checked 10 October 2026.
- PHP.net states each release branch is fully supported for two years and then supported for two further years for critical security issues only; an end-of-life release is no longer supported and may be exposed to unpatched security vulnerabilities. — source, checked 10 October 2026.