The module I am building currently will rely upon a lot of very large and fiddly views, which are currently being saved into the /files/configblahblah/active directory. Because I need to "transport" these views easily with the rest of the module, and manage the source code, is there some way I can get Views to accept that they are kept in my module subfolder, CRUD them there?
Accepted answer
Comments
@onyx - I do not have a good answer for you.
Remember, BackdropCMS now allows you to store all of your config in the database, if you prefer.
https://docs.backdropcms.org/change-records/swappable-config-storage
I don't know that this will solve your specific problem, but I thought I would mention it in case you are unaware of this relatively new feature.
Thanks, I wasn't aware of that. That goes back to D7 ways! I do like that these config files are JSONish, and so I can edit them easily by hand (for doing bulk substitution), which is painful in DB.
Hi @onyx. When you prepare your module files you can add the config for those views into the module folder under config. When someone installs the module then the config is copied into their active and the view becomes available.
Hi @onyx. When you prepare your module files you can add the config for those views into the module folder under config. When someone installs the module then the config is copied into their active and the view becomes available.