Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The clone module would then depend on them. That would allow other modules (like Cash Flow, which is my case) add a dependency on node_clone as well as clone, and Drush would then be able to download Node Clone properly. As it is, it'll either say that it can't enable node_clone or it will keep complaining that clone doesn't exist.
This isn't a functional change for the module. Other than the basic stuff in node_clone.info
, the placeholder files could be empty.
I'm willing to roll the patch if it would be reviewed.
Comment | File | Size | Author |
---|---|---|---|
#5 | 1919168-5.patch | 459 bytes | pwolanin |
Comments
Comment #1
pwolanin CreditAttribution: pwolanin commentedHow does this work for any other module where the project name and the module name are not identical?
Comment #2
wizonesolutionsI don't know. Is this something that has been raised, or that we should raise, upstream?
Comment #3
lolandese CreditAttribution: lolandese commentedComment #4
pwolanin CreditAttribution: pwolanin commentedThis idea is probably the less annoying solution.
Can we make it a hidden module?
Comment #5
pwolanin CreditAttribution: pwolanin as a volunteer and at Acquia commentedNot sure I love this, but please test and see how it works for you.
Comment #6
paulvandenburg CreditAttribution: paulvandenburg commented#5 has been solving this problem for us for quite a while now, since #2989434: Use node_clone module instead of clone to be exact.
I'm for including this in the next release.