Closed vkamelin closed 11 months ago
Anybody here?
This is working as expected.
When admin changes are disallowed (allowAdminChanges
is set to false
), the project config is intentionally set to read-only.
If you hit that error during a migration, it probably mean that you ran composer update
on a dev environment, pushed the composer.lock
changes, without actually running the update’s migrations. You should be able to fix it by running php craft up
locally, so the same migrations get run there (where admin changes are allowed), and then Git-push and delpoy the updated config/project/*
files.
What happened?
Description
php craft update all
Steps to reproduce
php craft update all
Craft CMS version
4.3.5
PHP version
8.2
Operating system and version
Ubuntu 22.04
Database type and version
MySQL 8.0.34
Image driver and version
No response
Installed plugins and versions
-