Zikula Community

• **unknown user**
  
  

  • Rank: Registered User
  • Registered: Mar 16, 2002
  • Last visit: May 17, 2003
  • Posts: 1

  Posted: May 16, 2003 - 05:13 PM

  Okay, I've had the left hand who love PHP-Nuke saying it's the end all of everything and on the right hand are the people who say PostNuke does more, and better.
  
  What I want to know is this, what one is the better and why?
  Would PHP-Nuke work on Apache or IIS better, or would PostNuke work smoother.
  
  I have a modest website running on a Windows 2000 Server box with Apache for WWW and various other programs doing all the various other tasks. Nothing other than the OS is from Microsoft and that's how I like it.
  
  Would adding PHP-Nuke to the mix cause me more headaches and if so will PostNuke make me happier with the overall layout?
  
  Please comment and help me onto the path that requires the least amount of Tylenol!
  
  Thanks
  =)

  • 
  •  
• markwest
  
  

  • Rank: Team Member
  • Registered: Mar 18, 2002
  • Last visit: Oct 21, 2009
  • Posts: 6606

  Posted: May 16, 2003 - 10:37 PM

  You're asking on a PN forum so the answers your get will favour PN. Likewise ask the same question on a phpnuke forum and the answers you'll get will favour phpnuke.
  
  I'll try and be as objective as possible by telling you why I chose PN when looking for a CMS 18 months ago and then eventually joined the development team.
  
  PN has a different methodology to phpnuke. PN aims for a lean, stable and flexable core that allows 3rd parties a good framework to build modules. Phpnuke tries to be a lot of things out of the box - some it does well some it doesn't.
  
  PN seeks not to force the choice of modules you have to use. Hence PN doesn't come with a forum module. You may not want a forum, or you may want a different forum. So we don't force you. Forum development is left to 3rd parties. PN is better for this methodology. The core team concentrate on the core.
  
  In PN the modules are truly modular (at least all modules compliant to PN's API standards). All these modules must be completely self contained, files must reside in a single directory in the modules folder. Modules must not alter core files. Modules should manage thier own database tables rather than force the user to manage SQL files or other install scripts.
  
  PN provides a methodology whereby modules can consume functionality from additional module either directly via an API call to the other module or indirectly via hooks (a loose method of module conectivity) thus enhancing the truly modular nature of PN. Modules shouldn't need thier own rating or comment code.
  
  The downside of PN at the moment is that were not there yet. Not all PN modules are API compliant, some have thier own commenting and rating code. Hence this (and other reasons) are why the current version is v0.723 i.e. pre v1.0.
  
  PN took phpnuke and is gradually changing the underlying core code into a flexible CMS framework.
  
  The next version of PN will include a templating solution (Xanthia) allowing for complete abstration of PHP code logic and display logic. This allow you, the administrator, to alter the look and feel of your site without needing to be familiar with PHP code.
  
  In short PN is more modular and hence more stable than phpnuke. We're not there yet but by using PN your 'buying' into a methodology.
  
  I hope this gives you an idea of the key differences (as I see them).
  
  -Mark

  • 
  •  
• **unknown user**
  
  

  • Rank: Registered User
  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 33

  Posted: May 18, 2003 - 03:36 AM

  And wwhen will that update come!??? Do you need economic help to finish it or what is needed to make this project go faster on!??? How does it look right now??? please keep us informed! :)

  • 
  •  
• markwest
  
  

  • Rank: Team Member
  • Registered: Mar 18, 2002
  • Last visit: Oct 21, 2009
  • Posts: 6606

  Posted: May 18, 2003 - 08:23 AM

  CHEETAH

  And wwhen will that update come!??? Do you need economic help to finish it or what is needed to make this project go faster on!??? How does it look right now??? please keep us informed! :)

  
  
  You can follow the progress of the code by a number of means.
  
  1. Getting a copy direct from CVS. See this article for docs on getting the code from CVS
  
  2. Following the task trackers on the NOC.
  
  3. We should have some annoucements and a demo of the new CVS up shortly - I'm getting a copy of our developers site DB as base to work on the demo site this week.
  
  We don't have any mechanisms in place for financial donation. My main limitation is time not money - I don't ever see myself as a full time coder. This is a hobby.
  
  -Mark

  • 
  •  
• **unknown user**
  
  

  • Rank: Registered User
  • Registered: Mar 16, 2002
  • Last visit: Oct 21, 2009
  • Posts: 33

  Posted: May 25, 2003 - 08:01 AM

  markwest:
  
  thx for the links. but still that doesn't make much sense for me who is not 'inside' the project. i can't see how long time it's left to the next release... i can't see what progress has been made and what difficulty it's left to fix before the release may come... and before the next stable release can be out.
  
  Could you give a briefing of the situation and what's next please?
  
  thx! /CHEETAH

  • 
  •  
•  
•  

Users on-line

• 0 users

This list is based on users active over the last 60 minutes.