MuRu Migration 2.4.0 Released: Fix 404s After a Joomla 3 Migration, Plus a New Health Check
MuRu Migration 2.4.0 fixes the reason imported articles answer 404 after a Joomla 3 to 4, 5 or 6 migration, and adds a Health Check that finds and repairs what a migration usually leaves behind. If you already migrated with an older version, you do not have to start over.
Quick answer
Two small differences between Joomla 3 and Joomla 4+ made imported pages fail: a zero finish publishing date that newer Joomla reads as expired, and menu component IDs that differ from site to site. 2.4.0 converts both during the import, and the new Health Check repairs sites that were already migrated.
- Why imported articles showed a 404
- Health Check: find and fix the rest
- Check the real pages
- A better Full Migration
- Already migrated with an older version?
- Frequently asked questions
Why Imported Articles Showed a 404
A plain export and import cannot see two things that differ between the versions:
- The publish dates. Joomla 3 stores "no expiry" as
0000-00-00. Joomla 4+ reads that as already expired, so every imported article is hidden. - The component of each menu item. The component ID is specific to each site (the article component is 22 on Joomla 3 and 19 on Joomla 6), so imported menu items were attached to the wrong component and answered 404.
MuRu Migration 2.4.0 converts the dates for the target site and resolves the component from the menu link, so pages work right after the import.
Health Check: Find and Fix the Rest
Open Components → MuRu Migration → Health Check. It applies the rules Joomla uses on the frontend and lists, with examples and edit links:
Articles
Unpublished categories, missing access levels, expired dates, duplicate aliases, missing authors.
Menus
Links to missing articles, items on the wrong component, broken trees, missing parents.
Modules and contacts
Assignments to pages that no longer exist, duplicated backend modules, contacts linked to a missing user.
Problems with an unambiguous repair have a one-click Fix. Nothing changes until you press it.
Check the Real Pages
Check live pages requests every public article and menu page the way a visitor would and lists any that do not answer 200. A 403 is shown in amber because it usually means a login is required. It finds what no database check can, such as a menu item attached to the wrong component.
A Better Full Migration
- Choose what to migrate: users, articles and images, menus, site modules.
- Every category travels with the export, including empty ones and parents, so URLs and category menu items survive.
- Custom access levels and authors are recreated and matched instead of silently becoming public or the wrong person.
- A menu link whose target was not migrated is imported unpublished instead of pointing at an unrelated page.
- Administrator modules are no longer imported into your backend.
- An import report keeps every warning and downloads as a text file.
Already Migrated with an Older Version?
Quick reference
- Back up the database.
- Install MuRu Migration 2.4.0 on the new site.
- Open Health Check and press the suggested fixes.
- Press Check live pages and open anything still red.
Frequently Asked Questions
Does the Joomla 3 edition get the Health Check?
The Health Check tab, section selection and import report are in the Joomla 4/5/6 edition. The Joomla 3 edition receives every import and export fix.
Do I need to migrate again?
No. Install 2.4.0 on the new site and use the Health Check fixes.
Will the fixes change my content?
They change database rows (dates, component links, aliases, trees), so take a backup first. Nothing is written until you press a Fix button.
Moving a site is mostly about the details a plain export cannot see. 2.4.0 handles the ones that made migrated pages disappear, and tells you about the rest.
MuRu Migration 2.4.0
Move a whole Joomla site between Joomla 3, 4, 5 and 6, then check it with the Health Check. Available now for active licenses.
Comments (0)
No comments yet. Be the first to comment!