Set default group for new registrations?

Guardian2003 · Posted: Tue Dec 09, 2008 2:54 am

You have it the wrong way around. It is not RavenNukes (tm) job to be compatible with bad or inefficient code but the job of third party developers to keep up with the current standards instead of perpetuating the cycle of re-using someone elses very old code.

Although RavenNuke should work with most older modules, there are a few things that might prevent them from working.
If you can be specific about any issue you have with a specific module then I'm sure someone can advise you what the problem might be.
So far, I have only found one module that would not work with RN2.3 and that was because it was a very old module that used the $dbi database abstraction layer. A warning that $dbi was deprecated and was not to be used was contained in every nuke version for at least the last 4 years.

montego · Posted: Tue Dec 09, 2008 6:16 am

One thing to also keep in mind about using older scripts (besides security issues) is that PHP-Nuke itself modified the way certain things worked, in the admin area for example, which essentially "breaks" many of these older modules. Since RavenNuke(tm) was built upon PHP-Nuke 7.6, to be fair and true to your comments, pureliving, about "modules i had on my previous php nuke website, i can no longer get to work with raven nuke. Why is this?", one would have to try and run the module on 7.6 as well as on RN to judge. I have numerous non-core RavenNuke modules and can tell you that not one of them could not run on both.