[Post-nuke-users] Hello, and some wish lists.

[Crutcher D. <cru...@da...>]

Hey.

Looks like I'm setting up a postnuke site at work. I'm liking what I'm
seeing of the code base, but there are a few things I'm gonna need, and
I'd like to here what the community thinks about implementation
techniques before I go off and write it. (To increase the probability
that I won't have to maintain a fork).

We have about a dozen large sections of data which we want to put up,
and they will be maintained by different people, who will want to take
different levels of involvement with the modular base, and html
complexity. So I need the sideboxes to come and go based upon what
section the user is in, preferably while they still have access to the
rest of the sites modules.

I am aware of hackish ways to do this. I could overlay several sites,
and have them share some tables, but not others. I'd rather not do this,
it is high maintinance, and I think there is probably a better way.

If the code was changed so that there was a global $CURRENT_AREA, and
every URL returned by a module returned
"http://host/path/file.php?Area=$CURRENT_AREA&..."
and main file extracted CURRENT_AREA from Area, and checked to see if it
was a valid area (perhaps a list of areas in config.php, with a default),
then we could start writing modules which used this idea.

Is that an acceptable way to do this? I need it, so I'll do the work, if
everyone is okay with it. Otherwise, how should I do it?

-- 
Crutcher        <cru...@da...>
GCS d--- s+:>+:- a-- C++++$ UL++++$ L+++$>++++ !E PS+++ PE Y+ PGP+>++++
    R-(+++) !tv(+++) b+(++++) G+ e>++++ h+>++ r* y+>*$