Hi All!

I've got an existing standalone G2 under a non-drupal domain/subdirectory structure '/a'. I am the only 'user' there - all the albums are mine.

I want to move a certain subset of nested albums to another domain/subdirectory '/b' on the same physical server. D6, G2 and Gallery module seem to work fine under new domain.

So I'm looking at /g2data/* in /a domain.

Gauging just by filenames I -think- I ought to be able to move just that /albums subdirectory, but not all of them, only the ones I want.

The 'problem' I half-think I see is that pointing the new D6 G2 config.php to the 'previous' database will turn up albums that don't exist in the new domain.

So, might that cause anything to puke on my shoes?

The only other brute force easy fix I can think of is to copy -all- existing albums from one directory structure to another and copy the -whole- existing mysql database to a new database. With that the new domain D6 G2 should be happy - and then delete the 'unwanted' albums from the new domain via G2.

Buuuut in al this mess it's also unclear how/when I should use the D6 G2 'sync' tool?

I know I can't break/lose anything but I hesitate to waste a lot of time with trial/ERRORS. Meaning, I don't know what kind of information is stored in the current G2 -db- that'll have a cow of I muck around with different -directory- structures.

Thanks much. Have a :) day!

Jim
jb@jbarchuk.com