I have content-types A and B. Content-type B uses many of the same fields as A, which will have the exact same values, but also has additional fields that are not found in A. Can I use your module as a means of pre-populating B's fields with A's values? Will content-type A remain after the conversion?

If this doesn't work, I'm thinking the way to go might be to clone A, then convert either A or its clone to content-type B.

Thanks, and if you can think of anything more efficient, I'd be greatly appreciative, as I am a newbie!

Victor

Comments

alcroito’s picture

alcroito commented

I think cloning the node, and then converting it to the needed content-type will work. You will have to use the API provided by clone node module and the API in node_convert. So basically you'll have to write some sort of script or module that utilizes the both.

alcroito’s picture

alcroito commented
Status: Active » Closed (won't fix)
sly5’s picture

sly5 commented
Status: Closed (won't fix) » Active

Placinta,

Great utility!! Thank you.

It's seems to have been a while with this ticket (I am not the original author), but I'll try and post a very useful scenario and update its status, hoping for your reconsideration.

In our site we have forums and we have support tickets. The user asks a question to the Forum under some category. It turns out the question deserves an administrative action and hence the admins "convert" the Forum post into a support ticket.

But the dialogue is lost from the Forum (containers, forum views, or in general the first places where a user checks for response). User is puzzled. Moreover, no history is kept. So we do this manually, in 3 stages as you say, with clone, convert, and go back to the original to post to reply "a ticket is created here".

It would be real nice to automate all this with a single check box on the "Convert" tab to say "Convert and keep the original, replying with a comment", where the reply would come from node convert templates, or a text box on the convert form, even better by using tokens such as "link-to-copy", etc..

How difficult you think is all this?

sly5

natoya’s picture

natoya commented

Hi Sly5!

Do you have a piece of code so that I can get started with this? I want to clone the content from node A to B and also add in node B an extra field (and this makes node B a different node type).
Regards,
natoya

vasike’s picture

vasike
Location Ramnicu Valcea
commented

subscribe.
could be 2 ways
1. clone + conversion
2. create new node conversion

hixster’s picture

hixster commented

try this -> http://drupal.org/project/crossclone

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Title: Can I use this module to essentially pre-populate fields from one content-type to another, and still keep the original node? » Support the Node Clone module. In other words: first clone - then convert (and still keep the original node).

The simplest solution here would be to detect if Node Clone is installed. If so, then offer the users the option to either do a straight conversion or to first clone and convert the clone to another node type.

This of course would not solve the part of auto-posting a comment on the original node pointing to the cloned+converted one, but that is way out of this modules scope IMO. I'm sure it can be achieved using Rules somehow.

@hixster: Hey Matt, thanx for spotting that alternative module (though seems a bit complicated).

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Version: 6.x-1.2 » 7.x-1.x-dev

...also, new features go against the latest dev of the most recent branch and then backported.