1

I am using the latest version of Craft CMS with 'useProjectConfigFile' enabled.

My development process involves creating/updating Craft settings locally, committing this to Git and then deploying to production. The changes are then sync'd the production Craft CMS fine.

For some reason I have a Global set in the production CMS that doesn't exist on my local version.

Should this be removed when the config file is sync'd up? Any reason why it isn't not syncing correctly?

Pedro
  • 1,148
  • 4
  • 16
  • 35
  • Does it recognize any differences on the production side? You can apply the changes in Craft CMS when recognized (CMS > Utilities > projectconfig). – Mr. Sam Nov 11 '20 at 15:52

3 Answers3

0

You have to sync the configs by hand in the cp of craft cms. Then they will be applyed.

alexanderbuergin
  • 1
  • Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Oct 09 '21 at 05:27
0

You could apply project config settings automatically during deployment via the craft console commands

./craft project-config/apply

Otherwise you have to manualiy apply the new settings in the craft control panel:

enter image description here

KSPR
  • 2,212
  • 4
  • 29
  • 46
0

You can try rebuilding the config with the help of this command.

project-config/rebuild

It rebuilds the config.

Dotsquares
  • 755
  • 1
  • 2
  • 10