User Functions


There are no upcoming events

What's New

Stories last 2 weeks

No new stories

Comments last 2 weeks

No new comments

Trackbacks last 2 weeks

No new trackback comments

Links last 2 weeks

No recent new links

Downloads last 2 weeks

No new files

Welcome to Geeklog Tuesday, December 06 2016 @ 07:05 am EST

Geeklog vs. PHPnuke: A Brief Review

  • Contributed by:
  • Views:
Several people here have mentioned how they tried PHPnuke, found out how much better it is, and abandoned Geeklog forever. Being curious myself, I decided to download PHPnuke and play with it and find out where they were coming from.

Here are the observations I made of how it is better/worse in comparison to GeekLog..

The Good..

  • Topics and sections are seperate entities, just like on the major weblogs
  • So easy to install, absolutely anyone could do it; the config file only has options relating to the database, and everything else is done invisibly to the user by the system
  • Pretty much everything is configurable through the web interface; no need to edit text files
  • Tons of cool modules, built-in and available with no additional downloading necessary
  • Plenty of very nice themes pre-installed, and many more available to download
  • Makes it easy to add RDF feeds..I was able to easily add feeds from my favorite geeky websites to my front page in under a minute, without having to look up their RDF URL.
  • Advertisement, forum, private message, and journal modules built-in, along with countless others
  • Actually has comment and story rating systems, even if they are broken and not configurable by the admin
The Bad..
  • That 'modules' block is just plain annoying, and the fact that its present on so many phpnuke sites reduces the respectability of yours
  • Comment rating system only worked with a select few versions of didn't work with older versions of IE and every other browser I tried
  • Downright awful regular user account was allowed to rate comments as many times as I wanted, the story rating system's feature to prevent repeat voting didn't always work.
  • Confusing admin system separates admin accounts from non-admin accounts.
Clearly, phpnuke is a very nice system and a powerful rival to geeklog. Now we come to have hardest part: having seen both systems, the soon-to-be weblog admin must choose one. If I were choosing one today, and was forbidden from altering the code of either system to fix annoyances like the ones listed above, I was choose Geeklog because whatever features it has are guaranteed to work right out of the box, and especially because those security-related issues would certainly be abused by my readers to do bad stuff.

However, having the knowledge to fix the problems listed above as I do, the decision becomes much harder and I might just pick phpnuke due to its feature-packedness and the sheer number of extra goodies available.

For my own site, I've already chosen GeekLog for my site while ago, and will stand by that choice.

The following comments are owned by whomever posted them. This site is not responsible for what they say.

  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Anonymous on Friday, December 06 2002 @ 12:35 pm EST
Thanks for the review. These are my thoughts after checking out phpnuke.

The creator of phpnuke took back ownership and is the sole person who makes all the decisions on what gets incorporated into future releases. So, if you need to get into the core code to fix a bug or make changes he won\'t incorporate, you\'re going to see messy spaghetti code. That alone turned me off of phpnuke.

phpnuke does have a lot of modules but how many of those do people really need or are even used by visitors? Many newbies think they must throw everything and the kitchen sink onto their website instead of putting things visitors will use. Anything uploaded onto your site and not used is a waste of disk space. Although it currently has a limited number of plugins, blocks, and themes, the ones Geeklog has available meet MY needs.

I went with whom I thought had a better core product plus great security features. The code here is written in a manner that I found it fairly easy to understand the logic and modify. Since phpnuke, postnuke, etc modules are written in php if there is something they have that I want I can port it over and avoid all the other bloatware.

I think Geeklog does have more room to grow in making it easier and more transparent for people to install the software and to add plugins/blocks. They also could use more folks helping out to develop themes and port over good modules. As far as I see though, they are headed in the right direction. Plus the developers here communicate and listen to the users.

phpnuke is great for those who want a totally out-of-the-box solution and need/want no changes. Those who want to grow sites or tinker around will get frustrated with the spaghetti code and having one person make all the decisions. Whether people like it or not if you plan on running a site with any decent number of visitors, you\'re going to run into problems and have to get your hands a little dirty in the code. For me, I would rather not play with spaghetti.
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Anonymous on Friday, December 06 2002 @ 03:28 pm EST
I have been searching my ass off for a Portal CMS that I feel is user friendly, easly understandable and easy to setup and maintain. I am a windows user so clear documentation is a must for the config files.

In the last week I have installed phpbb2, phpnuke 6, fullymod for phpbb2, mx-systems for phpbb2, clanunitys portal for phpbb2 and I have seen alot in a weeks time.

I need the ability to manage stories on the front page CMS area, also the ability for a post from the message board be posted to the fron page, and its a must that I retain full control over the look and feel, without editing 300 pages of crap, and 83 queries later. ( yes that for you fullymodded)

Geeklog, look F**** killer and If I can get it installed today on my box and test it, I will come back and give total support
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Creator on Friday, December 06 2002 @ 12:51 pm EST
I wanted to add that GeekLog seems to be relatively new as opposed to PHPnuke, which has been around for some time now. Right now it seems to me that the GL developers are concerned primarily with tuning and making perfect the core system, thus leaving development of new features, themes, and the like to geeks who love GL and want to help out.

