-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Upgrading to new version - what a mess #11799
Comments
Could you share these "EXTRA_FILE"? (not the files itself only the warning) |
Maybe related to #10677. I also got the "parsing response failed" initially when updating from 13.0.6 to 14.0.2. I proceeded by manually setting 'maintenance' => false in the config.php file. Then the update finished. |
I tried setting maintenance to false and retrying the upgrade...didn't work. Only thing that worked was manually triggering php updater.phar. I don't have the list of the "EXTRA_FILE" anymore....but it was all pointing to files inside the core folder (from the JSON error output). I scrapped my old installation and just reinstalled it from scratch. These type of things shouldn't be happening on stock installations...a lot of people are having issues upgrading. |
The error message is: The following extra files have been found:
ocm-privider is actually a directory, that contains one file: index.php See also this screenshot: #10677 (comment) |
resolved in #10677 |
I was trying to upgrade to 14.0.3 from 14.0.1 today through the web interface and it got stuck at the "parsing response failed".
I tried a variety of solutions from google, none of which worked.
Then I tried manually updating by invoking php updater.phar, it worked but then the web interface complained about tons of "EXTRA_FILE" files being found....which I couldn't actually find in the folder.
My 14.0.1 installation was a stock installation, nothing customized other than the data directory being in a different location (the permissions and the configs were set correctly). How can the upgrade fail on a stock installation??? Was this even tested before it was pushed out??
The text was updated successfully, but these errors were encountered: