-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to upgrade to the next TYPO3 version? #7
Comments
Will check it, have some ideas... I guess you currently have an OpCache issue means after a |
@rowild found the bug, the links are created wrong in case they already exist. This worked for me as temporary workaround until the script is fixed:
|
Closing with PR #8 |
Thanks for your PR. I like to keep the issue still open because there is a real bug in my script which needs to be addressed too. |
Ah, ok. Let me know when you need a tester. One thing I observe is that the script always leads to the install tool. So whenever I stop the project at the end of the day (ddev stop) and start it the next day (without doing any updates, just simply starting it again to keep working on it), I will end up in the install tool. |
Oh, forgot to add a closing statement to the PR #8 so I'm going to close it manualy now... |
It would be great, it the repo could also describe how an upgrade an existing project to the next version of TYPO3 and pre-requisites as well as the consequences to be considered.
Simply changing the requirement in ddev's
config.yaml
does not seem to suffice.This is what I did:
ddev export --gzip=false --file=db_backup.sql
ddev poweroff
.yaml
files in the.ddev
folder except forconfig.yaml
config.yaml
with the newTYPO3_MAJOR_VERSION
(10 in my case) (and adaptTYPO3_MINOR_VERSION
if necessary)ddev start
At this point TYPO3's front is opened, and it throws an error pointing to the TYPO3 v10.4.21 resource:
However, when switching to the install tool, it shows that the just updated project is still running on TYPO3 v9.5.31.
I would have proceeded like this:
ddev import --src=db_backup.sql
None of that makes any difference at this point.
I am most likely doing something very very wrong here :-/
Any chance to provide the steps? I'd be happy to poor them in sentences and provide a PR for the documentation.
The text was updated successfully, but these errors were encountered: