Node export has a bulk mode, and the module imports also despite the name. There is a module which allows inclusion of filefield images encoded right in the text, I have used it, it works well, respecting CCK fields well.<div>
<br></div><div>On its project page it describes an alternative advanced mode: Use views bonus pack and export a view-selected list of nodes via CSV, then use that file for the node_import module to grab on the other end. Also works well.</div>
<div><br></div><div>He that doth not backup first is condemned to hear about history repeating itself.</div><div><br></div><div>Victor Kane</div><div><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a><br><br>
<div class="gmail_quote">On Wed, Aug 11, 2010 at 6:05 PM, Lee Rowlands <span dir="ltr"><<a href="mailto:contact@rowlandsgroup.com">contact@rowlandsgroup.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>
I've had success before with node_export and node_export_file (a sub module of node export) - it also has drush integration.<br>
The file sub module works well with filefield (imagefield) cck fields. The only issue is nodereferences refer to old nodes.<br><font color="#888888">
Lee</font><div><div></div><div class="h5"><br>
On Thu, 2010-08-05 at 19:16 +0100, Phil Glanville wrote:<br>
<blockquote type="CITE">
Hi all.
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
We are struggling here with Drupal migration. We have two installations and would like to migrate *all* content (nodes and uploaded images) from one to the other. Just content not settings. Both installs have the same Modules present.
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
We've looked in to "Migrate" which seems overkill (in terms of customisation and setup) and have researched "Node Export" and "Node Import" (neither or which seem to be a complete solution). "Transformations" sounds good but again seems to be more code based rather than GUI.
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
Is there an easier / more logical way? For instance, would it (in theory) be possible to copy just 'node' or content specific db tables without causing serious problems?
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
Thanks for any help,
</blockquote>
<blockquote type="CITE">
<br>
<br>
</blockquote>
<blockquote type="CITE">
Phil.
</blockquote>
<blockquote type="CITE">
<br>
<br>
<br>
<br>
Printing this email? If you are planning to print this email please consider the environment before doing so, and whether you can print only the parts you really need. <br>
<br>
This email and any attachment(s) may be confidential and may be legally privileged. Any opinions expressed are not necessarily those of the company. If you are not the intended recipient, please notify the sender immediately; delete it and do not disclose, distribute, copy, use or act upon it. <br>
<br>
Warnings: We may monitor incoming and outgoing emails as permitted by law. While we take precautions to prevent viruses being transmitted by email you should make your own checks. <br>
<br>
This message has been scanned for Kitcatt Nohr Alexander Shaw Limited (Registered in England Company Number 4342369) by MailController <u><font color="#0000ff"><a href="http://www.mailcontroller.altohiway.com/" target="_blank">http://www.mailcontroller.altohiway.com/ </a></font></u><br>
<br>
</blockquote>
<br>
</div></div></div>
</blockquote></div><br></div>