Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handling "Your project.yaml file was created for different versions of Craft" errors #4914

aaronbushnell opened this issue Sep 11, 2019 · 1 comment


Copy link

commented Sep 11, 2019


I'm on the latest version of Craft 3.2.x and I have set useProjectConfigFile to true in my config file. The project.yaml file is created without issue, but I noticed schemaVersion is set to 3.1.27 (even though I'm on version 3.2.x).

If I make a small change in my project.yaml file and refresh the control panel I see the following error message.

Your project.yaml file was created for different versions of Craft and/or plugins than what’s currently installed.

Craft CMS currently installed has the schema version of 3.2.16 (expected 3.1.27)

Try running composer install from your terminal to resolve.

I have tried the following but none of these resolve this error message:

  1. Run ./craft project-config/rebuild
  2. Delete composer.lock and vendor/ and run composer install

I did notice that the config column in the craft_info table has an object that looks like this:

  "edition": "pro",
  "live": true,
  "name": "My Site",
  "timeZone": "America/Indiana/Indianapolis",

Should the schemaVersion be updated?

Additional info

  • PHP version: 7.1.26
  • OS version: Darwin 18.7.0
  • Database driver & version: MySQL 5.7.27
  • Image driver & version: GD 7.1.26
  • Craft edition & version: Craft Pro 3.2.10

This comment has been minimized.

Copy link
Contributor Author

commented Sep 11, 2019

It seems like this is no longer a problem locally if I call the updateCraftVersionInfo() function in a random module I have setup on this site.

I'm guessing that ensures the schemaVersion in the craft_info table under the config column is up-to-date?

Is this the best way to resolve this or are there some gotchas I should be on the look-out for here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.