Your project.yaml file was created for different.... Craft CMS schema version of 3.4.11 (expected 3.3.3)
Open
Nobody has claimed this yet.
bug
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
Hello hello,
Have just attempted to enable project config on a project I have inherited and getting this old favourite....
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.4.11 (expected 3.3.3)
SEOmatic currently installed has the schema version of 3.0.9 (expected 3.0.8)
Try running composer install from your terminal to resolve.
I've managed to fix this locally by running composer install but I can't work out how to get my staging server working now :(
Can anyone advise?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the project.yaml schema versions and the installed Craft CMS and SEOmatic versions described in the report. Compare the staging server with the local environment and inspect the Composer installation there. Done means project config can be enabled on staging without the version-mismatch error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100