[KLUG Members] CMS Systems

[Adam Tauno Williams]

> Since you have already looked at xoops, cool, that is where we are headed for

It seems to be the premier package, but I haven't looked at the code
yet.  Some <cough>most</cough> PHP packages are a complete train wreck
inside.  With Horde and PEAR being notable exceptions.  That xoops uses
PEAR is very encouraging.

> our needs for the Electronic Software Distribution logging / report server as
> well as public web sites. One team member is already digging through the xoops
> code as well as modules we are interested in, fixing bugs, commenting, etc...
> and will be sending that contribution back to the project team. Many of the
> modules are not as well integrated as they could be - using their own code and
> not common xoops shared code so for the modules we need that is being cleaned

<rant>Web developers and shared code?!  The two are almost antitheses of
each other.  Ask a web developer to spend 15 minutes reading the
documentation on some class library and he'll pitch the docs in the
trash, run off, and spend four weeks writing his own classes - or else
he just won't use classes and will just jam all the code inside the
markup.  I can't even begin to tell you how many times I've been down
that road.</rant>

I'm very happy to hear about potential fellow users on this list - xoops
seems to depend on web forms / wikis for support - and forums/wikis make
me break out in hives.

> up. They don't always generate HTML code which meets the spec of
> validator.w3.org so we are fixing that as well. Their generated code is not SEO
> (search engine optimization) friendly so that will be corrected as well.

SEO isn't a convcern for this project - if google never finds the site
that is OK with me.

> It is a very good starting point for us, saves us a lot of time.

Exactly what I am looking for.

> Audit logs will be added. Some sort of LDAP authentication for sure.

I found several posts indicating that 2.2 supports LDAP authentication.
But the docs don't seem to reflect this.  In fact, many of the links
regarding docs are currently broken.  That is not encouraging.

> Additionally there is a DB2 CLI interface for PHP, so we will be working on
> updating the xoops database object to use both the existing interface and also
> support targeting a DB2 back end which we will be using. To me LAMP is almost
> fine... MySQL \= "sleep well at night".
> http://us2.php.net/manual/en/ref.ibm-db2.php

I was rather surprised they didn't use PEARs own database abstraction
layer, since they seem to use PEAR all over for other stuff.

> A little / specific technical update post KLUG presentation! ;-)

:)