You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Upgrade from 6.4 to 6.5 broken with latest version #28
Just as a side note, in case others might come across this too:
The changes for the /public directory are breaking when upgrading Shopware from 6.4 to 6.5, resulting in public/index.php being deleted (and probably some other side-effects). As a workaround, use the older version 0.1.9 of the web-installer.
As 6.4 is out of date, I did not open an issue here, but wanted to give a hint for others.
changed the title [-]Just as a side note, in case others might come across this too:[/-][+]Upgrade from 6.4 to 6.5 broken with latest version[/+]on Jul 31, 2026
I will try to create that reproducer, but will take some time ;) currently working on other (paid) things, but found this with an old shopware installation.
For me it was reproducable all the time when having a non-clean 6.4 installation, using the web-browser way (via settings menu) and NOT using the CLI way. Using the previous 0.1.9 always works, where $this->recoveryManager->getProjectDir() was used instead of $this->recoveryManager->getInstallTargetDir() probably works different for my installation.
Activity
danny-althoff-applogik commentedon Jul 31, 2026
😉 probably better title:
"Upgrade from 6.4 to 6.5 broken with latest version"
[-]Just as a side note, in case others might come across this too:[/-][+]Upgrade from 6.4 to 6.5 broken with latest version[/+]shyim commentedon Aug 4, 2026
danny-althoff-applogik i could not reproduce this on my own. Could you maybe provide an small reproducer?
danny-althoff-applogik commentedon Aug 5, 2026
I will try to create that reproducer, but will take some time ;) currently working on other (paid) things, but found this with an old shopware installation.
For me it was reproducable all the time when having a non-clean 6.4 installation, using the web-browser way (via settings menu) and NOT using the CLI way. Using the previous 0.1.9 always works, where
$this->recoveryManager->getProjectDir()was used instead of$this->recoveryManager->getInstallTargetDir()probably works different for my installation.Will report back once I have a reproducable way.
shyim commentedon Sep 2, 2026
Hey,
I will close this Issues as it's inactive for a while. Feel free to create a new one when you have new details
danny-althoff-applogik commentedon Sep 2, 2026
Hi, Sorry for the late feedback.
I was not able to reproduce this every time. I suspect there was something else broken on my end :) sorry for the noise, no need to open this again