You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
update Craft 3.3.20.1 => 3.4.8
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.
The text was updated successfully, but these errors were encountered:
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:
Things went smoothly in my dev environment, but upon deploying to our staging environment, the Spoon migrations failed.
When deploying a second time, migrations succeed, but then project-config/sync failed with the error:
I then set
'allowAdminChanges' => true
and re-ran./craft project-config/sync
and it succeeded.I set
allowAdminChanges
back tofalse
(the original setting) and did another deploy to staging. Both migration and project-config/sync steps succeeded without any issues.The text was updated successfully, but these errors were encountered: