Feeling Lucky
?
[#6252] - Catch the potential DB errors when "#__postinstall_messages" is missing
- Closed
- 2 Mar 2015
- Medium
- Build: staging
- # 6252
- Diff
- zero-24:patch-13
- Success The Travis CI build passed Details
User tests: Successful: Unsuccessful:
Redo of #2840
This try catch the error if the postinstall table can not found. e.g. on upgrade from 2.5; or other Problems with the database table.
How to test
- setup clean staging.
- remove the #__postinstall_messages table form the database
- you can't open the cpanel.
- apply the patch
- you can access the cpanel but we display the error.
Credits and Thanks goes to @jms2win
joomla-cms-bot
- | Labels |
Added:
?
|
||
brianteeman
- | Category | ⇒ | Installation |
| Status | Pending | ⇒ | Ready to Commit |
zero-24
- comment
- 2 Mar 2015
As the code was orginaly contibuted by @jms2win i move this here to RTC. Thanks @waader for your test!
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6252.
| Status | Ready to Commit | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2015-03-02 13:41:34 |
zero-24
- comment
- 2 Mar 2015
@Kubik-Rubik don't forget @waader for testing 
Kubik-Rubik
- comment
- 2 Mar 2015
I usually only thank the PR creator! ;-)
But of course I am also thankful to all testers!
zero-24
- comment
- 2 Mar 2015
Thank you @zero-24 to have manage the Github things to make it finally fixed.
In fact, this issue was due a problem with the Migration from J2.5 to J3.x and the usage of the Method C.
In the same order, there are still other pending issues that helps in the migration from J2.5 to J3.x with the Method C.
https://docs.joomla.org/J2.5:Upgrading_from_an_existing_version#Method_C_-_Manual_Upgrade
I have reported that at
http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_id=8103&tracker_item_id=33177
That includes also the reference to the pull request that I have created more than 1 year ago
Here are some PR to review.
#2822
#2840 (done here)
#2839
The procedure to test is easy.
Just install a J2.5 and after apply the Method C (unzip the J3.x over the J2.5)
After that, you should be able to login on J3.x and go in the extension manager / database => Fix button to apply the DB changes.
This procedure fails due to several issue that I have described in the bug tracker.
I have also created a video when I use when I train people on how to migrate from J2.5 to J3.x with the different method and that show that.
http://youtu.be/Ip1edGkdY7w
Remark: The video shows the case with J2.5 to J3.2.7 (due to PHP version < 5.3.10)