Skip to content
Snippets Groups Projects
Select Git revision
  • 6.x-1.4
  • 7.x-1.x default
  • 8.x-1.x
  • 8.x-1.x-drupalmoduleupgrader
  • 6.x-1.x
  • 4.7.x-1.x
  • 4.7.x-2.x
  • 5.x-1.x
  • 5.x-2.x
  • 7.x-1.0
  • 7.x-1.0-rc4
  • 7.x-1.0-rc3
  • 7.x-1.0-rc2
  • 7.x-1.0-rc1
  • 6.x-1.3
  • 7.x-1.0-beta1
  • 6.x-1.2
  • 6.x-1.1
  • 5.x-1.7
  • 5.x-2.7
  • 6.x-1.0
  • 5.x-2.6
  • 5.x-1.6
  • 4.7.x-2.1
  • 4.7.x-1.3
  • 5.x-1.5
  • 5.x-2.5
  • 5.x-2.3
28 results

node_clone

  • Clone with SSH
  • Clone with HTTPS
  • pwolanin's avatar
    Issue #2376203 by pwolanin: Add a setting to suppress the destination query...
    Peter Wolanin authored
    Issue #2376203 by pwolanin: Add a setting to suppress the destination query string on the view field
    2333f563
    History
    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