Closed (fixed)
Project:
Node Convert
Version:
6.x-1.2
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
10 Sep 2008 at 13:38 UTC
Updated:
11 May 2009 at 16:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
alcroito commentedI'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.
Comment #2
lokineo commentedI 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
Comment #3
alcroito commentedSomething like this isn't supported yet. It would imply creating a complex permission system. It'll have to be looked into.
Comment #4
Anonymous (not verified) commentedi 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.
Comment #5
Anonymous (not verified) commentedi 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';
Comment #6
alcroito commentedActually, 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.
Comment #7
alcroito commentedCommited to the 6.x-1.3 release.