-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Can't migrate from Craft 2 -> 3.1 AWS #38
Comments
Are you using "dev-craft-3.1" in your composer as version for this library? See #35 |
I'm getting this as well, I am using dev-craft-3.1.
|
Well, as a rule I'm trying to keep active in dev versions of things out of my composer & stick to at least 'beta' stuff. I know it's only a little change and easy to change back, but historically I've found that I sometimes leave dev versions in (because I'm spinning many plates) - and then end up pulling in some code that is ... less than ideal...because I'm not following every repo, I don't always know a release has happened etc. It may just be I don't understand composer well enough to feel confident, too. Speaking more generally, I guess I just kinda have an expectation that first party plugins of fairly fundamental importance (i.e. volumes) & their migrations from previous major releases - will be made compatible & substantially tested before the release of a major platform update. Given I was following along with Craft 3.0 and Commerce 2 right up to the latest beta of that & all was well (in terms of migrations) - the amount of breakage that came with the final release of Commerce 2 requiring Craft 3.1 has been a bit of a nasty surprise... |
@bossanova808 point taken. In hindsight, 3.1 was too big of a release and we should have split that one up in at least two different releases - soft-deletes and project config. Pushing out one large release, especially with features that were developed side-by-side really hamstrung our testing efforts this time. As for this specific issue.
That's probably exactly why it's occurring. This is because the setting names have changed and you are setting a |
Once a faulty migration is ruled out, I'll cut a release. If that's indeed the |
Hi Andris - thanks for getting back to me (and apologies for grumpiness). I definitely don't have urlPrefix in my volumes.php....and I did not have an issue with the migration to 3.0 (I was not using volumes.php with that, I've recently created it along the way to trying to solve this...) This is my volumes.php right now:
|
(and the migration fails with or without that file in place) |
@bossanova808 will test. Have some ideas about what might be going wrong. As soon as I have this sorted out, I'll cut a release. |
No problems - thankyou. I do have a support ticket in with a link to a db etc...if that helps |
I do note in the asset sources table there is still urlPrefix etc in the settings saved in there...it's like the migration for the plugin install is not running (the code in But I will leave you to it - it's late here and the wife will get cranky with me if I hold up the evening too long... |
Fixed via 3cb4190 |
We'll try to get a release out today that adresses this. |
Thanks Andris - tested this jut now and it indeed appears to solve the issue. Clicking on the volume settings gives me an error about missing expires, but I suspect that I just need to add that to my volumes.php to solve that...will try that out as soon as I am near an appropriate computer. |
After my initial migration, I log into the CP and this plugin is in an uninstalled state (as it is not present in C2 I guess). When I then attempt to install, it gives the error and the CP is then unreachable:
This occurs even though I have my settings for the volumes in .env and config/volumes.php
The text was updated successfully, but these errors were encountered: