I'm looking for a Content Management System with a fairly specific set of
features to run a non-profit website on a Linux (Debian) based server. I've
spent most of the weekend digging around freshmeat, sourceforge, hotscripts
etc, and tested a lot of stuff. PHPX was looking good but I just can't get
it working :-/ So here's what I'm after:
PHP+MySQL+Apache based content management system with:
- Calendar
- Discussion boards (moderated and non-moderated)
- Ability to let others (registered admins etc) submit news/articles.
- 'Membership' system: registered users get e-mail of upcoming events, can
customise the content displayed etc.
- The usual security related stuff (PHPNuke has too many holes for my
liking).
I played with slashcode but didn't feel like hand coding a calendar system
:-| So over to the group. What do you suggest??
--James
http://www.Postnuke.com -no calenda(would be an addon module somewhere)
however install a M$ NET Frame work
server next to it and in 1 click you have this feature plus a CMS in 50
clicks --Ha ha
phpbb with the addon CMSfront from sourceforge.net (not so good looking)
sourcefore.net and overkill of CMS i guess (not a security hole in
it.Sourceforge .net CMS is like fort fucking Knox(no Im not pommy)
ezipublish--a bit of a scam but may be workable un Linux
sourceforge.net is my choice...but runs with perl
Have you thought about Zope (www.zope.org) it rocks!
It's not strictly a CMS but with a few modules like CMF it can do anything.
You can front it with Apache or use the built in ZServer and it can work
with a number of databases including MySQL or it's built in OODB.
We had a similar requirement for a not-for-profit (http://www.wire.org.au).
After lengthy research and evaluation we used the following open source
(free) components:
1. WebGUI content management system http://www.plainblack.com/webgui
This has proven to be an excellent CMS. It has an extensive range of well
thought out and powerful functions and is simple to use. Includes:
forums/discussion boards, user management/security, user customisation more
stuff than you can poke a stick at. It can claim stability, maturity, heavy
ongoing development. The support is so so as the developers generally don't
support forum unless they buy support, but we have never really needed it.
If you start using it feel free to swap notes with me.
- PhProjekt groupware
We have also been impressed with this software. It is well designed,
simple, stable and functional. The interface is pretty bland but we look
for function and stability ahead of bells and whistles. Provides:
- Powerful group calendaring
- Request tracking
- Pretty good preoject management
- Time tracking
- Notes, TODOs
- Contacts
- email
- forum
- chat
The technology for the above is Perl-MySQL-Apache. If you are prepared to
reduce the PHP restriction you will be on a good wicket with this stuff.
Regards,
Adam
> Centurion wrote:
>
>> Hi All,
>>
>> I'm looking for a Content Management System with a fairly specific set of
>> features to run a non-profit website on a Linux (Debian) based server.
>> I've spent most of the weekend digging around freshmeat, sourceforge,
>> hotscripts
>> etc, and tested a lot of stuff. PHPX was looking good but I just can't
>> get
>> it working :-/ So here's what I'm after:
>>
>> PHP+MySQL+Apache based content management system with:
>> - Calendar
>> - Discussion boards (moderated and non-moderated)
>> - Ability to let others (registered admins etc) submit news/articles.
>> - 'Membership' system: registered users get e-mail of upcoming events,
>> can customise the content displayed etc.
>> - The usual security related stuff (PHPNuke has too many holes for my
>> liking).
> We had a similar requirement for a not-for-profit
> (http://www.wire.org.au). After lengthy research and evaluation we used
> the following open source (free) components:
>
> 1. WebGUI content management system http://www.plainblack.com/webgui
Adam,
Thanks for the suggestion :-) You've done a good job with the wire.org.au
site too BTW.
The reason I'd like to avoid too much Perl is tht the hardware we are
running is somewhat limited (P133's with 64Mb RAM). The Perl VMs needed to
run WebGUI (like slashcode) just consume too many resources. PHP is lot
less resource hungry for the low traffic volumes we are expecting.
--James
__________________________
A random quote of nothing:
The lovely woman-child Kaa was mercilessly chained to the cruel post of
the warrior-chief Beast, with his barbarian tribe now stacking wood at
her nubile feet, when the strong clear voice of the poetic and heroic
Handsomas roared, 'Flick your Bic, crisp that chick, and you'll feel my
steel through your last meal!'
-- Winning sentence, 1984 Bulwer-Lytton bad fiction contest.
Not quite true about the resources.maybe you should consider a server 133
/64mb machine SCSI discs ect.It seems threading is your problem and the
reason you run low on these kind of resources.
even running a 1200mhz desktop as a server you see problems with not
enough resource for perl based server applications of which half of it is
the IDE disk drives.
After all they did make machines of this caliber for a reason
and 70% of servers still used today run at speeds lower than 600mhz and
cope quite well.
HP Netserver 133mhz 64mbRAM:
uptime:19 days ,13:46, 24 users, load average: 0.06,0.04, 0.03
Alot of perl,php,file transfer runs on this little machine round the
clock.It works as a file server just as much as webserver and the power
outs are all that put the things on downtime.
Good Luck
Yes this is true, good mod_perl performance apparently requires quite a bit
of memory and you are running very lowly specified hardware.
However, I really do believe that it is worth your while investing a few
hundred dollars in some hardware. A small investment could see your
mainboard, ram, cpu and hard drive upgraded to something that is several
orders of magnitude faster and more importantly removes any limitations as
to what software you choose. You might even be able to scrounge the
hardware from one of the many companies that are throwing out old computers.
I think that using the old hardware and resigning yourself to extra hard
work is something of a 'false economy'. The time battling with old hardware
and low level software is much better spent designing, implementing and
testing end user functionality.
Just a thought.
Regards,
Adam