Closed timmyomahony closed 1 year ago
I encountered this again today. The tip from the above linked issue worked:
rm -rf storage/runtime/cache
./craft project-config/sync --force
I noticed that during this time, there was an old plugin that I still had installed locally that had been removed in the project.yaml
. After running the sync command I saw:
> ./craft project-config/sync --force
Uninstalling plugin "env-sync" ... error: No plugin exists with the handle "env-sync".
Applying changes from project.yaml ... done
It might be related to the plugin not being installed
Closing unless if rears its head again. I haven't encountered this in a long time.
I've experienced this issue when pushing/pulling databases with
remote-sync
. You update a field or section/global on local then push to staging (or another dev machine). After pulling latest changes and restoring the database via the interface (which uses./craft restore/db
under the hood) the new fields aren't reflected.I think this is an issue with how Craft is handling
project.yaml
as well as the restore function. The issue has been logged here:https://github.com/craftcms/cms/issues/5952