I am interested in seeing the functionality of this module greatly expanded and ported to Drupal 6, with an eye towards inclusion in core. I've posted this as a suggested project for a Google Summer of Code participant to take on and would be interested in any feedback or support you'd care to offer as the existing module's maintainer.

http://groups.drupal.org/node/9975

Thank you.

Comments

scedwar’s picture

scedwar commented

I agree. I just spotted anoither new module crop up (http://drupal.org/project/node_convert) and I said similar things in that issue queue. This is such a useful tool it should be in core. These developers really should join forces.

kkaefer’s picture

kkaefer commented

Yep, I saw that module as well. I didn't install it yet, but if it does what this module does, I'll remove this (nodetype) module in favor of node_convert.

alcroito’s picture

alcroito commented

Hey.
What not let this module be as it is? If someone just needed to change the type of the node, it's pretty straighforward. Besides, in node_convert if you want just to change the node type, you still need the cck module.

scedwar’s picture

scedwar commented

That sounds to me like an argument for the merged module to have some simple logic of the sort

if (cck installed) then convert cck types
else just do a plain change of node type

Anyway, a combined module should do it all, from simple non-cck stuff, right the way through to wonderous actions/og/workflow/cck type stuff with bulk conversions and so on using an API etc. All very Drupal-esque.

alcroito’s picture

alcroito commented

Hmm. I guess I'll have to implement the cck installed part, but it'll be a bit tricky, cause the control has to be done more than in one place. Also I'll see to it how can node_convert work with actions/og/workflow. By the way I updated the module, so now it should work pretty well with all kinds of cck fields.