[geeklog-users] including javascript in blocks
geeklog-users-admin at lists.geeklog.net
geeklog-users-admin at lists.geeklog.net
Sun Jun 15 15:57:09 EDT 2003
PostNuke was one of a few forks formed by a huge fallout among
PhpNuke developers. Last year, it had its own fallout where the
majority of its developers walked away. Since then, PostNuke has
lacked direction and hasn't made much progress on its core code.
They had been evolving their code to where each release was
drastically different which was very hard on users. All the
themes and modules were breaking badly on each new release. It
required module/theme developers to do major rewrites each time
instead of just minor tweaks. In a way it was good they slowed
down to a full stop. The bad thing was they promised the next
major code revamp would be out first quarter of this year. It
wasn't until about a week or two ago they finally told people why
the promised release never materialized. They lost a huge amount
of code which they say was due to hard disk failure but was
really because yet another developer walked away. Things haven't
progressed as they originally envisioned.
PostNuke has some features I wish Geeklog would adopt. Many of
the modules are very nice too. I think the module developers are
the real reason users have kept an interest. The majority of the
modules are not using the API though so they aren't hooked into
the site's search, stats, etc. Some include their own separate
search capability.
When I tried PostNuke, it ran extremely slow when safe_mode was
on. Even with it off, it ran slower than Geeklog. If you're
running a site where all the info is either viewable to the
public or admin it's an okay system. If you want to do fine
grain security, forget it. Their security system is awful. Well,
it does work, but it is so damn hard to understand. Most people
either don't touch the default settings or have to ask each time
they want to do something. The html to create pages is
interwoven in the code. If you want to create a unique new
theme, you either have to fiddle with code or install one of the
template plugins which are not compatible across each other.
Every time I used the control panel, I wanted to tear the code
apart and completely redo it. There were many things that didn't
seem in the right place to me or could have been done better.
Although Geeklog lacks some of the features, I never had the same
urge. Personally, I think it would benefit us to do a survey
across the different CMS' to see what features others had now to
get ideas on how to improve our own.
As for the guy who thinks PostNuke is hands down the best, let's
see if his attitude changes if they can ever get the next major
revamp completed and released. They have a phased plan which
entails several major revamps for them to reach their 1.0 goal.
John
-----
Date: Sun, 15 Jun 2003 10:13:06 +0700
To: geeklog-users at lists.geeklog.net
Subject: Re: [geeklog-users] including javascript in blocks
From: geeklog-users-admin at lists.geeklog.net
Reply-To: geeklog-users at lists.geeklog.net
Dear Geeklog-ers,
Yesterday someone posted this article on
http://news.schoolforge.net (aka
opensourceschools.org) claiming, without substantiation, that
post nuke was
superior. If you have a moment to lend a critical eye to the
exact claims and
respond, I'd be grateful:
http://opensourceschools.org/article.php?story=20030614125833623
Sincerely,
David
Long-time satified Geeklog customer
More information about the geeklog-users
mailing list