Basically I am trying to make a simplified node relationship (node relativity / node hierarchy didn't work for this). The key factor I am trying to achieve is parent / child inheritance in regards to published / unpublished / deleted status. Basically if the parent gets deleted so does the child. a node with comments under it seems perfect, but there is only one comment type.
I want to have control over how many comments can be posted under a content type . I know that there is node comments but it only allows for one comment type. I also wanted to tie in quota by role, but of course since there is only 1 comment type, I have no way to make custom comment quotas for content types. So basically I want to achieve this:
content type 1 (parent) (can post 5 comment type 1)
comment type 1 (child)
content type 2 (parent) (can post 10 comment type 2)
comment type 2 (child)
etc....
The only thing I really want is the inheritance of the node status, so when a parent node gets unpublished or deleted so does it's children. I don't care how the relationship is formed (by having comments under the node or taxonomy or whatever) I just want to make sure that if the parent node gets unpublished, anything made under it also gets unpublished. can anyone point me in a direction to at least get this functionality?
Comments
_
You can probably get the inheritance working with the http://drupal.org/project/rules module-- thought it might require a bit of php for the action.
can't use rules because I am
can't use rules because I am using drupal 5....I would use workflow-ng, but it has issues with anything relating to system events....basically if anything is generated by the system and not the user, workflow-ng doesn't "know" about it...that's another issues I don't really want to try and solve. I was just really hoping to fake the idea of related content pieces with commetns...or even something like the book module, but I am not even sure if you delete a book that all it's pages get deleted too...
_
sorry about that-- I didn't catch the d5 tag on your post. Good point about book module-- i'm not sure what happens to child pages (i would hope they just became orphans instead of being deleted though).
Have you looked at any of the node relationship modules (nodehierarchy, relativity, etc.)?
heh like I said right at the
heh like I said right at the top of the post, node hierarchy and node relativity don't work at all in this way. I don't ever want to leave orphaned nodes....or even making the orphaned nodes not searchable until I delete them would be suitable. I basically am trying to have it so when the user makes child nodes under the parent node, those children disappear when the parent is gone. The parent is tied to auto expire. Right now when the node expires, all it's children are there and searchable. I don't mind faking the idea of the children being "gone", but right now I have to manually go through and see what nodes are orphaned. was just hoping to automate the whole thing.
Is there a way I can duplicate the idea of comments? it seems near perfect, except for the fact that there is only one type. I really wish I could tag content types as comments to go under other content types
_
geez--- i'm 0 for 2, lol. Sorry it's been a long weekend. I'm drawing a blank. There's no way to have comment types afaik. There's the nodecomment module but there again, i think comments are limited to 1 type. Maybe you could modify that module to be able to designate multiple content types as comments?
Have you tried actions? Or is that related to the problem using workflow_ng?
Other than that, i'm thinking you'll need to use custom code with some hook_comment and hook_nodeapi calls.
I appreciate the help either
I appreciate the help either way....just been looking for weeks on the forums for this functionality which I really feel should have been an option somewhere.... I am completely confused over actions. I have installed it multiple times over the months that I have been developing my site, but documentation and even how to use actions are so vague that I can't even begin to figure out how to do what I want, or even if it's possible. Actions 2.0 is supposedly a backport of rules which allow "things to happen" on system events, but every time I go to try and set a trigger, I am met with "there are no triggers for this event"....tried trigger unlock as well, and that's even more confusing.
I found code via this comment: http://drupal.org/node/175556#comment-604865 but I am not sure how to use it, or how to change it to un-publish instead of outright delete (although it does look like I could change node_delete to node_unpublish).