This came up in #1238...
@behindthepage in https://github.com/backdrop/backdrop-issues/issues/1238#issuecomment-142...
... I think paths should be checked when views or layouts are being installed. I think it is more likely to duplicate a path when installing a view or a layout than having conflicting config file names and this too can be solved with a bit more code during the copying of the config files. Maybe we can change the new path to duplicate_0 and set a message during install.
@quicksketch in https://github.com/backdrop/backdrop-issues/issues/1238#issuecomment-142...
Let's make an issue for this one in particular. I think we may be able to do a check, but doing a validation before installation may be difficult because each type of thing makes a menu path differently. It's only when they're all consolidated into
hook_menu()that you have the full list. And then each module could have duplicates within it as well (two views at the same path, two layouts at the same path, etc.)
Recent comments
Thanks!! Easiest for me to just give permission for anon users to see the admin theme. That worked. It's just for this one page.
Link field in a Content Type is malformed for annonymous user- Permission issue?
It looks like the screenshot of what you show it should look like is the admin theme whereas what they see is the front end theme. By default, such users won't have permissions to see the...
Link field in a Content Type is malformed for annonymous user- Permission issue?
I've added a new recipe. The recipe has no PHP code. It has two module dependencies (one of those depends on another contrib module and both depend on core modules that are normally enabled)...
The Future of Configuration Recipes for Backdrop CMS