I can see the answers provided for Drupal 8 here: https://drupal.stackexchange.com/questions/188817/how-to-prevent-devel-m...
Which if any of these methods work with Backdrop CMS? Are there other methods to consider?
Weekly office hours
Bring your questions to our weekly virtual office hours, every Wednesday. Everyone is welcome.
Recent topics
Posted 4 hours 54 min ago by (mad) in How-To and Troubleshooting
Posted 1 day 6 hours ago by Graham Leach (Graham Leach) in Other
Posted 1 day 16 hours ago by (mad) in How-To and Troubleshooting
Posted 1 day 17 hours ago by (mad) in How-To and Troubleshooting
Posted 2 days 16 min ago by Robert Garrigos (robertgarrigos) in How-To and Troubleshooting
Recent comments
Sorry if this got posted twice. For some reason it didn't seem that the post was working? Anyway I've given the view the machine name but it's not an option in the string when I...
Machnine Name missing in tpl strings in Views Theme: Information
Also, typically, this pattern "views-view-field--front-page-feature--new-front-hero--title.tpl.php," is broken as follows: views-view-field: common to all field templates...
Machnine Name missing in tpl strings in Views Theme: Information
Can you post an image of the view and what's showing on the Theme: Information UI?
Machnine Name missing in tpl strings in Views Theme: Information
Hello @herb, I think your way of describing it is quite elegant. Speaking for myself, I find rooting around for settings to be quite the drag. A nice feature of the /admin/...
RFC: Granular Module Functionality Enable/Disable Checkboxes?
I think a use case would be helpful in me understanding your question. Of the top of my head, it sounds like what you are looking for are module-specific settings. Each module can "own"...
Comments
That's a good question. I don't think there's a method at the moment other than manually enabling/disabling modules. There's no Config Split and the Backdrop drush config export command can only export everything. https://github.com/backdrop-contrib/drush/blob/1.x-0.x/commands/config/b...
You can add an issue there if you wish for the feature.
Something like config split wouldn't help in Backdrop because module status is not stored in configuration, it's in the database. What are the solutions for this in Drupal 7? We should be looking to those to find a comparable solution for Backdrop.
In D7, I played with the Habitat module. If module status is stored in the db though, perhaps I should just handle this in my deployment script..