“One of my non-profit Web sites, VarLinux.org, ran on my
modified version of the PHP-Nuke weblog package from the site’s
inception in March 2001 until late November 2002. I chose PHP-Nuke
as a starting point because I was very impressed with it. However,
the more I learned how to use PHP, the more I realized that
PHP-Nuke was not only a tangled mess but that I had made it even
worse with my modifications. A year later, I was faced with the
fact that VarLinux.org was not only lame because it was based on
PHP-Nuke, it was also showing its age. It lacked features of other
weblogs, and still lacked many of the features I had intended to
add to the site.“If I were going to fix the code, the first thing I would do
would be to make it an object-oriented system. I toyed with the
idea of converting my code into OOP-based code, but I concluded
that if the PHP-Nuke code base from which VarLinux.org began was at
one time worth the effort to convert into an object-oriented
system, I had mangled the code enough to make it a waste of
time.“So a few weeks ago, I decided that I would replace the mess
that VarLinux.org had become. I stumbled upon two almost identical
packages, X-oops and E-Xoops. Both are portals, which are expanded
versions of weblogs. Both are use object-oriented PHP, hence the
name X-oops: eXtensible Object Oriented Portal System. The
additional ‘E’ in E-Xoops is supposed to stand for
‘e-business…'”
LinuxWorld: X-oops, I Did It Again
By
Get the Free Newsletter!
Subscribe to Developer Insider for top news, trends, & analysis