Joomla 2.5 to 3.x Common Migration Errors
From Joomla! Documentation
The most common errors from Joomla 2.5 to 3 can be summed up in two items:
- Technical Specifications not met
- Third-party extension incompatibility
Go through your extensions in the Manage tab again. Likely, there is something in there that you missed. Have someone else look for you if you must. Sometimes it just takes another set of eyes to find extensions that need to be uninstalled or updated before a successful migration happens.
This document is a work in progress. You may add errors and solutions to this page. In the meantime, if you have an error from 2.5 to 3.x, copy the error into a Google search bar eliminating the parts that are server/site specific.
For example, if you get an error that says:
Fatal error: Call to a member function get() on a non-object in home/account/public_html/directory/administrator/components/com_installer/controller.php on line 39
Cut out the
home/account/public_html/directory portion of the error during your search so you get better search results.
For very large or very complex 2.5 to 3.x migrations
The one-click update will be fine and work well for many. For some larger, more complex sites, the one-click update may not be the best route. For large or very complex sites, you may want to follow instructions for a regular migration and bypass the one-click update functionality. To do this, follow the same instructions for planning 1.5 to 3.x and migrating from Joomla 1.5 to 3.x, simply substitute 2.5 for 1.5 while reading.
Errors & Solutions
Add errors and solutions below. Note if you have never added a link to a document before, save your text before linking! Then once saved go back in and add the link.
logs/joomla_update.phpto see if a proper update happened. Include this log with any post to the Joomla Forums so that people can help you. If the site is updated properly, you can use phpMyAdmin to disable third-party plugins that you may have overlooked before updating to Joomla! 3.x.
SELECT * FROM `#__extensions` where type = 'plugin' and extension_id > 700 Use your own prefix (#_)
Set column enabled to 0 to disable the plugin.
You need to restore from a backup if
logs/joomla_update.php is incomplete.
Alternative ways to get to the Database and/or Discover tabs