When we converted fields to config in https://github.com/backdrop/backdrop-issues/issues/178, we implemented a direct conversion as much as possible. While this maintained a lot of compatibility, it also kept the scattered configuration locations. Right now field module stores its config in several places:
- Each field has a config file (field.field.field_image
)
- Each instance of that field has a config file (field.instance.node.article.field_image
)
- And each bundle has its display settings in a config file (field.bundle.node.article
)
Combining these into fewer files is a long-term goal, but inevitably some of them must be separate because the field configuration isn't part of the content type and can reused in other types.
One potential way to make importing/exporting content types easier is to expand the single import/export page to include a checkbox for "include all fields" when exporting a content type. This checkbox could be form_altered() in by field.module (or even built into config.module directly). Checking it would AJAX-update the export to include all the related config files for a content type as a JSON array.
The import screen would detect the import of multiple config files, run the validation as normal, then stage the selected files all at once. Reviewing the diff and finishing the import would complete the process.
Recent comments
It is an admin theme that's based upon the bootstrap 3. Maybe it's missing a piece to act as an admin theme?
Add blocks filtering problem
Thank you, Martin and Olaf! I had a feeling that there might be something out there already :) I will check all three options (I will look at porting modules) and report back which one...
Filter by text in "message" in /admin/reports/dblog
The Views Watchdog module for Backdrop "extends the Views module and allows to create custom lists of log entries". On Github, there is also a Wiki page with information about available fields,...
Filter by text in "message" in /admin/reports/dblog