PHPNuke vs Postnuke
The following comparison is based on my own knowledge and experience
with both systems, I have developed several communities and portals
based on both scripts and this is what I can say of them.
First, it's nice to know where Postnuke comes from:
"Postnuke is a free, open source content management system forked from
PHP-Nuke, released under the GNU General Public License. The Postnuke
project was started because some PHP-Nuke users believed that there
should be a more open development environment than PHP-Nuke had at the
time. They felt that the only way this could be done was to develop
their own fork of the PHP-Nuke project. Postnuke is now a separate
project from PHP-Nuke, sharing very little code (if any) with the
Postnuke - From Wikipedia, the free encyclopedia.
That is, Postnuke is based on PHPNuke code, so the "feeling" you get
using any of them is very similar, although the code behind the tool
has changed a lot since the initial fork. Also, you can read the
previous paragraph as:
"Postnuke is a "more open" version of PHPNuke, developed by a lot of
people around the world, while PHPNuke is being developed by a single
person (Francisco Burzi) which supervises and integrates the
contributions from other developers."
Let's start the comparison:
When I think in PHPNuke, just one word comes to my mind: "easy".
PHPNuke is easy to manage, easy to modify and easy to deploy,
althought it's not very easy to install.
In just one word, Postnuke is "professional", it has been designed by
professional nuke users and PHP developers, it's intended to develop
serious communities and it's focused in security, stability and
PHPNuke installation requires some knowledge of PHP and MySQL, while
Postnuke features an integrated installer which makes it really easy
Postnuke is more versatile than PHPNuke, that is, it allows module
developers to do more with the framework than in PHPNuke.
PHPNuke is tied to the whishes of a single person that can listen to
the community or not, Postnuke is being developed by the community
itself, so integrates many of the features needed by them.
When Francisco Burzi started to write PHPNuke, he didn't know very
much PHP, it was just like a pet project, and still there are portions
of the code that shows that beginning. Althought both scripts features
a lot of the well-known "spaguetti code", Postnuke is being cleaned up
several times to remove unused code and refactored to achieve a higher
Develop themes for PostNuke or PHPNuke are almost the same, although
Postnuke features an internal system to get info about the framework
which makes easier to develop a theme.
It's easier to develop a module for PHPNuke, but because there are
less things you can do in a module
A said before, the Postnuke code has been modified to achieve high
performance, although this cannot be tested unless you run two very
succesful communities with lots of users
Security and bug response time
Postnuke is more secure because the code has been cleaned and bugs are
fixed sooner. There is a community behind finding and fixing bugs,
while to fix a PHPNuke bug, you need to wait until Francisco Burzi
releases an official patch.
My conclusion is that PHPNuke is the best solution for novice users
because it's easier to manage than Postnuke, but if you want to start
a serious community, and you want to be backed up by a team of
developers, I suggest you to use Postnuke, it gives you more freedom
and more power.
Please, feel free to request more info on an specific feature, I will
be happy to answer any of your requests.
Clarification of Answer by
04 Jan 2004 08:28 PST
Regarding addons/modules, most developers make them compatible for
both environments because it's very simple to do it, althought there
are more PHPNuke modules than postnuke ones.
You can find here a lot of postnuke modules:
And here a lot of addons for PHPNuke
Regarding themes, I said on the answer, most themes are compatible or
can be made compatible between frameworks.
Regarding other functionality, I just can tell you that both systems
are the "same", I mean, they share the same functionality, both
systems are content management systems which perform very specific
functions, that is, allow you to create a community, tune it up using
modules/themes and allow you to expand functionality very easily.
If you want more specific "technical" details on any aspect, just let
me know, I will be glad to provide them.