how do i upgrade

Regular Joined: Feb 17, 2006 Posts: 94

sorry i just dont understnd how to upgrade from ravennuke 7.6 2.02 to the latest version. i have read the install guide but only see how to update from say 7.5 to 7.6 etc

do i upload all the new files overwriting the old ones?

if so then what do i do next?

cheers

Sells PC To Pay For Divorce Joined: Posts: 5661

does this help ?

For those of you who are upgrading from an earlier version of RavenNuke(tm) OR are considering migrating from a non-RavenNuke(tm) version to RavenNuke(tm), there are very detailed guidelines available within the HowToInstall manual that is a part of the RavenNuke(tm) 2.10.00 download.

The manual is written in XHTML, so simply point your browser to the index.html page and then use the left-hand navigation menu to go to the Upgrading link.

Posted: Sun Apr 15, 2007 4:52 am

not really because i dont know what i am doing, i dont see a HowToInstall manual

cheers

Posted: Sun Apr 15, 2007 4:54 am

that big howto manual comes with the ravennuke pack...
you cant mis it..

Posted: Sun Apr 15, 2007 5:08 am

its way to confusing for me, i just dont understand at this time. i will have to keep reading learning i guess.

cheers anyway

Posted: Sun Apr 15, 2007 5:16 am

this is the upgrade tut.

From Prior Versions of RavenNuke(tm)
These instructions are for upgrading from version 2.02.02 of RavenNuke(tm) to the latest 2.10.00 version ONLY. If you are on a version earlier than 2.02.02, use the various patch downloads and/or support forum posts to help you get to 2.02.02 FIRST. Once you are on version 2.02.02 AND you have validated that everything is working properly (do NOT skip this step), you are ready to upgrade. Read ALL steps first to get the complete "picture" of what needs to be done and when.

Backup Current Installation FIRST! - This step is always the most crucial. You need to have a clean restore point (files and database) in case something goes wrong. We also recommend that you "test drive" this upgrade process on a local PC or server setup so you get a better feel for the process and have time to resolve any specific issues that your installation might throw your way. There are so many different ways in use today for backing up your site files and database, so the "how" will not be discussed in these instructions. Do NOT ignore this ALL important step (or any others for that matter). You have been warned!

Note Impacts to Your Add-Ons / Hacks - You should be doing this anyways as you make changes to your site. Make sure you understand the impacts to your add-ons and any files that you have "hacked" since your original RavenNuke(tm) installation. Look especially for modified core RavenNuke(tm) tables or modified core script files. You will have to analyze these yourself and ensure that you do not overwrite your changes or somehow get your database out-of-sync with your script files. This is where a good set of change management notes and a good version comparison tool will save the day. Any table that was added new, or new script file that was added, will NOT be impacted by this upgrade, unless somehow, they use the same name.

Extract, Prepare and Upload Files - Here is where you might want to refresh your memory on the steps you took for the full original installation (review the steps of this manual again) so that you take care not to overwrite critical files such as config.php, .htaccess, .staccess, .ftaccess, ultramode.txt, etc. which you have already configured. The file config.php has been modified heavily, so it is recommended that you save off your current version of this and replace it with the one from the 2.10.00 distribution, then make sure it has the right database connectivity and other settings in it. Much has changed in the area of configurability, so please take some time to review the steps mentioned in this manual related to a complete new installation (especially the section on Prepare/Install the Files). The configuration instructions will NOT be repeated here. NOTE: you should NOT have to reconfigure NukeSentinel(tm)! NOTE: If you normally experience difficulties FTP'ng large quantities of files to your server, and if you have a means of decompressing files on the server, you might want to consider compressing the distribution (zip or tar.gz) and ftp'ng the compressed distribution as a single file and then decompressing it there.

Upgrade Core RavenNuke(tm) Tables - From your browser, type http://www.YOURDOMAIN.com/INSTALLATION/rndb_upgrade.php. This will upgrade your core RavenNuke(tm) tables (we'll get to NukeSentinel(tm) next) from 2.02.02 to 2.10.00. It will ONLY touch the core tables and nothing that you have added as completely new. However, if you have previously made changes to these core tables, there is no guarantee that this upgrade to 2.10.00 will work properly. When you run this upgrade script, output will be written to your screen. We highly recommend that you copy and paste this output into your favorite text editor and save it with your other conversion notes. Depending on your personal preference, you may also wish to print it and save it in your conversion notebook. Having a record of the changes that were made, as well as any errors or exceptions, can be invaluable if problems occur at a later time or if you need to post something in Forums asking for help.

Posted: Sun Apr 15, 2007 5:28 am

ok thanks, will need to read really carefully as i dont really have a clue what i am doing

cheers

Posted: Sun Apr 15, 2007 5:34 am

well funny you say this.... Laughing

im sure you will manage...cause you have your current site installed ?
Your doing its maintenance ?...etc...

just reading it isnt so hard....
or just pay someone to do it for you.....
but i hope you understand that we cant say it any better then its already written in that howto upgrade..

registered · Posted: Sun Apr 15, 2007 2:00 pm

If you have not installed any hacks to the original RavenNuke(tm) code, the upgrade is very painless. Just uploading of all the files and running two database upgrade scripts. That easy!

Posted: Sun Apr 15, 2007 3:50 pm

what do you nean by hacks? 3rd party modules etc?

Posted: Sun Apr 15, 2007 5:42 pm

Yes, that's what he means. Or possibly altering the code yourself or altering any of the database tables.

I hope that you have a test system to try all this out on. If not, and if you have a system that people rely on, you might want to make a copy and try the changes there. That would give you the liberty to experiment and to learn and then you apply those lessons to your "real" system.

Posted: Mon Apr 16, 2007 6:19 am

Quote:

Or possibly altering the code yourself or altering any of the database tables.

Yes, the above is what I meant. I am less concerned with third party add-ons unless they altered the core database tables.

It sounded to me like you may have had a pretty straightforward installation, so maybe you have not modified any of the core script files? If so, the upgrade is a breeze.

Posted: Mon Apr 16, 2007 9:16 am

i have only added stuff like
Teamspeak module
coppermine

cheers

Regular Joined: Sep 25, 2006 Posts: 57

I've done this with my main site and it worked.

I did read that you can start with a fresh database and install rn2.10 and move everything from the 2.02 in afterwards. How is this done?

Posted: Sat Jun 30, 2007 6:24 am

As long as the data base structures match (and there are many threads on this topic that you can find here), you can just dump and restore the tables to the rn2.10 set of tables. Or even just point config.php in RN2.10 to your old tables. But you need exactly the same set of tables that are in rn2.10 with the same structure to them.

Regular Joined: Jan 10, 2006 Posts: 93

>> If you are on a version earlier than 2.02.02, use the various patch downloads and/or support forum posts to help you get to 2.02.02 FIRST

Where might I find these?

Posted: Mon Jan 28, 2008 7:58 am

Your sig says you are on 2.02 so the 2.02.02 upgrade is best for you which can be found in the downloads.

Posted: Tue Jan 29, 2008 5:40 am

Nash, can you please verify if you are on 2.02.00 or 2.02.02. There is definitely a difference and you would need to be on 2.02.02 to follow the directions to get you to 2.10.01.