Skip to content
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

Closed
rowild opened this issue Oct 11, 2021 · 6 comments
Closed

How to upgrade to the next TYPO3 version? #7

rowild opened this issue Oct 11, 2021 · 6 comments
Labels
bug Something isn't working

Comments

@rowild
Copy link
Contributor

rowild commented Oct 11, 2021

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:

  • Backup the DB with ddev export --gzip=false --file=db_backup.sql
  • Run ddev poweroff
  • Delete all .yaml files in the .ddev folder except for config.yaml
  • Configure config.yaml with the new TYPO3_MAJOR_VERSION (10 in my case) (and adapt TYPO3_MINOR_VERSION if necessary)
  • Run ddev start

At this point TYPO3's front is opened, and it throws an error pointing to the TYPO3 v10.4.21 resource:

Call to undefined method TYPO3\CMS\Core\Cache\Frontend\VariableFrontend::require()

in /var/www/html/typo3_src-10.4.21/typo3/sysext/core/Classes/Package/PackageManager.php line 207

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:

  • Import database with ddev import --src=db_backup.sql
  • Run Database update
  • Run Updater

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.

@gilbertsoft
Copy link
Member

Will check it, have some ideas...

I guess you currently have an OpCache issue means after a ddev restart your project should most probably work again with the new sources.

@gilbertsoft gilbertsoft added the bug Something isn't working label Oct 12, 2021
@gilbertsoft
Copy link
Member

@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:

  • stop the project ddev stop
  • change TYPO3_MAJOR_VERSION in .ddev/config.yaml
  • remove htdocs/typo3_src, htdocs/typo3, htdocs/index.php and htdocs/typo3temp
  • enable the install tool ddev exec touch htdocs/typo3conf/ENABLE_INSTALL_TOOL
  • start the project ddev start
  • run the upgrade wizards in the install tool

@rowild
Copy link
Contributor Author

rowild commented Oct 14, 2021

Closing with PR #8

@rowild rowild closed this as completed Oct 14, 2021
@gilbertsoft
Copy link
Member

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.

@gilbertsoft gilbertsoft reopened this Oct 14, 2021
@rowild
Copy link
Contributor Author

rowild commented Oct 14, 2021

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.
This is not a problem at all for me. It is just something that I observe. Usually, when I start working on a page, I open the backend, not the install toll.

@gilbertsoft
Copy link
Member

Oh, forgot to add a closing statement to the PR #8 so I'm going to close it manualy now...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants