[#11282] - [Regression][fix]Migration from 2.5.28 to 3.6 returns Fatal errors & reverts #9655
- Fixed in Code Base
- 24 Jul 2016
- Medium
- Build: staging
- # 11282
- Diff
- zero-24:revert9655
- Success continuous-integration/travis-ci/pr The Travis CI build passed Details
- Success JTracker/HumanTestResults Human Test Results: 2 Successful 0 Failed. Details
User tests: Successful: Unsuccessful:
Pull Request for Issue #11117 .
Summary of Changes
Reverts #9655
There reason is simple. The new file that calls the post update deletion of the files get not called if you update from 2.5 to 3.6 ther for this needs to stay in the script.php too.
Testing Instructions
install 2.5
Update to 3.6
see the issue
Notice: Undefined property: LoginController::$input in ...administrator\components\com_login\controller.php on line 36
Fatal error: Call to a member function set() on null in ...administrator\components\com_login\controller.php on line 36
roll back to 2.5
install the update to 3.6 with the changes in this patch (or use this update server: http://www.jah-tz.de/downloads/core/list.xml)
there should be no issues on updating.
@wilsonge please have a look here if this can go into 3.6.1 too as exactly that happen what you guess in the original thread: c864a01
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration Components |
| Labels |
Added:
?
|
||
I have tested this item
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11282.
| Title |
|
||||||
| Status | Pending | ⇒ | Ready to Commit | ||||
RTC. This solves the issue.
This has to go imho in 3.6.1
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11282.
| Labels |
Added:
?
|
||
I just wanted to thank @zero-24 for this information and provide the error message I was receiving which was different. I was doing a migration today for an old site from j2.5.28 to j3.6 and ran in to a similar problem. The only difference was I received the following error message:
Fatal error: Call to a member function isAdmin() on null in /plugins/system/stats/stats.php on line 87
When I used your update server the migration worked successfully!
I was not using the Statistics module but it was enabled in the extension manager. I first tried disabling it and then when that didn't work I restored the site from backup, disabled it once again, then uninstalled it, and still the problem remained. That is until I used this fix for the migration! Thank you again!
| Status | Ready to Commit | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2016-07-24 22:09:15 |
| Closed_By | ⇒ | wilsonge |
| Labels |
Removed:
?
|
||
if i use this update server("http://www.jah-tz.de/downloads/core/list.xml"), joomla says: "Download of update package failed".
Is it correct that in the Options pane, i select "Custom url", and in the custom url textbox, i type: "http://www.jah-tz.de/downloads/core/list.xml"?
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11282.
FYI. I have uploaded this just 13 days ago and now we have more than 100 Downloads on that package that was for testing this PR only?! I'm going to remove this update server now. I hope you all have swiched back to the default update server after using mine else you will never get any update anymore!
Correct. So we changed it so that 2.5.x goes to 3.5.1 then 3.5.1 to 3.6.0 then 3.6.0 to whatever after updating joomla update. It's in the notes here: https://www.joomla.org/announcements/release-news/5666-the-joomla-3-6-1-update.html
It's super horrible. But it's the best we can do :(
yes, it seems so.
so the migrate/upgrade path from 2.5.28 is:
- 2.5.28 > 3.5.1
- 3.5.1 > 3.6.0
- update joomla update component
- 3.6.0 > latest version
@brianteeman can you give us more details? And move that to a new issue so we can debug and fix the issue? ;)
it didnt happen when i tried again ;)
hmm can you share the details in a new issue or via mail regardless so I can double check that case. As the updater is a important thing in our system I think we should analyse any errors that comes up even if we decide / found out that it is not a issue we can / need fix or it just popup random.
I have tested this item✅ successfully on 8c9b0f8
ok, no more error.
Thanks
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/11282.