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
I hope so too.... Thanks very much for the quick response, and have a Happy and productive 2026!!
Base table or view not found upgrading to 1.32.0, TRUNCATE {cache_book}
Good to hear you have sorted it. We haven't seen anything similar, so hopefully that is a one off.
Base table or view not found upgrading to 1.32.0, TRUNCATE {cache_book}
That fixed it, must have been something odd when the database was imported.
Base table or view not found upgrading to 1.32.0, TRUNCATE {cache_book}