Migrate from Image Module galleries to Node Gallery/Imagefields

It will require custom code to create gallery nodes and to attach the image nodes to these. You'll have to traverse the gallery taxonomy vocabulary and create a node for every term, as well as "register" the nodes to these gallery nodes afterwards.

If you want, and are willing to invest some time yourself, we can try to build some code together in this issue. At some point, I'll migrate one of my existing sites to NG3 from image.module, and will need similar code as well.

One additional problem would be that gallery hierarchies are only planned for NG 3.1.

I've never used Acidfree, but I have something that may be of help.

I've a views_bulk_operations junkie, and since I'm the maintainer, I made sure that NG3 worked with it. In NG3, we expose an action that can assign images to galleries. So, if you can come up with a way to isolate images using VBO's filters, then you can do this all via the gui.

However, this sounds like it would be a pretty quick and easy drush script. Once the gallery and image types are part of a relationship, nodeapi takes care of the rest. POC code:

$acidfree_gallery_nids = get_acidfree_gallery_nids();
foreach ($acidfree_gallery_nids as $afnid) {
  $gallery = new stdClass;
  $gallery->gid = $afnid;
  // create the row in node_gallery_galleries
  drupal_write_record('node_gallery_galleries', $gallery);
  node_save($gallery);
  $image_nids = get_acidfree_image_nids($afnid);
  foreach ($image_nids as $image_nid) {
    $image = node_load($image_nid);
    $image->gid = $afnid;
    node_save($image);
  }
}

That's all you need to do to build the linkage between gallery and image, but obviously the bulk of the work is in the unwritten get_acidfree_gallery_nids() and get_acidfree_image_nids() functions. If you have a truly large number of images and galleries, I would definitely run this via 'drush scr' so you don't run into execution time issues.

BTW: you're Andy, right?

Here's those functions, and a script to boot: http://pastebin.com/0L8RcZmC

scroogie can help you with the image.module to imagefield migration, since he needs to do it anyway. Here's the basics of what you'd do:

1) Install Node Gallery, leave the defaults.
2) Run the script above.
3) Run scroogie's script to convert images to imagefield
4) Uninstall the Acidfree module
5) Enjoy

I didn't test that script above, so please don't even attempt with it until you are working on a development copy of your live site.

To run it, download and install drush according to the docs. Change to your drupal install root, and place the script linked above in a file named acidfree_migrate.php. Then run 'drush scr acidfree_migrate'.

The script needs some more work to retrieve the title of the gallery, author, etc. I think you should start with acidfree_get_vocab_id() and then taxonomy_get_term() your way through the galleries. I used acidfree only in Drupal 5, quite some time ago.

Well, that's good progress. Next step, create the gallery nodes.

Try using http://drupal.org/project/taxonomy_node to create a node_gallery_gallery node for each of your terms.

Post back whether that succeeds or not. If it works, then it should be a pretty simple script to get the images into the galleries.

Okay, wrt "The node_gallery_gallery type is already part of a relationship.", that was a validation bug that I've fixed in dev.

As for your problem in saving, I'm not for sure where the problem is at. Can you give me:
1) The content types in your relationship
2) The content type of the image you're editing
3) What user you're editing the image with
4) The title of the gallery you're selecting in the "Assign to Gallery:" select box
5) The content type of the gallery selected in 4)

Oh, and of course, clear your caches first if you haven't already.

@yngens - I commited the fix for 'The node_gallery_gallery type is already part of a relationship' this morning, you'll need a dev build after that.

I found and fixed the bug in dev that was causing yngens to not be able to manually assign pre-existing image nodes to galleries. @yngens, I left the fixed file in place on your server, so you don't need to wait for a dev build.

http://pastebin.com/rLN3tYj5

You owe me a lot of beer, or a lot of documentation :)

Put that script someplace, like /tmp/ng_migrate.php. cd into your drupal root directory, and run the script: 'php /tmp/ng_migrate.php'. In it's current form, it will not change anything, just print out how many images it finds for each gallery.

If that looks right, remove the comment from the drupal_write_record() and the node_save() lines. PLEASE FOR THE LOVE OF GOD BACKUP YOUR DB FIRST. I haven't tested it - it should work, but I claim no reponsibility for anything in it.

If that script works, please post the code back to this issue for safekeeping.

Updated the link above to http://pastebin.com/rLN3tYj5

This should be more efficient on memory, and also skip any images that are already part of the gallery.

RE: user profile: http://drupal.org/project/node_gallery_user_profile

Shouldn't need batch API if you're running at the command line with the cache clearing that the new version does.

That's right - one gallery per image, no subgalleries. So, regarding #20, 1, 2, and 3 are all correct afaik. The error in #21 is non-fatal, it just means that we're looking inside an empty gallery.

