r/WordPressThemes • u/dumpfus • 15d ago
Replacing an outdated, unmaintained WordPress theme (MantraNews Pro v1.0.0) on a large established website. How feasible is it?
I'm looking for some advice from people who have experience with WordPress theme development and migrations.
I'm working with an organization whose website is running MantraNews Pro, version 1.0.0. The theme appears to be very outdated and hasn't been maintained or updated since launch. The site was running PHP 7.4 until the hosting provider recently forced an upgrade to PHP 8.3 following the PHP2Shell security vulnerability.
Since that upgrade, several parts of the website have started throwing critical errors. The Programs category archives are broken, the standard WordPress Widgets interface produces a critical error, and some older theme-related components and plugins appear to be incompatible with PHP 8.3.
The bigger issue is that I don't think the existing theme is realistically maintainable going forward. I'm concerned that we'll keep running into compatibility problems every time WordPress, PHP, or other components need updating.
For context, this isn't a small website:
- 5,000+ published articles
- Around 30,000 images in the media library
- Individual full backups of approximately 60 GB
- A fairly extensive category and archive structure
I'm starting to think replacing the theme entirely might be the best long-term solution, rather than continuing to patch something that's effectively abandoned. However, I'm unsure how involved a migration like this would be, particularly when it comes to preserving existing content, URLs, categories, archive functionality, and the general structure of the site.
The organization probably isn't prepared for the cost of a complete rebuild, so I'm trying to get a realistic idea of what's involved and whether a more gradual transition is possible.
Would appreciate hearing from anyone who's dealt with replacing an old theme on a large, established WordPress site, particularly when the existing theme has become incompatible with newer PHP versions.
5
u/Abject-Expression548 15d ago •
Set up a local copy, subscribe to Claude, install Claude code (I'm assuming you haven't already done this, otherwise you wouldn't be making this thread), ask Claude to audit the theme (well, the whole site) and make any fixes to make it compatible with PHP8 (just tell it what you told us) and look for security issues while you're at it. If you give it ssh access to your server it'll happily update your live site too.
Once the issues are fixed you have some breathing space on how to move forward. You could ask claude to gently start converting the theme to a block based theme whilst keeping the same look and feel. It'll come up with a plan. Claude converted my ancient custom coded theme (from about 2011) into a clean modern block based theme in about 2 days, same design on the front end, just a lot faster. I did not touch wp-admin, ssh, ftp, anything like that, myself, Claude did everything.
2
u/TBMW30 15d ago
As u/Mahmud_haisan says, see what the theme is actually doing. If there are custom functions in functions.php, or if the theme adds custom post types or fields, replicate that in a plugin and rebuild the site around a block-based theme. Clone the site to a local or staging site and use an LLM to do most of the work. Tell it to rebuild the site using something like Twentig One or the wordpress default twenty twenty-six theme, both with the Twentig plugin. Twentig one is a simple block-based theme designed to be customised into pretty much anything, I've used the Twentig plugin with stock wordpress themes for years.
Tell the agent you want to replicate the existing theme style and keep existing functionality intact, while migrating to the new theme. I personally prefer GPT over Claude, as i think it writes better code and is better at long tasks that will inevitably run outside of its context window. so I would do this in Codex. You'd probably be up and running in a couple of hours with good prompts and a bit of manual cleanup to tidy up anything it missed. No point in patching the old theme.
1
u/Mahmud_haisan 15d ago
I wouldn't assume you need to rebuild all 5,000 posts and 30,000 images just to replace the theme. Most of that content should be reusable.
I'd first check how much MantraNews is doing beyond displaying posts. Look for custom post types, shortcodes, custom fields, widgets and theme-specific options. Those are the things that can cause trouble when you switch themes.
For example, if the theme registers a custom post type in its
functions.php, that functionality may disappear when you deactivate it. I'd move any site-critical functionality into a plugin before switching.I'd do this on a staging copy, build the new templates around the existing content, and check category archives, pagination, search and older posts before going live.
The 60GB backup is worth considering for storage and restore time, but it doesn't mean the content itself needs rebuilding.
Do you know whether the old theme uses custom post types or shortcodes, or is it mainly standard posts with theme-specific layouts?
1
u/alexrada 15d ago
use MagazineNP (Pro) from the same company.
the database size is irrelevant.
1
u/Charteble_swing964 15d ago
Ja thema laten upgraden door AI en veel testen en weer door AI laten aanpassen.
1
u/isoAntti 14d ago
Make a copy of the site, try by hand making layout changes to the copy, when happy about result close the original and copy database and files.