In case of a manual upgrade from Joomla 2.5.17 to J3.2.1, it happens that some tables or columns are not present in the DB before that the DB / Fix is applied and therefore may cause DB Errors.
To allow using the Database / Fix functionality, it is important that this intercept all kind of DB errors.
This is why we added a try/cath on the loadObject that allow have access to the Extension Manager / Database / Fix action.
@test Success. After creating a test case that triggers the code I was able to see that no longer the error page is shown but the error message is shown after fixing the database.
roland-d
- test_item
- 9 May 2015
- Tested successfully
joomla-cms-bot
- 
Works as expected.
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6275.