From my own personal experience, having played with GL and PHPnuke, I find that I prefer GL simply because it is easier for me to build the site I want from a basic install rather than digging through the huge and unwieldy PHPnuke install.

However, I can see how a newbie would prefer PHPnuke since it already comes with nearly everything except the kitchen sink with a basic install.

One thing I'd suggest is that the basic install of GL should include ALL the debugged themes, blocks, and plugins that are available so that the newbie could simply activate those that he/she wants without having to go through the pain of finding them, downloading, configuring, installing, etc etc etc.

Also, for the newbie, I think it would be nice if there was a web-based interface for dealing with config.php upon initial install, much like the way Gallery does with their system. And perhaps a web-based interface for easy editing of themes.

A shopping cart plugin for GL would be the cherry on top of the whipped cream, IMO!

Ok enough wishing!

L. Whitworth

  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Anonymous on Friday, December 06 2002 @ 01:17 pm EST
I wouldn\'t recommend putting ALL the blocks and plugins in the basic install. Perhaps giving a menu of options on which ones you want to include in the download and then making them transparent to install like you recommended would be better. Over time, the number will grow and if you put them all in the intall you\'ll create the same bloated product like phpnuke.
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Creator on Friday, December 06 2002 @ 01:40 pm EST
Not if they aren't activated to begin with! Just include them (along with all the necessary changes to lib-common.php, lib-custom.php, lib-database.php, and/or config.php then add just one more initial story telling the new admin about their existence and where they can go to activate them. It'd still be the same clean install in the first place.

Ok, maybe not ALL of them... Just the most popular ones like the Weather block and the downloads plugin.

L. Whitworth

  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:richschmidt on Monday, December 09 2002 @ 01:53 pm EST
As a newbie myself, just trying to get my GeekLog site up and running, I would LOVE it if there was a distro available with many of the \"common\" plugins, etc, included. One reason I\'d like to power my site with GeekLog is because of the promise of being able to include things like the Weather deal, news headlines, Google search, etc. That fits what we\'re trying to create. The easier that would be for me to do, the better. :)

  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Anonymous on Friday, December 06 2002 @ 01:40 pm EST
I came from PHPNuke to GL. It has just about everything I want (waiting for the forums! 8^), has some great themes, and a good community.
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Anonymous on Friday, December 06 2002 @ 02:19 pm EST
What was your reason for switching?
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Anonymous on Friday, December 06 2002 @ 03:48 pm EST
I started with PHPNuke, then onto Postnuke, then onto Encompass and finally ended up with Geeklog. I was sure glad when I finally found Geeklog as it had everything I was looking for and the code was written in way that I could understand it enough to make modifications.

I was always confused by the whole \"Sections\" and \"Topic\" thing on PHPNuke and Postnuke as I never saw the need for having both of them. The permissions system on Postnuke was also way to complicated.

A feature of Geeklog that I really liked was that you could upload images with your articles and then embed the images in the articles.
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:FlightSimGuy on Tuesday, December 10 2002 @ 07:31 am EST
Think of it this way: the local newspaper\'s medicine section happens to be doing an article on AIDS this case, medicine is the section and AIDS is the topic. Makes sense to me, but perhaps more importantly, the major weblogs do it and I wanna do it to. :)
Once I finish my comment & story eval addon I\'ll see if I can code in this functionality.

That image-grabbing feature is really nice; what would be even better is if it could grab images from WWW locations onto your local server and let you refer to them in the same way. When I find a news article I wanna blog, it would be helpful to be able to grab images directly from it.
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Anonymous on Friday, December 13 2002 @ 05:26 am EST
I guess I always thought of the example you describe as being topic / sub-topic. Example: Medicine - AIDS. I guess it really doesn\'t matter though as it is personal preference. The great thing is that we have the flexibility to change it to whatever our personal liking may be. ;-)
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:ScurvyDawg on Saturday, December 07 2002 @ 10:47 pm EST

I looked around quite a bit before coming upon GL.

I use a third party server that was quite involved in my search. They refused to allow PostNuke and most of the others onto their server for apparently known security issues.

They had zero issues with GL.

GL all the way..

  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Remdotc on Tuesday, December 10 2002 @ 11:09 am EST
Well, there are some other nice vs bad points..

PhpNuke is a pain, even with version 6.0 to Theme, or make unique.
PhpNuke is a pig. 45-60K pages, Anyone not on broadband isnt going to enjoy this, plus the server load the provider isnt going to enjoy

PhpNuke is Boxed: Every phpnuke site i have seen, looks like every other phpnuke site i have seen.

