Upgrading To The Latest Version Of Raven's RavenNuke Distro

Worker Joined: Aug 22, 2006 Posts: 192

Hi fellow 'Raven Nukers',

I began using PHPNuke when this site actively worked on the 'original version' of PHP Nuke Version 7.6 and my first website used PHP Nuke Version 7.6 with a seperate installation of Nuke Sentinel.

I subsequently installed another website using the first version of Raven's RavenNuke Distro Version 2.10.00 and have recently installed a 3rd site but using Raven's RavenNuke Distro Version 2.10.01

I now wish to install another website and learn there is a further latest version of Raven's RavenNuke Distro, which is Version 2.10.02.

As you will understand, I would like all my websites to be running the latest version of Raven's RavenNuke Distro, however I understand that this is no easy task to acheive.

The following is what I understand and I wonder if someone would please verify if my understanding is correct and/or advise what I should do or an easier way around this.

As I understand it, once you have backed up your current website, in order to upgrade to the latest version, you have to either complete a fresh install with the latest package, or run an 'upgrade package'.

However, I understand that if you have made changes to files in your original website, (whether they are simple text wording/spelling changes or whether you have changed various pieces of code, e.g. when you want to eliminate the use of the journal function in a users admin panel), these changes will no longer be 'valid' and you have to manually make the changes again, once your new install or upgrade is completed.

Do I understand all this correctly?

What is your advise.

Much appreciated.

registered · Posted: Sat Sep 01, 2007 7:13 am

emmaphp, the keys are 1) getting the database to the latest, and 2) getting the files to the latest. I'll discuss each below:

1) Getting the database to the latest is the easiest of the two. We provide upgrade scripts to do this as well as instructions. So, as always, take your db and file backups ahead of time just in case.

2) For this, I really recommend everyone to have a copy of their sites local on their PC (if you even want a "runnable" version of it locally, you can install XAMPP), at a minimum with the current files. You can use cPanel to backup your files and then using FTP pull them down.

I now ALWAYS do the following process when upgrading a web site's files:

a) Make sure my local files exactly match production web site (is always the case because I even have them under version control)

b) Pull down the RN package and extract it in a separate directory.

c) With Beyond Compare 2 (you can use Winmerge instead), I do a directory comparison between my local site copy of files to the HTML directory under the RN extracted directory. If using Beyond Compare 2, it is important to use only the "Binary Comparison" method - trust me...

d) c) above will point out every file that is different and you can double-click on each of those and see the differences. You should be able to recognize where the changes are yours vs. what the RN team has done (I actually keep a log of all changes that I make to my scripts so that I don't have to figure this out each time). You can, most likely, just merge the changes with into your local files.

Take not of which files have been removed from the distribution (the comparison tools will highlight these as well), as you will want to manually remove these later as well.

e) Once all of this work is done, since I have a working copy running on my PC using XAMPP, I can even run the db upgrades and test the whole upgrade completely prior to uploading.

f) Upload the db upgrade script to your production site along with either just the changed files, or just re-FTP everything.

g) Run through the db upgrade scripts. Remove them as soon as you are done with them.

h) Test

i) If everything looks good, you are done, if not, you might have to restore your backups (but if you test these out thoroughly locally first, you shouldn't have any issues).

I know it looks like a lot of steps, but each one taken together will keep you out of trouble with a solid repeatable process!

Posted: Sun Sep 02, 2007 5:11 am

Hi Montego,

Although this sounds like a lengthy chore, I do see how being methodical about the process will assist making sure everything is in order, in the long run.

As always, your time and contribution/reply is very much appreciated.

Just one final question though...In addition to me wishing to upgrade my current sites, I am about to begin authoring a completely new site. I need the site running by October 1 and so need to begin authoring and designing it as soon as possible. Should I wait for the new version of Ravens Nuke to be launched (and save myself upgrading), or do you think it will be a while before this is launched/released?

Posted: Sun Sep 02, 2007 9:00 am

I would not wait. There is no 2.10.02 release (bug fixes only). Raven decided to add new capabilities, so we're going to release a 2.20.00 version, but timing is TBD.

Posted: Sun Sep 02, 2007 9:28 am

Thanks Montego.

Now, the downloads section of this website does not CLEARLY identify to me which the latest FULL Raven Nuke package is to download, so please would you advise me of the exact URL/location where I can proceed to do this.

Thanks in advance.

Smile

registered · Posted: Sun Sep 02, 2007 10:58 am

Don't be confused. Raven only has the 2.10.01 package available for download. The packages differ only in how they are compressed. So choose your favorite archive format, download, and enjoy. Smile

Posted: Sun Sep 02, 2007 11:46 am

Ahhh...Yes Yes...I see this now you highlight the point Gremmie Very Happy

I wish it was made that clear by actually saying so in the download section.

Thank you again.

Wave