modules/node_clone/README.txt

$Id: README.txt,v 1.11 2008/05/04 00:23:21 pwolanin Exp $

README file for the clone module for Drupal 6.x.

The clone module allows users to make a copy of an existing node and then edit
that copy. The authorship is set to the current user, the menu and url aliases
are reset, and the (localized) words "Clone of" are inserted into the title to
remind you that you are not editing the original node.

Users with the "clone node" or "clone own nodes" permission can utilize this 
functionality. A new tab will appear on node pages with the word "Clone".  
Depending on the setting you choose there are two possible actions that will 
occur when you click that tab. Each of these is a different cloning "method".

The default method (used in the 5.x-2.x branch also) works by pre-populating the 
node form, rather than immediately saving a copy of the original node to the 
database.  Thus, your node will not be saved until you hit "Submit" (just like 
if you went to node/add/x).

The alternative method that may be selected immediately saves the node (by 
default the user must confirm this action on a confirmation form). This may
work better in some cases, but also means that the copied node may immediately
show up on the front page or in RSS feeds even while you are editing it.

This module makes reasonable checks on access permissions.  A user cannot clone
a node unless they can use the input format of that node, and unless they have
permission to create new nodes of that type based on a call to node_access().

Settings can be accessed at admin/settings/clone.  On this page you can
set whether the publishing options are reset when making a clone of a node.
This is set for each node type individually.

This module seems to work with common node types, however YMMV, especially with
nodes that have any sort of image or file  attachments.   In all cases, but
especially if you are using a complex (CCK) or custom node type, you should
evaluate this module on a test site with a copy of your database before
attempting to use it on a live site. On the settings page you may choose
node types to be omitted from the cloning mechanism - no users will be able
to clone a node of an omitted type.

This module makes no attempt to respect field-level permissions set via
CCK's Content Permissions module, or any other module that implements
CCK field-level permissions hooks. You should test your configuration
carefully or not allow access to the clone functionality for non-admins if
you rely on field-level permissions for important site features.

To install this module, copy the folder with all the files to the
/sites/all/modules  OR /sites/default/modules directory of your Drupal 
installation and enable it at /admin/build/modules.  Two new permissions are 
available, but there are no changes to the database structure.

Note: this module originally derived from code posted by Steve Ringwood
(nevets@drupal) at http://drupal.org/node/73381#comment-137714

1	$Id: README.txt,v 1.11 2008/05/04 00:23:21 pwolanin Exp $
2
3	README file for the clone module for Drupal 6.x.
4
5	The clone module allows users to make a copy of an existing node and then edit
6	that copy. The authorship is set to the current user, the menu and url aliases
7	are reset, and the (localized) words "Clone of" are inserted into the title to
8	remind you that you are not editing the original node.
9
10	Users with the "clone node" or "clone own nodes" permission can utilize this
11	functionality. A new tab will appear on node pages with the word "Clone".
12	Depending on the setting you choose there are two possible actions that will
13	occur when you click that tab. Each of these is a different cloning "method".
14
15	The default method (used in the 5.x-2.x branch also) works by pre-populating the
16	node form, rather than immediately saving a copy of the original node to the
17	database. Thus, your node will not be saved until you hit "Submit" (just like
18	if you went to node/add/x).
19
20	The alternative method that may be selected immediately saves the node (by
21	default the user must confirm this action on a confirmation form). This may
22	work better in some cases, but also means that the copied node may immediately
23	show up on the front page or in RSS feeds even while you are editing it.
24
25	This module makes reasonable checks on access permissions. A user cannot clone
26	a node unless they can use the input format of that node, and unless they have
27	permission to create new nodes of that type based on a call to node_access().
28
29	Settings can be accessed at admin/settings/clone. On this page you can
30	set whether the publishing options are reset when making a clone of a node.
31	This is set for each node type individually.
32
33	This module seems to work with common node types, however YMMV, especially with
34	nodes that have any sort of image or file attachments. In all cases, but
35	especially if you are using a complex (CCK) or custom node type, you should
36	evaluate this module on a test site with a copy of your database before
37	attempting to use it on a live site. On the settings page you may choose
38	node types to be omitted from the cloning mechanism - no users will be able
39	to clone a node of an omitted type.
40
41	This module makes no attempt to respect field-level permissions set via
42	CCK's Content Permissions module, or any other module that implements
43	CCK field-level permissions hooks. You should test your configuration
44	carefully or not allow access to the clone functionality for non-admins if
45	you rely on field-level permissions for important site features.
46
47	To install this module, copy the folder with all the files to the
48	/sites/all/modules OR /sites/default/modules directory of your Drupal
49	installation and enable it at /admin/build/modules. Two new permissions are
50	available, but there are no changes to the database structure.
51
52	Note: this module originally derived from code posted by Steve Ringwood
53	(nevets@drupal) at http://drupal.org/node/73381#comment-137714
54