PhpNuke Lacks Security: PhpNuke security system is horrible.
PhpNuke is Slow to update: One developer. Slow to update
PhpNuke Core: Speghetti Code. Non Defined functions, No credit given for the orginal code that ( it is based off of.
So Simple, You have to be dead not to install it.

Bonuses of PhpNuke, Not Listed
PhpNuke is forkware: Aka PhpNuke,PostNuke,NukeKid... Trillions of websites all supporting Nuke
PhpNuke, is mindless. So simple, You have to be dead not to install it

--Minuses of Geeklog--
Its still a new kid on the block, Not as many plugins. Not as popular

--Bonuses of Geeklog--
Well commented code. These guys work for EDS?
Not as popular, So sites look fresh
Developer Support is great. Usually one of the developers will try to answer your question in a few days
Content Security is that of some very expensive CMS\'s
Open Source: If there is a bug , a plugin, or question, the developers pass it on to the community

After looking and testing numberous CMS packages(, Cofax, Nuke--(fill in the blank) , EzPublish, Thatware, Dacode, Dropal, Typo3, Odonivia, Mambo ) Only one code comes to mind for my site, which i have spent months on changing, tweaking, and testing for its launch date later this month. Thats geeklog. None of the others have all the features I wanted.

Whilst my site will not look like your typical GL page, rest assured the core is geeklog

  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Anonymous on Tuesday, December 10 2002 @ 07:31 pm EST
I come from a background of \"never use anyone else\'s code\" and for the past year or so have been trying unsuccessfully to write my own interface that included everything I wanted.

I had an actual list of things I had to have and was SHOCKED to find that all of them were included with Geeklog.

High fives and kudos all around to the Geeklog team - you have saved my site from certain despair. Or disrepair...

Although I needed mucho help from my geek husband and could have never worked around the numerous issues that threatened to force me to throw GL into the can, I am beyond pleased now that it is up and running.

Now if only I can manage to customize a theme so it looks like my own site I will be on my way to heaven.
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:moyashi on Saturday, December 14 2002 @ 08:34 am EST
ugh, haha, I\'m just like the rest.

Actually, I\'ve been watching GL for over a year.

To be honest I\'ve been playing with postnuke too for the past 2 weeks and I keep coming back to GL. Sure there are few things I\'d like to see but I have this gut feeling pulling me back to GL ever few hours of fiddling with postnuke.

However, I\'m getting sick of all this whishy-washy-ness, trying to decide which to go with. I wish somebody would just force me to go with one. hehe, I\'m sticking with GL most likely.

- Why does everybody have to go off on forking tangents?
- I would love to see GL take the lead and bring up talks with some other script developers. Nothing against anybody in particular, but I just can\'t figure out why everybody is re-inventing the wheel? (phpAdsNew, oscommerce, phpBB/invisionboard, blah blah script) So much valuable time could be saved and used on bringing more goodies to the base system.
- true multi-lingua abilities. (hmm, postnuke is a bit better than GL o this)

This isn\'t meant to be a rant, it\'s just the past 3 weeks has going in circles in trying to find a solution for my ideas. haha, best bet would be to study programming once and for all.


Cheers and just gotta say GL is really really a decent system and crowd to be with.
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:FlightSimGuy on Sunday, December 15 2002 @ 08:57 pm EST
Heres a hypothetial scenario that\'ll hopefully make it clearer to you why people fork..
Say, I wanna extend GeekLog to include new features that that delve too deep into the core, and can\'t be done with the API. So I modify the core directly and attempt to release those modifications as modified files (the custom users.php, comment.php, etc.) GeekLog developers refuse to accept them into the standard core. The next official GL release comes along and by this time, I\'ve extended my library to, say, 6 features, none of which can be done with the API.
Now to get them to work with the new version, I\'d have to make a complicated series of modifications (remember, these new features were released as modified files from the GL core). And the GL developers still refuse to include any of them in the next release, preferring to focus on refining the core rather than new features.
Then I say enough. I make my own release with all 6 features integrated and call it, say, BlahLog 1.0. From that point onward I continue on my own path with my own goal of adding as many cool features as possible to every release.

..And there you have it. :)
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:Anonymous on Monday, April 07 2003 @ 01:05 pm EDT
Like some many projects, the Nukes are trying to do too much. It is preferable to be a better system then to be number one and most poplur.

GL has everything I have needed and is a dream to develop for.

Rock on
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:vegeta9870 on Saturday, February 21 2004 @ 10:28 pm EST
Another thing you should have had on the bad end is how much space that thing takes up! I had a 30mb free accont and it was about 27mb full!

If you wish to taste the ground feel free to attack me.
  • Geeklog vs. PHPnuke: A Brief Review
  • Authored by:rjrufo on Thursday, November 04 2004 @ 08:59 pm EST
I found this article while searching for something else and had to add
my own comment.

My extended family, aunts, uncles, cousins, etc. wanted a better way to
keep in touch since we are spread out all over the country (USA), and
they asked if I could develop a web site to do that. I primarily did static
web sites, and didn't know squat about how to build what they wanted,
so I started looking into a CMS solution. I tried several other CMS
systems, including PHPNuke. After finding Geeklog, and having done my
research with the others, I decided that Geeklog was the way to go.

That site has been up for a year this month (November, '04), and has
been extensively customized. If it wasn't for the way Geeklog was built, I
don't think I'd have been able to customize it the way I have.

I'd also like to thank the developers of Geeklog for the very fast response
times to the questions I've had regarding different issues I've come
across. I doubt that any of the other CMS system developers would have
done the same.