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 Issue #:
1242
Recent comments
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list
If you haven't already, flush all the caches. If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...
custom module not showing up in modules list
Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...
custom module not showing up in modules list