Do not allow modules to be enabled at all if they have conflicting config file names with any existing config.

https://github.com/backdrop/backdrop-issues/issues/1238#issuecomment-141...

When the module is enabled backdrop would check that there is no naming issues, warn of any path issues and copy these files into the sites config folder.

I think this would be a good idea in any case. We shouldn't allow modules to be enabled at all if they have conflicting config file names with any existing config.

GitHub Link:

https://github.com/backdrop/backdrop-issues/issues/1242

GitHub Issue #:

1242

Log in or register to post comments

Recent topics

Set title to Node reference

Posted 16 hours 50 min ago by (Mike Kettle) in How-To and Troubleshooting

Errant "configure view" link is visible to anonymous users

Posted 2 days 15 hours ago by (Chrys) in How-To and Troubleshooting

[current-page:title] token in Custom Block

Posted 4 days 17 hours ago by (xorgev) in How-To and Troubleshooting

Recent comments

I also have a problem with the Taxonomy Menu module. I was trying to associate a menu to a taxonomy using the taxonomy menu, and it doesn't work. I thought it was a problem with the website I'm...

Posted 10 hours 12 min ago by (xorgev) on:

Taxonomy menu module is broken

I was gonna say I'll go off and try them options but the simple link looks like the easiest as it took seconds to implement! Didn't really want to manage outside of BD as that requires...

Posted 15 hours 50 min ago by (Mike Kettle) on:

Set title to Node reference

You could have a simple link using this: Or you could make the Content: Nid field link to the content. Give it a meaningful label and you don't need the title field in the View. ...

Posted 16 hours 3 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:

Set title to Node reference