/[drupal]/contributions/modules/links/UPGRADE.txt
ViewVC logotype

Contents of /contributions/modules/links/UPGRADE.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.1 - (show annotations) (download)
Thu Feb 2 04:50:59 2006 UTC (3 years, 9 months ago) by syscrusher
Branch: MAIN
CVS Tags: DRUPAL-5--1-12-BETA1, DRUPAL-5--1-9, DRUPAL-5--1-8, DRUPAL-5--1-5, DRUPAL-5--1-7, DRUPAL-5--1-6, DRUPAL-5--1-3, DRUPAL-5--1-2, DRUPAL-4-7--1-1, DRUPAL-5--1-4, DRUPAL-6--1-0-BETA14, DRUPAL-6--1-0-BETA13, DRUPAL-6--1-0-BETA12, DRUPAL-6--1-0-BETA11, DRUPAL-6--1-0-BETA10, DRUPAL-5--1-11, DRUPAL-5--1-10, DRUPAL-5--1-13, DRUPAL-5--1-12, DRUPAL-6--1-0-BETA9, DRUPAL-6--1-0-BETA8, DRUPAL-6--1-0-BETA3, DRUPAL-6--1-0-BETA2, DRUPAL-6--1-0-BETA1, DRUPAL-6--1-0-BETA7, DRUPAL-6--1-0-BETA6, DRUPAL-6--1-0-BETA5, HEAD
Branch point for: DRUPAL-4-7, DRUPAL-6--1, DRUPAL-5
File MIME type: text/plain
Lots of improvements to the update scripts, including the addition of a
new script for recent weblinks versions. The latter is UNTESTED as of now
due to lack of a test site. Test reports welcome if someone else gets
time to test it before I do.

Also added first draft of upgrade instructions.
1 $Id$
2
3 The Links Package contains several scripts that can help you upgrade from
4 legacy modules. If your favorite legacy module should be supported and
5 isn't, contributed update scripts are welcome. Please create new scripts
6 rather than adding additional modules to the existing ones, as the desire
7 is to keep these as simple as possible.
8
9
10 GENERAL UPGRADE PROCEDURE:
11
12 1. Use Drupal's own upgrade process to convert to Drupal 4.7.x. Don't worry
13 that the URLs appear to be missing. They are stored in a table separate
14 from the basic nodes, and will be migrated to the new {links_node} table
15 by this script.
16
17 2. Decide which script(s) you need based on the instructions that follow.
18 Copy the script(s) to the top-level directory of your Drupal site.
19
20 3. Login to your site as the administrative user.
21
22 4. Manually type the URL to the upgrade script you wish to run. These scripts
23 are independent of one another, so if you need to use more than one, you
24 can run them in any order you wish.
25
26 5. To prevent the timeout errors that can happen on some servers during
27 database transactions that process thousands of records, the upgrade
28 scripts limit themselves to no more than 1000 nodes per run. You should
29 simply use your browser's reload or refresh function to re-execute each
30 script until it reports that it had zero records to do on its run. The
31 scripts are self-limiting, so you won't hurt anything by accidentally
32 running it too many times.
33
34
35 DESCRIPTION OF THE UPGRADE SCRIPTS:
36
37 update-weblinks-old.php
38
39 This script is to be used for "weblink" nodes created with the OLD
40 version of weblink.module, for Drupal versions prior to 4.6. Do NOT
41 attempt to use this script with the newer versions of weblink.module
42 created by Ber Kessels.
43
44 update-weblinks.php
45
46 This script is for the newer "weblink" nodes created with Ber
47 Kessels' version of weblinks for Drupal 4.6. Do NOT run this
48 script against older versions.
49
50 update-webstory.php
51
52 Most people will not need this script; it is provided mainly as an
53 example. The webstory.module was a custom node type used only on a
54 few web sites. But since it needed to be written, there was no reason
55 not to share in hopes that it might be useful as a template for
56 others who have custom links-handling modules.

  ViewVC Help
Powered by ViewVC 1.1.2