[KLUG Members] CMS Systems

[Adam bultman]

I'm afriad that here, I can only respond in the negative.

The company I work for uses webgui (www.plainblack.com/webgui) for
content management; and all I can say is that "It's the most horrible
thing since anything"

It fills some of your requirements: external authentication (we use
ldap), extendability (you can add your own new modules), it's written in
perl,and works with linux/mod_perl/apache.

It's problems:
1. It's piss slow.
2. The mysql database is a mess
3. The way it stores data on disk is horrible
4. Upgrades happen way too frequently, and are difficult to perform (and
are risky), and very often the phrase" complete rewrite" exists and
things get abandoned.
5. The code is sloppy
6.  It doesn't scale, no matter how much it says it does.
7. In order to be properly "supported" by plainblack, you need to adhere
to PlainBlack's totally nonstandard, totally hairbrained filesystem
hierarchy (which adheres to no standards)


So, there you go. Avoid webgui. 

Adam

Adam Tauno Williams wrote:

><aside>Is saying "Systems" after "CMS" [Content Management Systems] redundant? 
>It has always bothered me to say "RDMBS Systems" (again the "S" is "System")
>but "RDBMSs" seems wrong and "RDBM Systems" also seems wrong.</aside>
>
>I need to put up a website to facilitate some things but I want to spend close
>to zero time doing it (the website isn't the point, the information is).  So
>I'm shopping around looking at the dizzying number of web CMS systems on
>Freshmeat.  I looked especially at x-oops because that one was presented on at
>a KLUG meeting by our own Mr. McGovern.  It seems to do 99.44% of what I need:
>articles, news, files, etc... maybe an occasional survey just for kicks.
>
>But I figured I'd ask the esteemed KLUG members@ list if anyone here has any
>thoughts, recommendations, horror stories.
>
>My requirements:
>1. I don't care what-so-ever what database it uses, since this will sit all
>alo1ne on its own box.
>2. It has to support an external authenticator, at least LDAP, but it would be
>best if I could plug in my own (via JASSO in Java, or an assembly in .NET, or
>just overloading a class in PHP;  I don't much care about the 'how' so long as
>it doesn't involved hacking the core of a package so my changes get whacked by
>any upgrade).
>3. A solution in JAVA (Tomcat), PHP, or C# is fine.  Just because I know these
>three and they tend not to blow up on me when some obscure assembly in some
>distant dependency gets updated/modified.
>4. Work on Apache/LINUX (of course).
>5. Have some mechanism for adding
>modules/components/{whatever-you-want-to-call-them} as I'll need just two or
>three 'vertical' features.  I want to spend my time on these and not all that
>other stuff.  Even something as simple as a way to embed a URL via an IFRAME
>and pass a list of parameters out of the CMS is fine (like OpenGroupware's
>template system,  if you have had the distinct pleasure of working with that).
>
>Adam Tauno Williams
>Network & Systems Administrator
>Morrison Industries
>Grand Rapids, Mi. USA
>_______________________________________________
>Members mailing list
>Members at kalamazoolinux.org
>
>  
>