Thank you so much for creating this module! 2 questions...Is there a way to limit the content types available for converting from and converting to? And does this delete the original node upon conversion?

Again, thank you-thank you-thank you!

CommentFileSizeAuthor
#5 convert_nodes_with_perms.patch1.35 KBAnonymous (not verified)

Comments

alcroito’s picture

I'm not quite sure what you mean by limiting content types.
As for the second question: No, the original node is not deleted, the type is changed directly without making any copies of nodes.

lokineo’s picture

I just want the convert option to be available for only one content type and I want it to be able to convert to a specific content type. Basically I have it set up that a user creates a node and then someone with basic admin privileges can then go and convert that node to a different node type so that way when the admins comment on that node it is not visible by the user. Hope that made sense. :D

alcroito’s picture

Something like this isn't supported yet. It would imply creating a complex permission system. It'll have to be looked into.

Anonymous’s picture

i second that request. it would be great to specify for example: user A can convert nodetype B to nodetype C (but not reverse) and so on. as far as i know, the workflow module already has such an complex permission system in use.

Anonymous’s picture

StatusFileSize
new1.35 KB

i wrote a patch which does the first part: look if a user has the permission to convert a specific content type. with this patch its not possible to restrict the conversion based on the 'destination node type';

alcroito’s picture

Actually, I have already implemented the permission system a long time ago (that's wasn't that complex after a better insight), but I didn't have the opportunity to commit to cvs, because I added some other things in the module amongst that. I'll try to commit the code a few days from now.

alcroito’s picture

Status: Active » Fixed

Commited to the 6.x-1.3 release.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.