-
-
Notifications
You must be signed in to change notification settings - Fork 551
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
[3.1] Problem during upgrade in multi-site Statamic\UpdateScripts\UseDedicatedTrees #3377
Comments
Can you provide |
Sure:
There are no settings for the API in .env |
Thank you. |
Can you provide the whole stack trace? You should see it in storage/logs/laravel.log |
Here you go:
|
In case it's relevant, these are also from the upgrade command:
|
Interesting in the output you've just shown it says that you've upgraded from 3.0.38 to 3.0.39. Not 3.1.
Can you provide your |
That's weird:
I can undo all changes using Git and try again to see if it solves it. |
Yeah give it another shot. I can get it to fail with the same error if I revert one of the bundled config files to what it was in 3.0. But... if you've upgraded to 3.1, it wouldn't be like that. 🤔 Weird! |
I reverted, removed the vendor folder, fresh install that worked, upgrade failed again with the same error. It looks like it's upgrading:
Which file creates the problem so I can replace it and try again? |
Is it that same |
Yes exactly the same. Trace:
|
A couple of things: In your original issue:
Do you mean you upgraded other sites to 3.1 successfully? Or you mean that you've upgraded other sites to any version in general? Could you try upgrading again, and paste all the output of your composer command from your terminal? |
Oh, also. Do you have anything in your global composer config related to Statamic? ( |
We have currently 4 Statamic sites in development due sometime next month, so we decided to do an early upgrade to 3.1. 3 of them worked just fine, this one is giving this error.
Nothing there, just one line for Laravel Valet. Console log:
|
After the upgrade can you show the contents of |
Here you go:
The site's own |
Yeah that looks fine. I'm stumped. 🤔 Got any addons installed? |
Nothing, it's as vanilla as it gets! Maybe I have something broken in some Collection's structure? The site is not that big so I can always manually copy structures in |
Could you zip the site (pre-upgrade) and send it to support@statamic.com ? |
I was able to replicate this issue. It's because your config is cached. We might be able to fix this, but for now, run You shouldn't caching your config locally. Or if you're on production, then you probably shouldn't be updating on production. |
I hit this error also. |
Bug Description
Trying to upgrade a site to 3.1 I got this error and my structures did not move correctly into content/trees. Other sites, again with multi-site and API enabled upgraded correctly.
How to Reproduce
Not really sure.
Extra Detail
Environment
Statamic version: 3.1 Beta 1
PHP version: 7.4.11
Install method (choose one):
The text was updated successfully, but these errors were encountered: