Do we have another solution for the "After cloning a node" event for the Node clone module?

Question

I would like to use the event in Rules "After cloning a node" but unfortunality this does not work. (see Event "After cloning a node" by node clone module is not working).

I tried to patch the module but did not succeed.

I would like to solve this with rules with :

Event - "Node Edit on type foo" and then add some conditions.

Does anybody knows a good condition for this? What can I compare?

Are there other solution possible?

I need it for the folowing situation: the user has two options for a node: (1) Edit (2) Clone

(1) The edit option is just going to the edit form. Normal editing should be done.

(2) The clone option makes a copy of the Content Type and then starts editing in this node. Before the user is starting this editing two fields in the content type should be empty.

--- Patch log (#8)
$ patch -p1 <2212039-8.patch
patching file clone.pages.inc
Hunk #1 FAILED at 160 (different line endings).
1 out of 1 hunk FAILED -- saving rejects to file clone.pages.inc.rej

--- Patch log (#8) With option --ignore-whitespace
$ patch -p1 --ignore-whitespace <2212039-8.patch
patching file clone.pages.inc
Hunk #1 FAILED at 160 (different line endings).
1 out of 1 hunk FAILED -- saving rejects to file clone.pages.inc.rej

Answer 1

Try to think of a way to better describe what you're trying to do, and for which using that specific event does not work (because of that bug).

Obviously, it doesn't matter what the subsequent Rules Condition and/or Rules Action would be (after you have "an" alternative for that Rules Event you are asking about).

But sometimes the solution for a problem, is to avoid the problem from happening, right? E.g. maybe there is some specific path you could try to intercept (also using the Rules module), right before/after that event occurred. I seem to remember node clone also has such path. And if anything else fails, use Rules Event "Drupal is initializing", followed by a Rules Condition to check such path (if needed using RegEx also ... I bet you know about that Rules trick also).

Answer 2

You should really try first to apply the patch or patches.

1. Save the patch file(s) into the node_clone folder
2. cd into that folder
3. apply patch #8

   patch -p1 < 2212039-8.patch

4. check if the problem persists and apply patch #9 if it does

   patch -p1 < node_clone-7.x-1.x-add_preparing_clone_rule-2212039-9.patch

5. check if the problem still persists
6. :-(

You need to try both patches I guess and see if the error is fixed.

Cheers!

Issue reference on D.O.: https://www.drupal.org/node/2212039

Answer 3

I made a custom rules action module that clones any node, based on this code it returns new cloned node NID, then in rules do other stuff with new NID, code of my rules action:

  <?php
  /**
  * Implement hook_rules_action_info()
  * Declare any meta data about actions for Rules
  */

  function clone_poliza_rules_action_info() {


  $actions = array(
    'clone_poliza_action' => array(
        'label' => t('Clone a node'),
        'group' => t('cadena'),

        'parameter' => array(

          'poliza_nid' => array(
                  'type' => 'integer',
                  'label' => t('node NID to be cloned'),
                  ),

              ),


        'provides' => array(
            'new_poliza_nid' => array(
                    'type' => 'integer',
                    'label' => t('new cloned node NID'),
                    // 'wrap' => TRUE,
                    //'format' => 'full_html'
                    ),
                  ),
      ),
    );
      return $actions;

  } // fin de actions_info


  function clone_poliza_action($poliza_nid) {

  $node = node_load($poliza_nid);

  $new = clone $node;
  $new->is_new = true;
  unset($new->nid);
  unset($new->vid);
  unset($new->tnid);
  node_save($new);

  $new_poliza_nid = $new->nid;

  return array('new_poliza_nid' => $new_poliza_nid);

  }