I've had success before with node_export and node_export_file (a sub module of node export) - it also has drush integration. The file sub module works well with filefield (imagefield) cck fields. The only issue is nodereferences refer to old nodes. Lee On Thu, 2010-08-05 at 19:16 +0100, Phil Glanville wrote:
> Hi all. > > > > 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. > > > 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. > > > 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? > > > Thanks for any help, > > > Phil. > > > > > > 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. > > 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. > > 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. > > This message has been scanned for Kitcatt Nohr Alexander Shaw Limited > (Registered in England Company Number 4342369) by MailController > http://www.mailcontroller.altohiway.com/ >
