I was thinking about this idea, where I could create a module that would have a bunch of different areas that would control various things on the site.
for example setting a background, or selecting documents to display in a menu, or items to use in sidebar, that kind of stuff.
Currently I’m using a resource I name settings, and have a special template and tvs for that, and then the other documents pull these settings from there. It seems a bit on the crude side and I have this feeling that maybe a module would be able to do this better or look less crude.
Is there any validity to this?
Has anyone tried something like this?
Quote from: daspoda at Feb 24, 2010, 11:21 AM
I was thinking about this idea, where I could create a module that would have a bunch of different areas that would control various things on the site.
for example setting a background, or selecting documents to display in a menu, or items to use in sidebar, that kind of stuff.
Currently I’m using a resource I name settings, and have a special template and tvs for that, and then the other documents pull these settings from there. It seems a bit on the crude side and I have this feeling that maybe a module would be able to do this better or look less crude.
Is there any validity to this?
Has anyone tried something like this?
A Module would definitely look less crude. The down side of a Module is that it would be much more difficult to translate to MODx Revolution, should you choose to install Revo.
BTW, if these are commonly used site-wide settings, you might consider adding them to the system_settings table. They would then be easily accessible anywhere (in any template, chunk, resource, or included CSS file) via system settings tags [(SettingName)] and available to snippets and plugins with $modx->getOption[’SettingName’);
