URL Rewrite paths.

OK, mod_rewrite with Apache works, I have everything installed perfectly.

For my Gallery 1 I used to have real nice short clean URLS like:

http://domain.nl/albumname/imagename

and you would get the page with the sized image, and that was it!
Great, I really liked that.

My /albums folder was at the domain root for G1
and I have moved it to be /albums in the G2 root folder too.
I'm gonna import them from there.

How do I configure URL Rewrite to use the same short URLs for
newly added pics (instead of those long-winded URLs G2 defaults with)?
Plus how do they stay as they were for my G1 imported pics.

In the URL Rewrite plugin config I see the Migration G1 > G2
is set to %path% (and I can't change it, greyed out).
If I understand correctly I want %path% to be
my new image view URL as well, even for new G2 images.

What do I do?

G2 version is 2.2 RC1, and Apache gets to rewrite via htaccess. PHP 4.4.4

Bandwidth theft and image-stealing is fine with me.
I'll handle that in my own way. I don't even have
a problem with allowing access to my album folders
as indexed folders. Never been a problem for me.

Thanks in advance.

I already did, but it does not answer my question(s). At all.
Again: I want to have my URLs (so also the NEW ones) exactly like before,
furthermore, I prefer to have my image-files in the same locations, as actual files.
The config screen does not let me do that, because I cant enter
%path% and %path% in two of the boxes at the same time.
In fact, G2 asks me to put the actual files in an unreachable location,
which I do not understand, since Im putting imagefiles online in order
to get them seen, I dont care about them not being available,
Im making them available for a reason: They should be seen,
preferably even indexed by google.

G2 also makes the endings in the form of filename.jpg.html
while in my G1 install I had them as filename
(and nothing after it). Can I get rid of that .extension.extension addition?

OK, so why use the URL Rewrite mapping option at all then?
It seems to me it is doing something very stressful for the webserver, if I keep the Migration plugin enabled at all times. G1 is such a relief compared to how all this is done in G2. It all sounds way too complex and workaround-ish to me.

Here's what I would prefer instead:

- To not use ANY G1 > G2 URL mapping, let Google etc. index all of the images anew.
( Make the 404 go to the index of the gallery, so not found images can be found again via the main index.)

- To make the View image URL as short as possible, i.e. %path% for the main G2 URL.
Even when I'm not using G1>G2 mapping, I still can't get the %path% entry in there.

- Make the actual gallery data root the same as the G2 install root, so that folder
/albums/ is in the same physical location as it was before, and most jpg/png/gif etc.
are at the exact same location, so many direct links will still work. Only those for subalbums are now 1 directory deeper (as I've seen G2 do it now).

The security issue is a non-issue for me: I'm not running a gallery to hide stuff, I'm running it to publish stuff. ;-) In that I don't really care how people access my content. If it's through remote direct links, or fancy-index httpd folders, that's fine with me. Most of them I block through SetEnv entries anyway.

> > - Make the actual gallery data root the same as the G2 install root,
> > so that folder /albums/ is in the same physical location as it was before,
> while you can't do this in a physical way, you can use URL rewrite and some minor code changes to make URLs look like that.

Seems to me I can do this. I just give the data folder the absolute path of the gallery root dir. Sure, I might have to take out 1 htaccess file, but that's not a problem for me.