Skip to content
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

Migration issue going from 3.4.3 => 3.5.2 #91

Open
jeremyfrank opened this issue Feb 28, 2020 · 2 comments
Open

Migration issue going from 3.4.3 => 3.5.2 #91

jeremyfrank opened this issue Feb 28, 2020 · 2 comments
Labels
Bug Report Something isn't working

Comments

@jeremyfrank
Copy link

I think there may still be an issue in the latest migration file, but I'm not sure exactly what it might be. Similar to #89 and #87.


We recently did a batch of updates, including the following:

  1. update Craft 3.3.20.1 => 3.4.8
  2. update Spoon Plugin 3.4.3 => 3.5.2

Things went smoothly in my dev environment, but upon deploying to our staging environment, the Spoon migrations failed.

> add column groupSortOrder smallint UNSIGNED AFTER `context` to table {{%spoon_blocktypes}} ... done (time: 0.064s)
> add column sortOrder smallint UNSIGNED AFTER `groupSortOrder` to table {{%spoon_blocktypes}} ... done (time: 0.065s)
Exception 'craft\errors\MigrateException' with message 'An error occurred while migrating Spoon.'

When deploying a second time, migrations succeed, but then project-config/sync failed with the error:

Applying changes from project.yaml ... error: Changes to the project config are not possible while in read-only mode.

I then set 'allowAdminChanges' => true and re-ran ./craft project-config/sync and it succeeded.

I set allowAdminChanges back to false (the original setting) and did another deploy to staging. Both migration and project-config/sync steps succeeded without any issues.

@baileydoestech
Copy link

baileydoestech commented Mar 9, 2020

We are seeing the same issue (identical version updates)

image

@ghost
Copy link

ghost commented May 18, 2020

We are having this issue too, getting the same error as @jeremyfrank.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Report Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants