README file for the clone module for Drupal 5.x.
5.x-2.x branch.
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" permission can utilize this functionality for any
node, while users with "clone own nodes" permission can only clone content that
they are the author of (see below regarding other permission checks). A new
tab will appear on node pages with the word "Clone". The -2.x branch of this
module 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).
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. For the core Upload
module and for the CCK Imagefield and Filefield modules, the node is proceesed
before populating the form to make sure about attachements on the original node
is removed. Otherwise, data corruption could occur. For other modules that add
attachements, you may have problems.
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 user will be
able to clone a node of an omitted type.
To install this module, copy the folder with the .info and .module files to the
/sites/all/modules OR /modules directory of your Drupal installation and enable
it at /admin/build/modules. A new permission is available, but there are no
changes to the database structure. On the settings page you may choose
node types to be omitted from the cloning mechanism - no users will be able
to try to clone a node of an omitted type.
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.
The Clone module was originally derived from code posted by Steve Ringwood
(nevets@drupal) at http://drupal.org/node/73381#comment-137714
An additional helper module, Clone Imagefield, is also present. If this module
is enabled, files attached using the CCK Imagefield module will be copied when
the clone is created. Typically, this means the filename of the copy will have
a number appended to it to distinguish it form the original file.
Development of the Clone Imagefield module for 5.x sponsored by paulnem
(paulnem@drupal).
View source
-
- README file for the clone module for Drupal 5.x.
-
- 5.x-2.x branch.
-
- 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" permission can utilize this functionality for any
- node, while users with "clone own nodes" permission can only clone content that
- they are the author of (see below regarding other permission checks). A new
- tab will appear on node pages with the word "Clone". The -2.x branch of this
- module 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).
-
- 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. For the core Upload
- module and for the CCK Imagefield and Filefield modules, the node is proceesed
- before populating the form to make sure about attachements on the original node
- is removed. Otherwise, data corruption could occur. For other modules that add
- attachements, you may have problems.
-
- 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 user will be
- able to clone a node of an omitted type.
-
- To install this module, copy the folder with the .info and .module files to the
- /sites/all/modules OR /modules directory of your Drupal installation and enable
- it at /admin/build/modules. A new permission is available, but there are no
- changes to the database structure. On the settings page you may choose
- node types to be omitted from the cloning mechanism - no users will be able
- to try to clone a node of an omitted type.
-
- 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.
-
- The Clone module was originally derived from code posted by Steve Ringwood
- (nevets@drupal) at http://drupal.org/node/73381#comment-137714
-
- An additional helper module, Clone Imagefield, is also present. If this module
- is enabled, files attached using the CCK Imagefield module will be copied when
- the clone is created. Typically, this means the filename of the copy will have
- a number appended to it to distinguish it form the original file.
-
- Development of the Clone Imagefield module for 5.x sponsored by paulnem
- (paulnem@drupal).
-