hi all

before i go completely mad...

I have site with a huge number of modules. The site's in 5 sections and the same set of around 30 modules are duplicated for each section.

There are many annoying things about this:

1. You cant select modules belonging to only one section (unless you create a template for each section, which i havent)

2. Since titles are displayed, you cant (for example) code the section ID in to the module title and select on that (i.e. all modules with the section prefix).

3. Since each section has a module with the same title, in the same module position, I see 5 apparently identical modules in the module manager and i can only tell them apart by editing them and seeing which menu entries they're displayed on...etc

Shall I just say that this is bloody tedious?

I tried an advanced module manager but it failed at the starting gate. I have not the time to experiment with others, although I know I should. Frustratingly, there is also no potential for this to be solved in 1.6. And yes I do know the info is available in the menu entry, but that's no more efficient to edit.

If only you could classify modules in to groups.....

Anyone got a you-beaut solution?

thanks
Dex

Aw c'mon folks, I'm desperate...!

Also, by the way, I would also need something that says
(a) group modules together by classifying them as a section and then
(b) for every module in this section, publish it for every submenu entry of that section's top level menu entry.

So that when I've stupidly forgotten a menu entry (one menu entry, but for all 5 sections), I dont have to edit 150 modules to assign them to this extra one menu entry.

I cant be the only person who finds this slightly tedious???

Can I?

Or am i just going mad?

Hi Dex - I don't know a module that does this or a you beaut solution and you probably have already thought of this and discarded it - but maybe set it up directly via the database so section 1 mods were id'd 100, 101, 102 etc and section 2, 200, 201, 202 etc etc - then youd'e know better where you were at eth backend and then you could manually run queries to the database when you needed to make changes on mass..... I know this isn't an easy solution, but I think if I faced this problem after a couple of hours setting up it would make teh future easier!

Hopefully someone has a far better solution though!!

crikey Audra,
desperate times when i need to run queries....altho a good idea and some top lateral thinking involved
thx