Already very experienced with Perl scripts and Coranto? Then follow these instructions:
If you have any problems, read the full instructions below.
The upgrade is a 5-step procedure. The amount of pain it will involve depends largely on the quirks of your web host.
The very first thing to do is BACKUP ALL YOUR CURRENT FILES before attempting the upgrade! There is no way to automatically revert to the old version if something fails so this way you will have a point of safe return if the upgrade fails.
If you have altered any of the settings available within cruser.pl, make sure that you update the new cruser.pl accordingly. Also, if you have stored any custom subroutines inside your cruser.pl file, you need to backup them and reinsert them in the new version of cruser.pl! If you haven't touched cruser.pl since you installed the current Coranto you are using (which applies to most users), you can simply upload the new cruser.pl (in step 3).
Please note that the three old settings 'nsettingspath', 'nsbkpath' and 'cfgpath' have all been replaced with the single setting 'data_path', which defines the common folder where to place nsettings.cgi, nsbk.cgi, crcfg.dat and newsdat.txt. This means that you must use the original filenames for these files and place them in the folder you specify with 'data_path'. However, as mentioned before, this is not something you normally should have changed so if this sounds confusing it is highly doubtfull you have used this option to begin with.
Before uploading coranto.cgi and viewnews.cgi: Make sure that the path to Perl at the very first line of these files is the same in the new versions as in the ones you currently use. Also, if you have specified values for the abspath and scripturl variables at the begining of coranto.cgi and viewnews.cgi make sure to apply the same values in the new versions of these files as well.
Next, you should upload the Coranto files to your server.
You should upload the new subfolders 'addons', 'docs' and 'languages' with all their contents in ASCII mode. You must *not* upload the subfolders 'data' and 'templates', since you allready have working files that will be placed in these folder. You can create the folers if you want, but leave them empty.
Please note that there is new versions of the addons distributed with Coranto, so if you haven't done any custom changes to the addons 'News Category', 'Modify User Column' or 'Backup' you can remove them from the Coranto base folder (since the new versions are now in the subfolder 'addons' you just uploaded, right?). You can of course leave them as is, but you will then get a note in STEP 4 that states that the automatic upgrade was not able to move these addons, which would be OK.
You must also upload all the files in the Category base directory (coranto.cgi, craddon.pl, cradmin.pl and so on) in ASCII mode and overwrite the files currently in the Coranto folder. The files coranto.cgi, viewnews.cgi and cruser.pl should include the changes you did in STEP 2. After you have uploaded the files they should have the same chmod settings as previously.
And oh, you created a backup as stated in step 1 before uploading, huh?
Now access coranto.cgi via your web browser to kickstart the automatic upgrade. For example, visit the URL http://your.site.com/path/coranto.cgi It should display a page letting you know the status for how the automatic upgrade went. If everything went well you should see a page that states Upgrade Sucessfull! and a bunch of information about what was done during the upgrade.
If something didn't go well, you will see a page with the header Upgrade Failure! and information about what went wrong. Based on that information you should hopefully be able to fix the problems manually. If you don't know how to interpret the information or know what to do with it, maybe the people at the Coranto Forum can help you out...
At this stage Coranto should be fully installed and working.
The file crsetup.pl in your Coranto base directory was only used during the upgrade and can thus you can
remove it now if you want. It doesn't do any real harm having it there either, just takes up some space.