Not sure if anyone's noticed this yet, but Node Hierarchy seems to completely break any semblance of a parent/child relationship between a forum topic and its container. Can't seem to repair this simply by designating a forum topic capable of being child or anything else.. is there a way to fix this without having to use some sort of hack?

Comments

ronan’s picture

ronan commented

I'm afraid I don't use the forum module so off-hand I'm not sure if there's a workaround. Nodehierarchy unfortunately does not necessarily play well with others right now (notably the book module). It's especially troublesome with other modules that implement a hierarchy of some sort themselves. This is mostly because it was designed to replace these single use-case modules with a more generic approach.

I'll look into the interaction with forum as soon as a get a free moment, and see if there's a simple way to get them working in harmony.

Rysk’s picture

Rysk commented

I could be way off base here, but it seems to me the simplest workaround for now.. at least as a temporary measure, would be to make it completely avoid having anything at all to do with the "forum topic" content type. Although, I'm sure that's probably a lot of hassle

ronan’s picture

ronan commented

I haven't looked into it, but my guess is that the two modules are competing internally for some generic term such as 'parent'. I need to clean up my module to try and avoid such terms in order to help interoperability with other modules.

dgorton’s picture

dgorton commented

Similar to namespace collisions with book - http://drupal.org/node/190456
Any progress will be posted there.

dgorton’s picture

dgorton commented
Status: Active » Closed (fixed)

Closing per duplicate status noted in #4