I seem to remember Dries introducing a hack into Drupal.org to handle a bug with submitting issues lately, where "project_issue" was becoming "project".

After trying the latest project.module on drupal HEAD I've had the same problems and tracked it down to node_get_module_name.

See the attached patch.

CommentFileSizeAuthor
node_name.patch479 bytesThox

Comments

Thox’s picture

Thox commented
Status: Needs review » Closed (fixed)

chx pointed out that the bug in previous versions of Drupal that allowed project module to work has now been removed. This patch works, but apparently isn't the right approach.

chx’s picture

chx commented

As this was a patch issue thus get on the devel list, let my comment be available here.

node_get_module_name is supposed to return the name of the module that defines the node type of the given node. This was not so in previous Drupals. Instead of this, it returned everything before the first dash, if there was no dash, it returned the whole node type. As the docs says "to prevent namespace conflicts, each node type defined by a module should be prefixed by the name of the module and a dash." this should be correct. But project module used underscore instead of a dash. This is a bug actually which triggered the bug in node_get_module_name so project_issue was returned as module name instead of project. But now, project is returned.