Closed tomdavies closed 4 years ago
Hi @tomdavies,
That's interesting, i'll have a look if I can prevent this issue from happening when updating to Craft 3.4. If not i'll update the docs as you suggested
Hey @tomdavies.
I encounter the same error and tried your solution, but I keep getting the same error.
Any chance you can tell me the steps you followed to update to Craft 3.4?
Thank you.
Hey @rmdiaconu,
Can you try updating to Craft 3.4 with neo set as "spicyweb/craft-neo": "2.6.5.1",
within your composer file first? You can then revert neos version within composer and then update it.
Steps:
Hey @pvldigital, tried your solution and the following error occurred:
`Performing one update:
- craft 3.3.20.1 => 3.4.13
Backup the database? (yes|no) [no]:n Skipping database backup. Performing update with Composer ... error: An error occurred
Output:
Loading composer repositories with package information Updating dependencies Your requirements could not be resolved to an installable set of packages.
Problem 1
Hi @rmdiaconu,
How are you updating to the latest craft version? Are you using the command line (if so what was the command)?
Can you also send over the composer file to plugins@spicyweb.com.au so I can have a look?
@pvldigital We had the same issue as @tomdavies (hi btw :-) ) and I can confirm that locking to Neo to 2.6.5.1 in the first steps solves the problem.
It also solves another problem, which might happen when coming from before Craft 3.4.0 because the Neo migration of 3.7.5 tries to delete a row from the separate projectconfig table, which does not exist if Craft's migrations have not been done before migration Neo.
I ran into this today and followed these steps without any issue.
Before the update, I was at Neo 2.5.10 and Craft 3.3.20.1
composer update
@hiasl @avr good to know those steps worked for you. I'm currently working on a fix for this so any future updates will not have this issue.
Just to close the loop on this: updating to 2.6.5.1
first worked for me too. Many thanks @pvldigital. Feel free to close this issue if you have another place you're tracking the required change for a long term fix
Latest version v2.7.8 has a fix for this issue. Updating from an older version to Craft 3.4 shouldn't cause any issues.
Hey,
I have a suggestion for an addition to the docs.
I found I was getting a failed craft (core) migration when attempting to upgrade from Neo 2.5.10 => 2.7.3 at the same time as updating from Craft 3.3.20.1 => 3.4.11
I traced it to the fact that
./craft migrate/all
will run Craft's own migrations before plugin migration. However because the 3.4 update triggers element resaves, these resaves in turn result in Neo 2.7.3 calls before Neo's own migrations have run, making everything explode (stack trace below for completeness)The solution is to run
before running
Other information