project-config sync/rebuild errors with missing fields
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
Following a Craft 2 upgrade, I'm able to run craft project-config/rebuild, which succeeds.
There are certain fieldtypes that have no match – they remain in project.yaml, and show red in the CP.
I would assume, that running craft project-config/sync --force immediately following rebuild would always succeed, but in this case it doesn't. I get errors about missing field classes for the fields that no longer have types.
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 reproducing the Craft 2 upgrade scenario, then run craft project-config/rebuild followed by craft project-config/sync --force. Trace the missing field-class errors for field definitions that remain in project.yaml; done means the documented sequence completes successfully or handles those unsupported fields without errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100