The node_clone module has a directory called "node_clone" but the module files are all called clone.*
This is not a problem if you load the module using the modules admin interface.
However if you use an installation profile then there is an additional check that runs as part of the installation process (drupal_verify_profile()) which fails to find the module since it assumes the name of the module directory will be the name of the module.

This is the only module I have found so far that has this issue - every other module I've used so far uses the same name for both directory and files.

Comments

dudleyc’s picture

dudleyc CreditAttribution: dudleyc commented

Looks like the directoryname, the prefix to .module & .info filenames and the 'project' value in the .info file should all be set to the same string.
Renaming the directory to be 'clone' and changing the 'project' value in the .info file meant that drupal_verify_profile() was then happy.
Keeping them as 'node_clone' and renaming all the files and methods to be 'node_clone' instead of 'clone' would also be a valid solution.

ladybug_3777’s picture

ladybug_3777 CreditAttribution: ladybug_3777 commented
Status: Active » Closed (duplicate)

This issue was first reported here: https://www.drupal.org/node/1809898 . I'm marking this as a duplicate so people will link to the original that has a little more detail. Thanks!