Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

shockme (2685)

  reversethis-{gro.dnuowtixe} {ta} {kcohs}
AOL IM: stephenhargrove (Add Buddy, Send Message)

If you really must have more information about me, see my home node [] at PerlMonks [] or my journal [] at

Journal of shockme (2685)

Monday November 17, 2003
09:17 PM

CMS, Wikis and Perl

[ #15827 ]
At the office, we use PostNuke for our Systems Group's documentation portal and announcements. We also use PHP Wiki for various purposes, but mainly for daily journals and general "how to" documents.

Many moons ago, we used PHPNuke. At that time, I wrote a small module that was basically a checklist. However, I didn't port it when we migrated to PostNuke, and haven't really thought that much about it. Especially since no one had bitched about its absence.

Until today. Now it's a must have.

PHP Wiki plugs into PostNuke very nicely. But getting it operational under PHPNuke isn't that easy. And it's not well documented either. I had it working where I could access it directly (http://document_root/modules/phpWiki/index.php), but accessing as a module wasn't happening. All I ever got was a blank page.

I was going through PostNuke's documentation on creating modules ... good lord, man. It quickly became apparent that I didn't have time to "do it the right way".

So, I hacked up a Perl script that will access the PostNuke cookies to determine permissions, etc., and present the checklist. It's a hack, no doubt. But it's working quite well. Once I have a little more time, I'll revisit the PostNuke documentation and do it correctly.

Justin barfed at school today. No fever. No weirdness. Just puke. Lori picked him up at lunch and took her back to work with her. He's all kinds of pissed that he couldn't go out and play tonight ...

Posted from, comment here.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.