The PostNuke permissions system is half arsed voodoo magic.
I’m working on the Waltham Forest Twins and Triplets site for Cathie in my spare (yeah right) time. To
save me having to write a lot of code I’ve opted for one of the ‘Nukes’. I
went for post nuke as it seemed better supported, the earlier one seems to
be one guy with arbitrary releases, this one has a community of developers.
Anyway I have to write the spec for the site on the fly. e.g. figuring out the access groups and what type of user can view what sort of content, not forgetting that there should be content to view under undefined sections (so I need to define those too)
Off the shelf generic is all well and good, but it’s a bitch to configure
for the new user. Bearing in mind that I’m a web developer with lots of experience I am surprised at how fiddly the thing is to configure. Admittedly the *install* was pretty painless, although it did require a modicum of cmd line exposure.
November 27th, 2004 at 7:48 am
It has it’s beauty, and it’s downfalls. I think that some of the programmers get so into their coding, they make it too complicated for others to trace their code. They can break things apart a bit TOO much, ya know?
The upgrade issue is a double head sword. If it was written by scratch, we wouldn’t have the security support, and constant tweaking. But then we could have serious security breaches based upon what we *don’t* know. (And those are the scary ones!) If we didn’t use Nuke, we wouldn’t have to patch and update it so much.
So what’s with the name “Nuke”? I personally prefer a “no-nukes” policy in my personal life, so that name conflict cuts many times thru a programming session.
The best thing I find with PostNuke, is a developer can do their thing… get the site going, make it cool… and then hand it to anyone with a concept of OpenSource code.
And move on…..