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
Sounds like the Stripe processor isn’t fully initialising, so the extension tries to call create() on a missing Stripe client. On Backdrop/CiviCRM this usually happens when the payment processor...
Getting Error after submitting event register form By using Stripe Payment Processor
Welcome to Backdrop! For your setup, you’ll want to create a subtheme of Bootstrap5 Lite itself; the Bootswatch styles (like Cerulean) are just presets that B5 Lite loads, and you can “lock in”...
Basic Theme designing questions, using Bootstrap5 Lite
Hi Rob, Welcome to Backdrop! Here’s a quick overview: Subtheming Bootswatch: You should create your subtheme based on Bootstrap5 Lite, not directly on a Bootswatch style....
Basic Theme designing questions, using Bootstrap5 Lite