Difference between revisions of "Known upgrading issues and solutions"
From Joomla! Documentation
|Line 13:||Line 13:|
Latest revision as of 10:11, 30 June 2015
This article or section is in the process of an expansion or major restructuring. You are welcome to assist in its construction by editing it as well. If this article or section
This page lists upgrading issues you may encounter when upgrading to a current version of Joomla! from a previous one. Please use the links on this page to see more detail about the issue and the suggested fix.
|Articles||The Reported Issue||Versions|
|"Save as New" and "Save as Copy" removed from article manager after 3.3.4 Upgrade||
After upgrading from Joomla v3.3.3 to v3.3.4 The "Save as Copy" and "Save as New" buttons are no longer available when editing an article. I used a backup to revert back to v3.3.3 and all is well.
|AJAX and Content History menu items are displaying in the components menu||When a site is upgraded from Joomla 3.1 to 3.2 using FTP or another manual upgrade, a number of extensions show up through the discover install method.||3.2.x|
|Backend Login looks bad|
|Backend Login looks bad/en||
In Joomla 3.4.2 we improved the styling of the backend login page.
|Cannot create new content 3.1.4||Some users report that they receive the following error when attempting to create new content (of any type).||3.1.4|
|Cannot log in to Joomla frontend||A small number of users have reported not being able to log in to the frontend of Joomla!||3.1.4,3.1.5|
|Class 'PDO' not found||
In Joomla 3.4 a new, based on the PDO, database driver for MySQL, was added (rapidly becoming the new de facto driver for MySQL database connections). However an incomplete check for the existence of the PDO driver was implemented for some users who didn't have the driver installed with PHP. </translate>
|Class 'PDO' not found/en||
In Joomla 3.4 a new, based on the PDO, database driver for MySQL, was added (rapidly becoming the new de facto driver for MySQL database connections). However an incomplete check for the existence of the PDO driver was implemented for some users who didn't have the driver installed with PHP.
|Class attributes are not included in mailcloak||Class attributes are not being included in mailcloak.||3.3.2|
|CLI Applications Broken||Because of changes made to JTable, CLI and other stand alone applications that use JTable break in Joomla 3.1.3 and later.||3.1.3,3.1.4,3.1.5|
|Codemirror editor fullscreen mode|
|Codemirror editor fullscreen mode/en||
In Joomla 3.4.2 we improved the Codemirror Editor there we miss a one line change.
|Database schema version (3.2.3-2014-02-20) does not match CMS version (3.2.3)||
After updating Joomla to version 3.2.3 (using MySQL database), the Extensions > Extension Manager > Database > [Fix] shows "Warning: Database is not up to date!"
|Date of birth shows everywhere on a single contact page|
|Date of birth shows everywhere on a single contact page/en||
In Joomla 3.4.2 we improved the handeling of the Date of birth field.
|Delete button on the media manager does not work anymore|
|Delete button on the media manager does not work anymore/en||
In Joomla 3.4.2 we improved the media manager.
|Detailed instructions for updating from 3.1.2 to 3.1.4||Joomla! 3.1.2 wasn't an officially released version and my install was upgraded accidentally during a pre release error.||3.1.2|
|Duplicate Maintenance Info|
|Duplicate Maintenance Info/en||
|Editing module shows module XML data not available||
Some modules installed in Joomla 3.4 and higher (that previously worked in Joomla 3.3.6) show an error when attempting to edit </translate>
|Editing module shows module XML data not available/en||
Some modules installed in Joomla 3.4 and higher (that previously worked in Joomla 3.3.6) show an error when attempting to edit
|Errors in 2.5.26, 3.2.6, and 3.3.5||In the Joomla! 2.5.26, 3.2.6, and 3.3.5, an error was introduced into the code which processes Joomla! updates in the update component which causes errors when attempting to update Joomla.||2.5.26,3.2.6,3.3.5|
|Extension won't install||
Some extensions won't install on Joomla 3.4.0 giving an error of "No file selected. Unable to find install package" </translate>
|Extension won't install/zh-cn||
|Extensions Broken in 3.1.4||Some extensions that worked in 3.1.1 give a 500 error in version 3.1.4.||3.1.4|
|Fatal error Class JClassLoader||
In Joomla 3.4.2 we changed the way our Composer libraries are loaded.
|Fatal error Class JClassLoader/en||
In Joomla 3.4.2 we change the way how our composer libraries get autoloaded.
|Getting a 500 when trying to sort users by User Group||Open an article for edit, go to the Publishing tab, click to choose an author in Created by. A modal displays with 3 columns. Clicking to order by User Groups causes an error.||3.3.2|
|Global editor setting overrides user editor setting||Global Configuration editor setting is overriding individual user's editor setting.||3.3.2|
|Infinite error loop on multilanguage sites||
In some multilingual sites that were created before Joomla 2.5.4 when upgrading to 3.4 you can have a redirect loop created. </translate>
|Infinite error loop on multilanguage sites/en||
In some multilingual sites that were created before Joomla 2.5.4 when upgrading to 3.4 you can have a redirect loop created.
|Insert error in menu table of migrated data||If your site was migrated from Joomla! 1.5 to 2.5, you might experience problems when trying to update from your Joomla! 2.5.x to a 3.1.x version.||3.1.x|
|Missing JBrowser class after upgrading||After update to Joomla 3.1.4 or later, some some extensions that depend on the native autoloader, with a working code before, may stop working.||3.1.4,3.1.5|
|Module article news ordering ascending||Module article news show articles in reverse order.||3.2.0|
|Multilang-site override a option of JCategories that cause a SQL error|
|Multilang-site override a option of JCategories that cause a SQL error/en||
In Joomla! 3.4.2 we improved the multilingual code. But for now if a component don't have disable a specific option in JCategories that gets overwritten on multilinguage sites.
|No admin menu item for component||
In Joomla 3.4 a component installed will not create a menu item </translate>
|No admin menu item for component/en||
In Joomla 3.4 a component installed will not create a menu item
|Notice: Undefined variable $link com menus|
|Notice: Undefined variable $link com menus/en||
In Joomla 3.4.2 we improved the usage of modals also in menus.
|Open basedir in effect in template manager|
|Problems for Sqlsrv||The main article and category list queries are broken for SqlSrv based sites.||3.1.4,3.1.5|
|Setting proper default values for access level|
|Setting proper default values for access level/en||
Setting proper default values for access level
|Subcategories Not Showing||Why are subcategories not showing on drill downs?
In some category views subcategory information is not showing but they did prior to updating. This seems to be the case specifically when there is not a direct menu link to the category view displaying the subcategories.
|Table xxx postinstall cpanels does not exist||Users are seeing a "Table #__ doesn't exist" message due to an incompatibility in the older version of FOF code with the Joomla 3.x series.||3.2.x|
|The reCaptcha function has been temporarily disabled for Joomla 3.2||Error Message: The reCaptcha function has been temporarily disabled for Joomla 3.2||3.2.0|
|Toolbar buttons missing after upgrade||Toolbar buttons are missing in the administrator views after a Joomla! upgrade.||3.1.4,3.1.5|
|Unable to delete modules after updating||When a site is upgraded to 3.2, users are unable to delete modules and are shown a generic "An error has occurred" message. This also applies to trying to empty trash in the module manager.||3.2.x|
|Validation error on creating a menu entry|
|Validation error on creating a menu entry/en||
|Warnings upgrading from Joomla 2.5 to 3.x||When updating from the 2.5 series to the 3 series you may see a large number of warnings and notices on the update page.||3.0.x,3.1.x|