README.txt 2.8 KB

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