Best approach to saving extension settings for multiple sites?
Development and Programming
Hey guys,
I haven’t seen any modules / extensions that store different settings for different sites using the MSM. Obviously this would be a great addition to LG Better Meta and I want to include it ASAP.
I’m not sure about what the best approach is on this one. I could create a new table just for the settings (which seems like overkill) or I could save the settings for every site in a single associative array, saving the settings as normal.
Anyone got any ideas on the best way to approach this?
Dev team? 😊
Cheers Leevi
Leevi, wouldn’t it be best not to rely only to MSM sites? As you know, there are numerous other ways to develop multiple sites within one EE installation - and all would profite from thus enhancements. Therefore, I’d choose to have different sets of settings (dynamically, not limited to a fixed number) and call them via a parameter in the tag … some sort of array or else. Obviously, it would be possible to have one set of setting the “default” one, so that the parameter would be optional and no change to existing sites would be needed.
And another thought: If the parameter name could be choosen to be related/identical to the MSM site name or ID, that might make the use within MSM even easier.
Just my .02$
.Markus
Okay, after rethinking my own ideas, it seems the MSM could need a bit more work ideally: Only that settings might be visible that are specific for that MSM site - but honestly: as long as the SCM and other modules aren’t seperating their settings and don’t even allow multiple sets of settings, I’d be more than happy with every module and extension that just allows to store and select multiple sets.
.Markus
I’m concentrating on MSM installations at the moment because they are the quickest and easiest way for users to create multiple sites.
It would be great if you could create unlimited variations of settings and assign them to many sites using which ever multiple site method you choose. However this isn’t an option for now.