Persistant "Component class 'benf\neo\Field' belongs to an uninstalled plugin (Neo)" error
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.6k
- Forks
- 705
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 134
Description
Description
This ticket is related to this Neo ticket, but I'm posting it here also as it may be a more general related Craft CMS issue.
I have a project that required multiples branches, and multiple databases (as a few settings where stored in DB only, not in project config).
After merging from one branch to another, I got this error:
Component class 'benf\neo\Field' belongs to an uninstalled plugin (Neo).
It's not the first time I got it and can easily fix it like this:
composer require spicyweb/craft-neo
When it's not enough:
- I try again with
composer remove spicyweb/craft-neobefore the other one - I run
./craft plugin/enable neo
Or alternatively:
- Uninstall plugin from
/admin/settings/plugins - Install plugin from
/admin/settings/plugins
Unfortunately, I still got the same error that the plugin is missing.
Even after running:
./craft project-config/rebuild
./craft project-config/apply
In /admin/settings/fields all my Neo fields are still showing benf\neo\Field in red color text.
Any idea how to fix this?
Other information
- Neo version: 2.12.1
- Craft version: 3.7.27.1
- Multi-site: yes, but without propagation
- Is eager-loading used? No
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 missing-plugin state using the reported Craft and Neo versions, then compare the project-config rebuild/apply commands with the plugin enable and install flows. Check the admin Settings > Fields view to trace why Neo fields still appear as benf\neo\Field and confirm that the uninstalled-plugin error and red field labels are gone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100