-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.txt
60 lines (47 loc) · 3.27 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
README file for the process clone module for Drupal 7.x.
This is a fork of the node clone module. It differs from the baseline module by
presetting the author to the current user and preserving a record of the cloned
nodes' lineage.
---------
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 "Clone content" local action link will appear on node pages.
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 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/config/content/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 (non-core) field 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. For example, if you use Field Collections,
you may need to also enable the extra Field Collection Node Clone module from
https://www.drupal.org/project/field_collection_node_clone Otherwise, the cloned
node will reference the items in the original field collection.
This module makes no attempt to respect field-level permissions set via
the Field Permissions module, or any other module that implements
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