Your project config YAML files contain pending changes.
Description
Keep getting this message even after running a ./craft project-config/apply and even ./craft project-config/apply --force.
Your project config YAML files contain pending changes. Review
Steps to reproduce
- Have a lot of YAML changes.
- Attempt to apply them.
Additional info
- Craft version: 3.5.16
- PHP version: 7.x
Weird. Can you please send a database backup, your Composer files, and the contents of your config/project/ folder into [email protected]? We can look into it further from there.
@TonyDeStefano
Hello. I'm coming here with a similar case. Have you guys found out the culprit?
Not sure it ever got fixed, I moved on to a new company that doesn't use Craft.
@brandonkelly I've been having this issue intermittently for years. Sometimes, I get it immediately after updating a plugin via the GUI. Other times I might get it after git pull && composer install && php craft up.
Here's the variation I'm seeing on a client's site right now; it always looks like this, with the empty curly brackets and categoryGroups, although I don't know if the GUID is always the same:
@proimage Weird. Would you be able to send a database backup and your config/project/ folder over to [email protected]?
@proimage Weird. Would you be able to send a database backup and your
config/project/folder over to [email protected]?
Sure thing, but the DB backup is too large for an email. ~~Got a preferred method of file transfer?~~ Nevermind, I just sent it as a Google Drive link.
@proimage was this ever resolved or the root cause determined?
@proimage was this ever resolved or the root cause determined?
@westhouseit Yes, actually... sometimes the config/project directory gets these junk-looking folder names... In the sample I sent to P&T, the names were ._4oY and ._gmb. Remove those and the issue should be gone. Note that they might be hidden from view.
@proimage I just wondered about a root cause so that perhaps the creation of these temp directories can be prevented.
@proimage I just wondered about a root cause so that perhaps the creation of these temp directories can be prevented.
We had this issue a while back, it happened when Craft didn't have permissions to write in config/project folder.
@proimage I just wondered about a root cause so that perhaps the creation of these temp directories can be prevented.
We had this issue a while back, it happened when Craft didn't have permissions to write in
config/projectfolder.
Thanks, that's an interesting insight. I'll see if this is the issue if it crops up again.