| 1 |
$Id: README.txt,v 1.3 2006/01/21 19:21:28 syscrusher Exp $
|
| 2 |
|
| 3 |
The Links Package is a set of modules that facilitate use of web links
|
| 4 |
(URLs) in various content types. Each link is carefully examined to put
|
| 5 |
it into a common format and then cataloged into a master database table
|
| 6 |
when it is first used. Later, references to the same link by other content
|
| 7 |
on the site are automatically connected to the same master catalog entry,
|
| 8 |
so that any particular unique URL appears in the database only once, no
|
| 9 |
matter how many times it is referred to by site content.
|
| 10 |
|
| 11 |
|
| 12 |
|
| 13 |
MODULE DESCRIPTIONS
|
| 14 |
|
| 15 |
LINKS
|
| 16 |
|
| 17 |
links.module provides an application program interface (API) for managing
|
| 18 |
internal and external links as part of a Drupal node. The module by itself
|
| 19 |
does very little; mainly, it provides a user interface for controlling the
|
| 20 |
way in which links are handled and how they behave within all nodes -- in
|
| 21 |
other words, the global settings for the API library.
|
| 22 |
|
| 23 |
Author: Scott Courtney (drupal.org user "syscrusher")
|
| 24 |
|
| 25 |
RELEASE STATUS: This module is at an initial release state, ready for
|
| 26 |
early-adopter use in production.
|
| 27 |
|
| 28 |
LINKS_RELATED
|
| 29 |
|
| 30 |
links_related.module allows nodes of arbitrary types (as designated by the
|
| 31 |
site administrator) to have one or more associated links to related
|
| 32 |
content.
|
| 33 |
|
| 34 |
Author: Scott Courtney (drupal.org user "syscrusher")
|
| 35 |
|
| 36 |
RELEASE STATUS: This module is at an initial release state, ready for
|
| 37 |
early-adopter use in production.
|
| 38 |
|
| 39 |
LINKS_WEBLINK
|
| 40 |
|
| 41 |
links_weblink.module is a modified version of the existing weblink.module,
|
| 42 |
but uses the new links API and database tables. links_weblink.module is
|
| 43 |
also integrated with views.module, which allows very flexible retrieval
|
| 44 |
of the links catalog. links_weblink.module provides its own simple query
|
| 45 |
mechanism for sites with modest needs, but views.module offers a much
|
| 46 |
more robust mechanism.
|
| 47 |
|
| 48 |
RELEASE STATUS: This module is at an initial release state, ready for
|
| 49 |
early-adopter use in production.
|
| 50 |
|
| 51 |
LINKS_ADMIN
|
| 52 |
|
| 53 |
links_admin.module is for administering the site-wide database of links,
|
| 54 |
independent of the module(s) using each link.
|
| 55 |
|
| 56 |
RELEASE STATUS: This module is EXPERIMENTAL. Do not use in production
|
| 57 |
sites. links_admin.module is not yet part of the standard download and
|
| 58 |
is available only from CVS.
|
| 59 |
|
| 60 |
|
| 61 |
UPDATE SCRIPTS
|
| 62 |
|
| 63 |
To run the update scripts, you must first use the regular Drupal ugrade
|
| 64 |
procedure to convert your {node} table (and related tables) to version 4.6
|
| 65 |
The update scripts will NOT work with Drupal 4.5; neither will the links
|
| 66 |
package.
|
| 67 |
|
| 68 |
THE UPDATE SCRIPTS ARE EXPERIMENTAL -- Use at your own risk.
|
| 69 |
|
| 70 |
update-weblinks-old.php
|
| 71 |
|
| 72 |
If you have weblink nodes that were created before Drupal 4.6, this is the
|
| 73 |
update script that you need. It non-destructively copies data from the old
|
| 74 |
{weblink} table into the new combination of {links} and {links_node}
|
| 75 |
using the API calls to correctly normalize each URL. (It is *not* correct
|
| 76 |
to simply use SQL commands to directly copy the URLs from the old table to
|
| 77 |
the new ones.)
|
| 78 |
|
| 79 |
update-webstory.php
|
| 80 |
|
| 81 |
The module "webstory" was developed for use on a few specific sites. Chances
|
| 82 |
are about 99% that you are not using webstory.module and therefore do not
|
| 83 |
need this script. It's provided as an example, however, in case it might
|
| 84 |
be useful to other developers.
|