You are here

README.txt in Node clone 5

Same filename and directory in other branches
  1. 8 README.txt
  2. 5.2 README.txt
  3. 6 README.txt
  4. 7 README.txt
README file for the clone module for Drupal 5.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" 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".  Once you click this
tab you have *already* created a new node that is a copy of the node you were
viewing, and you will be redirected to an edit screen for that new node.

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 an additional confirmation screen is required before making a clone
of a node, and also 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. File attachments
are not included in the cloned node. For the core Upload module and for the CCK
Imagefield and Filefield modules, the node is proceesed to make sure data about
attachements on the original node is removed. Otherwise, data corruption would
occur. For other modules that add attachements, you may have problems.

This module seems to produce functional clones of forms made using the webform 
module, but because of replication of some of the webforms IDs, the form's 
theming will always be the same as the original webform.

In all cases, but especially if you are using a complex 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. 

To install this module, copy the folder with the all the files to the
/sites/all/modules  OR sites/defualt/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).

File

README.txt
View source
  1. README file for the clone module for Drupal 5.x.
  2. The clone module allows users to make a copy of an existing node and then edit
  3. that copy. The authorship is set to the current user, the menu and url aliases
  4. are reset, and the (localized) words "Clone of" are inserted into the title to
  5. remind you that you are not editing the original node.
  6. Users with the "clone node" permission can utilize this functionality for any
  7. node, while users with "clone own nodes" permission can only clone content that
  8. they are the author of (see below regarding other permission checks). A new
  9. tab will appear on node pages with the word "Clone". Once you click this
  10. tab you have *already* created a new node that is a copy of the node you were
  11. viewing, and you will be redirected to an edit screen for that new node.
  12. This module makes reasonable checks on access permissions. A user cannot clone
  13. a node unless they can use the input format of that node, and unless they have
  14. permission to create new nodes of that type based on a call to node_access().
  15. Settings can be accessed at admin/settings/clone. On this page you can
  16. set whether an additional confirmation screen is required before making a clone
  17. of a node, and also set whether the publishing options are reset when making
  18. a clone of a node. This is set for each node type individually.
  19. This module seems to work with common node types, however YMMV. File attachments
  20. are not included in the cloned node. For the core Upload module and for the CCK
  21. Imagefield and Filefield modules, the node is proceesed to make sure data about
  22. attachements on the original node is removed. Otherwise, data corruption would
  23. occur. For other modules that add attachements, you may have problems.
  24. This module seems to produce functional clones of forms made using the webform
  25. module, but because of replication of some of the webforms IDs, the form's
  26. theming will always be the same as the original webform.
  27. In all cases, but especially if you are using a complex or custom node type, you
  28. should evaluate this module on a test site with a copy of your database before
  29. attempting to use it on a live site. On the settings page you may choose node
  30. types to be omitted from the cloning mechanism - no users will be able to clone
  31. a node of an omitted type.
  32. To install this module, copy the folder with the all the files to the
  33. /sites/all/modules OR sites/defualt/modules directory of your Drupal
  34. installation and enable it at /admin/build/modules. Two new permissions are
  35. available, but there are no changes to the database structure.
  36. The Clone module was originally derived from code posted by Steve Ringwood
  37. (nevets@drupal) at http://drupal.org/node/73381#comment-137714
  38. An additional helper module, Clone Imagefield, is also present. If this module
  39. is enabled, files attached using the CCK Imagefield module will be copied when
  40. the clone is created. Typically, this means the filename of the copy will have
  41. a number appended to it to distinguish it form the original file.
  42. Development of the Clone Imagefield module for 5.x sponsored by paulnem
  43. (paulnem@drupal).