Better PHPnuke upgrade strategy !

Nuke Cadet Joined: May 27, 2003 Posts: 8

Hi folks !

As i got more and more involved in nuke stuff and using all these blocks and modules i like nuke on one hand. But on the other hand i begin to hate it - patching or upgrading to new version is so time consuming that running a site steals very much spare time.

I use some tweaks (NSNGroups, etc) and Modules (EventCalendar, WYSIWYG etc.) which require source code changes. All these changes must be redone while upgrading - an absolut stupid and errorful job.

Has FB or anyone else of the nuke-experts thought of a better upgrade strategy? I think it will be easy to incorporate necessary changes of the core code and manage them by flags at least.

Is there some development in this direction and what is the shedule ?

Thanks in advance !

Posted: Sun Jun 15, 2003 8:47 am

Keep in mind FB works with PHP-Nuke's core and we can't expect him to keep track of the hundreds, if not thousands of modules and add-ons that exist, much less guess which ones are being used by who.

Nuke Cadet Joined: May 27, 2003 Posts: 8

I have that in mind, but IMO a better upgrading strategy is essential to Nuke. FB should provide the basics only. (there is no direct contact possibility as he cancelled the forums)

One of the most disturbing points is this flat user/groups/rights management. Therefore some modules have to patch core code.

I claim that there must be a strategy that module designers don't need to touch core code.

Perhaps the mentioned CVS system can be a solution at least, because the module developers can work in their own modules.
My minimum whish is that there exists a setup surface to switch these modules on and off (like that one used in module administration). This will (in conjunction with a CVS repository) guarantee that the module designers patch well known code and the user can choose between different BBs or different calendars or WYSYWIG editors.

Wounderful world i'm dreaming of ?