Looks like this is a known views issue: http://drupal.org/node/989092

subscribing

Is there an update on this? I am now in exactly the same position of migrating image galleries from Image and Image Gallery to Node Gallery.

I have got as far as migrating all the images to use image field, so now I just need to create the gallery nodes and build the relationships of images to galleries. Things should be a little simpler for me as I have a 1:1 image:gallery relationship and no user galleries to worry about.

Is the script linked in #19 still the best way to go? How did you get on with VBO, was that better? It would be great to see updated/definitive scripts posted back here.

Ok, here is the script that I have written to do the migration in a (hopefully) safe manner. I've run it a few times and all seems to work, but YMMV.

Perhaps this should go into a documentation page?

/**
* @file
* Migrate all image galleries from using Taxonomy terms to Node Gallery nodes.
* This script will traverse a given vocabulary, create Gallery nodes if needed
* and link image nodes to the relevant gallery.
* 
* USAGE
* -----
* - Backup your Drupal database.
* - Edit the 'Configuration' section below.
* - Place this script in the root of your Drupal site.
* - Run the script by requesting, e.g. http://<yoursite>/ng_migrate.php
* - Re-run the script if necessary (if it did not complete)
* - You are free to remove/tidy up your old gallery vocabulary
* 
* LIMITATIONS
* -----------
* - This script is designed to work with Node Gallery 6.x-3.0. As such, it only supports
* a 1:1 image:gallery relationship and does not support nested galleries.
* - It doesn't migrate the images themselves (from image to imagefield).  To do that, see
* http://drupal.org/node/432860 and http://drupal.org/node/201983
* - This script should be run once you have migrated your images.
* - While it will move the taxonomy description to the gallery node body, it will not correctly
* populate the teaser field.  That will only be set and displayed once the gallery node has
* subsequently been edited.
* 
* AUTHORS
* -------
* justintime (http://drupal.org/user/99149)
* nasi (http://drupal.org/user/5712)
*/

// ***** CONFIGURATION *******

// The taxonomy id of your Image Gallery vocabulary
$vid = 8;
// THe user with which all new galleries should be created
$uid = 1;

// ***** END CONFIGURATION *******

require_once('includes/bootstrap.inc');
drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);

$total_images = 0;
$galleries = 0;
$gallery = new stdClass;
$sql = 'SELECT DISTINCT(n.nid)
  FROM {node} n
  INNER JOIN {term_node} tn ON n.vid = tn.vid
  WHERE tn.tid = %d';

// Get the list of terms for the given tid
$terms = taxonomy_get_tree($vid);

foreach ($terms as $term) {
	// See if a gallery node already exists for this term
	$gal['title'] = $term->name;
	$gallery = node_load($gal, NULL, TRUE);
	if (!$gallery) {
		printf("Gallery: '%s' does not exist.<br/>\n", $term->name);
		// Create a new gallery node
		$gallery->title = $term->name;
		$gallery->body = $term->description;
		$gallery->type = 'node_gallery_gallery';
		$gallery->uid = $uid;
		node_save(&$gallery);
		if ($gallery->nid) {
			$galleries++;
			printf("Gallery: '%s' CREATED<br/>\n", $gallery->title);
		} else {
			printf("Gallery: '%s' creation FAILED<br/>\n", $gallery->title);
		}
	} else {
		printf("Gallery: '%s' already exists.<br/>\n", $gallery->title);
	}
	// Find and attach all images in this gallery
	$gid = $gallery->nid;
	$images = 0;
	$result = db_query($sql, $term->tid);
	while ($row = db_fetch_object($result)) {
		// Check if this image is already in the gallery
		if (in_array($row->nid, node_gallery_get_image_nids($gid, FALSE, FALSE, TRUE))) {
			continue;
		}
		$image = node_load($row->nid);
		$image->gid = $gid;
		node_save($image);
		$images++;
	}
	printf("Gallery: '%s': Migrated %d images.<br/>\n", $gallery->title, $images);
	$total_images += $images;
}
printf("<br/><b>Migrated %d galleries and %d images to Node Gallery</b>\n", $galleries, $total_images);

Adding to documentation queue - thanks for the contribution!

subscribing

One additional limitation worth pointing out (that I have since discovered); This script will not populate the teaser field of the new gallery nodes. So gallery descriptions will appear in the gallery body but not in teaser displays.

The way I solved this was to edit and save each gallery node by hand, but that would be impractical for a site with a lot of galleries. So anyone planning to use this script on a large scale may want to first work out how to also save the teaser, correctly truncated.

I have edited the script above to reflect this.

updateing component