[#30358] - [4.0] Feedback: Migration to V4
- Closed
- 16 Sep 2020
- Medium
- Build: staging
- # 30358
Steps to reproduce the issue
- Migrate from V3.9.20 to V3.10 Alpha
- Try to mgrate to V4 Beta 3
Expected result
Step1: successfully Migration to V3.10
Step2: migration to Admin-Backend successful,
Management for setting site template and extensions via backend is possible
Actual result
- Migration to 3.10 works fine - no errors detected
- Migration to V4 destroyed installation
- process did not migrate to new "atum" template causing failure of admin backend (got message "template failed")
- error500 (expected) on frontend - could not be recovered (e.g. by using template "casiopeia" for frontend) as backend failed.
Additional comments
Besides restoring backup of system there would be a recovery way, if at least migration of backend to V4 would be successfully.
It may ease migration to V4, if process would disable all installed extensions, where it is not ensured that they do support V4.
joomla-cms-bot
- | Labels |
Added:
?
|
||
@dgrammatiko The update is not fixed yet. In addition to PR #30333 in J 3.10, it needs another change in J4 to remove the same statements from the J4 update scripts, otherwise the update fails, which is currently the case. But when I remove that in J4, then updating from 4.0 Beta 1 or 2 or 3 to a future Beta 4 (or nightly) fails. I've pinged @wilsonge about that for a decision what to do, but no reply yet.
Quy
- | Labels |
Added:
Information Required
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2020-09-16 18:09:31 |
| Closed_By | ⇒ | Quy |
@jschmi102 The migration path was broken by #30192 but fixed with #30333
You need to d/l the nightly 3.10 ( https://developer.joomla.org/nightly-builds.html ) to have a successful migration