Talk:Gallery2:migration - Gallery Codex
Personal tools


From Gallery Codex

General Comment: using the g1/g2 is confusing, especially after we have instructed renaming a folder to "g1"

Step 3: Run the find orphans script on your g1. Fix any problems that it found.

Where is this script and how do you run it?

Log in to gallery as administrator and click "admin page" near upper right of page. You'll see several choices, one of which is "find orphans".

Step 5: Go to your new g1 location and fix your config so that it works in the new location.

"What does it mean to go to the g1 location? How does one 'fix your config' so that it works in the new location? Does this require running the Configuration Wizard?"

This page has been updated now with instructions on modifying the config.php.

Pov says: "If your import stops on an image without any message nor log in the apache log verify the length of the title of the image it's stopped on. Titles in g2 are limited to 128 characters (at least in PostgreSQL, not sure in mysql or oracle). Characters not in the range of iso-8859-1 are encoded as html entity and can occupy more than 1 char in the database."

G2 does entity safe truncation during migration, so long titles should not cause problems (they'll get truncated, and you'll be notified). Pov, did you find a specific case where this did not work? We can/should/will fix that :-) --Bharat 20:55, 15 October 2005 (PDT)

I wresseld with the g1->g2 migration for a day before I watched the serialized file from g1 into an editor and found that there was no problem in it, of course the G1 verification scripts found no orphans or missing image. Then I watched in psql the schema of the db and found that the title column was varchar 128, so I tried to shorten the title of the image who blocked the migration and it worked. The part I removed was purely ASCII so it wasn't the problem. But when I checked my title was longer than the allowed 128 chars. BTW the html entities were not decoded during the import, that would have helped to make the problem less noticeable (and more importantly help me gain some time finishing the import).

Pov 06:16, 16 October 2005 (PDT)


I incorporated some of these comments (esp the g1/g2 language), added some corrections based on my experience and refactored the page. I hope you feel it is an improvement.

Uslacker 21:05, 20 May 2006 (PDT)

Looks good to me. Thanks, Uslacker! --Bharat 10:58, 21 May 2006 (PDT)

Move (rename) from "migration" to "Migration"

I would suggest moving (renaming) the page from "migration" to "Migration" for proper capitalization. -- Zimzat 17:23, 11 July 2006 (PDT)

What is the scope of this document?

Looking at this document, it's not clear if it applies to Gallery 1.5.x --> Gallery 2.0, or if it applies to Gallery 2.1.x, or the forthcoming 2.2.0



1.x to 2.x

The first heading in the article is "Migrating from Gallery 1 to Gallery 2". --Mindless 08:48, 11 March 2007 (PDT)


The guide worked really well for me, thanks to the contributors for writing it! I just have the following comments regarding the import module :

  • There is no "submit" button on the import prep page - now it is the "Prepare import" button.
  • There seems to be no "choose objects" page for the migration module, the first page lets you choose everything you need to. So step 3 of the import sections is not applicable, as far as I can see.
  • To confirm the import there is no submit button, it is now the "Confirm migration" button.


  • The albums, once imported, will not be in the same order as they were in g1. But that can be fixed by rearranging.

Other than that, well done! It is a good guide and I am running gallery 2 now. Woot!

--Ftclausen 03:31, 14 February 2008 (PST)

Upgrading from 1.5.1 to v2, and it's been a loooong time since the initial install, so some of the instructions leave me a bit clueless. Like:

Rename your Gallery v1 application folder (likely '../gallery') to "g1" (We will use the original gallery folder for the Gallery v2 install). Modify your web server configuration to reflect the folder change if necessary. You may also need to modify your "g1" .htaccess file if you were using mod_rewrite for search-engine friendly URLs.

My questions:

How do I know if the config modification is necessary? What modification would I make? Same questions for the g1 .htaccess mod.

--Littlewilson 18:00, 28 July 2008 (UTC)