| 1 |
// $Id$
|
| 2 |
|
| 3 |
Upgrading from previous versions of FileField does not differ from the
|
| 4 |
recommended approach for other modules.
|
| 5 |
|
| 6 |
Upgrading from Drupal 5
|
| 7 |
-----------------------
|
| 8 |
|
| 9 |
1) Your Drupal 5 installation must be running at least FileField 2.3 before
|
| 10 |
migrating to Drupal 6. If your version of FileField is older than this,
|
| 11 |
install the latest version of FileField for Drupal 5 on your Drupal 5 site
|
| 12 |
and run update.php. This gets the database in a format that the Drupal 6
|
| 13 |
upgrade expects.
|
| 14 |
|
| 15 |
2) After ensure FileField 2.3 or higher is on your Drupal 5 site, upgrade your
|
| 16 |
site normally to Drupal 6. Download the latest version of FileField for
|
| 17 |
Drupal 6 and place it in your sites/all/modules directory.
|
| 18 |
|
| 19 |
3) Run update.php on your Drupal 6 site to upgrade FileField to the latest
|
| 20 |
database schema.
|
| 21 |
|
| 22 |
|
| 23 |
Upgrading from any previous Drupal 6 version
|
| 24 |
--------------------------------------------
|
| 25 |
|
| 26 |
1) Download the latest version of FileField and the filefield directory in
|
| 27 |
sites/all/modules.
|
| 28 |
|
| 29 |
2) Visit update.php on your site and run the update.
|
| 30 |
|
| 31 |
|
| 32 |
Running update.php
|
| 33 |
------------------
|
| 34 |
Never, never, ever expand the "Select versions" fieldset and manually change
|
| 35 |
the update number. Drupal knows which version you are currently running and
|
| 36 |
automatically selects the appropriate version. If you change this number, you
|
| 37 |
risk running an update twice (if you select a lower number) or you'll skip
|
| 38 |
updates entirely (if you select a higher number). The ability to change the
|
| 39 |
update number was intended for developers. Due to the confusion caused by this
|
| 40 |
fieldset, it has been removed entirely in Drupal 7 to prevent such accidental
|
| 41 |
self-inflicted damage to user sites.
|
Parent Directory
| 
Revision Log
| 
Revision Graph