versitycobalt
07-13-2005, 09:20 PM
I don't really know what to call the thread but the main idea is limiting the number of modules that show up when editing pages.
At the moment, when you go to edit a page, you have every module listed and then you can simply enabled or disable the modules you want to show on the page. Easy, simple, but crowded.
The one thing I would like to see that would help if you have a lot of modules installed and being used, would be a way of having a module "library". This way, when you go to edit the page, you only see the modules 'assigned' to the page. At this point, you can just enable and disable modules pn a page basis as needed. If you need to add a module, just choose it from the module library.
The module library could work like side by side select lists that you can > or < modules from the library to the page being modified.
This would also solve the issue with people wanting modules in one column on one page and in another column on another because you could chose the column for it to go into when adding them module to the page.
In the adv_pages database table, the current modules column would be replaced with rcol, ccol, lcol column for right, center, and left columns respectively. For keeping track of which modules are enabled or disabled for a particular page, you would just to turn the module number to a negative. Keeping in mind to check whether its a negative or not when pulling from the database and making note of it in an array when building the page.
Just a thought on making CMPS easier to manage and less cluttered.
At the moment, when you go to edit a page, you have every module listed and then you can simply enabled or disable the modules you want to show on the page. Easy, simple, but crowded.
The one thing I would like to see that would help if you have a lot of modules installed and being used, would be a way of having a module "library". This way, when you go to edit the page, you only see the modules 'assigned' to the page. At this point, you can just enable and disable modules pn a page basis as needed. If you need to add a module, just choose it from the module library.
The module library could work like side by side select lists that you can > or < modules from the library to the page being modified.
This would also solve the issue with people wanting modules in one column on one page and in another column on another because you could chose the column for it to go into when adding them module to the page.
In the adv_pages database table, the current modules column would be replaced with rcol, ccol, lcol column for right, center, and left columns respectively. For keeping track of which modules are enabled or disabled for a particular page, you would just to turn the module number to a negative. Keeping in mind to check whether its a negative or not when pulling from the database and making note of it in an array when building the page.
Just a thought on making CMPS easier to manage and less cluttered.