Add contrib and custom directories to the docroot/modules directory.
How do people feel about this? We added a files directory for easier site installation.
I personally strongly dislike when I inherit a site and the contrib and custom modules are all mixed together.
We could make it easy for the site builders and developers to use best practices by having this structure in place out of the box with README.md files in each explaining what types of modules belong in each.
Are there reasons we should not do this?
GitHub Issue #:
1996
Recent comments
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists