| 1 |
/* $Id: UPGRADE,v 1.8 2006/11/26 14:07:40 vhmauery Exp $ */
|
| 2 |
|
| 3 |
Steps for upgrading from 4.7 to 5.0
|
| 4 |
|
| 5 |
1. Go to admin/modules and disable Acidfree
|
| 6 |
2. Perform the Drupal upgrade process
|
| 7 |
3. Download and unpack the Drupal 5.0 modules: Acidfree, Image, and Views.
|
| 8 |
If your site has any Acidfree videos, download Video as well.
|
| 9 |
4. Go to admin/build/modules and enable Acidfree, Image, Taxonomy, and Views.
|
| 10 |
If your site has any Acidfree videos, enable Video, Video Image,
|
| 11 |
and Video Upload.
|
| 12 |
5. After enabling the modules, there is a link to update.php. Run the update
|
| 13 |
script again and make sure that Acidfree Module Version selected is 3.
|
| 14 |
6. Press the Update button and wait while the update script converts all the
|
| 15 |
images and videos to the new version.
|
| 16 |
|
| 17 |
WARNING WARNING WARNING
|
| 18 |
|
| 19 |
Upgrading should be done with great care. Please back up all your data BEFORE
|
| 20 |
doing anything. This means both the database AND the image/video files.
|
| 21 |
Upgrading may destroy your website and suck many days out of your life. So
|
| 22 |
I am warning you here to test the upgrade on a replica of your production site
|
| 23 |
to make sure it will go smoothly. Try it a couple of times to make sure it
|
| 24 |
will work. Report any problems you have so they can get fixed.
|
| 25 |
|
| 26 |
The actual execution time of the upgrade may be a long time. If the script
|
| 27 |
gets killed because it ran past the max execution time, you will almost
|
| 28 |
certainly corrupt the Acidfree tables. You may want to modify the line in your
|
| 29 |
php.ini to allow for longer execution time:
|
| 30 |
|
| 31 |
max_execution_time = 600 ; Maximum execution time of each script, in seconds
|
| 32 |
|
| 33 |
I set it to 10 minutes for the upgrade of my large site and that was plenty.
|
| 34 |
This may take some time, depending on the number of Acidfree nodes, the
|
| 35 |
image/video file sizes, etc. As an example of how long it might take, a 3000+
|
| 36 |
node site of mostly images with a few videos might take about five minutes.
|
| 37 |
Much of the time spent is actually file copy time (moving it from the
|
| 38 |
Filemanager file store to the Drupal file system), so faster hard drives mean
|
| 39 |
faster execution time.
|