Page 1 of 1

Different source path for a folder (aka folder aliases)

Posted: 17 Jan 2011, 13:22
by locher
Hi!

First of all, thanks for the great gallery: I've just set up the latest version on my site, and I really like it.

However, it seems like I need a feature which does not exist in the current Imagevue.
It would be great if it was possible to specify a different source path for the contents of a specific folder - to separate the logical tree-structure of the image library from the underlying physical structure of folders on the website.

I'll explain the use-case. I have several folders in my "content" folder, let's say "Nepal" and "Nepal-2010". I've decided to re-organize the structure of the gallery and create a top-level folder "Travel", then a sub-folder "Nepal", and two subfolders in it: "2009" and "2010".
I can easily create such structure and simply move my existing pictures into the new folders. However, in this case I am getting a problem: I have a lot of direct external references to the existing files (I usually insert the pictures into my blog posts), and they will be broken if I mode the pictures.

So, it seems like I need some kind of an "Alias" to an existing path, so I can leave physical images where they are now and create a different logical structure to access them from the gallery menu and the URL string.

Right now I try to achieve similar behavior by hiding old folders and creating new ones as internal links. However, internal links do not work in HTML-mode (is that a known issue?).
Also, link-folders do not change the URL. In the example above, I want the folder "/content/Nepal" to be displayed by the URL "www.mysite.com/#/content/Travel/Nepal/2009", but using link-folder will just redirect the user to "www.mysite.com/#/content/Nepal", which is not what I exactly want.

I hope the explanation is clear enough. Also hope that this feature will be useful not only for me :)
Thanks

Re: Different source path for a folder (aka folder aliases)

Posted: 18 Jan 2011, 00:30
by mjau-mjau
Unfortunately, Imagevue is integrated with a file-based system, so it needs to physical paths to function properly. If they are changed, the specific link to the gallery needs to change also.

This is the same issue that most website developers have to face when they change the URL for the pages of their website. The mostly used solution for this is 301 redirects which can be set up on your server. Basically, it tells your server to redirect one specific call to another, for example you could have "/content/path/" point to "/content/path/2001". I found two tutorials on it here:

http://webdesign.about.com/od/htaccess/ ... direct.htm
http://www.techtalkpoint.com/articles/h ... re-domain/

Unfortunately, there is no other logical approach currently if you want to try and use the Imagevue system. Basically, when you use #/content/path/, it will simply try to load the content of the path provided. At least, if you have incorrect external links, they will still go to the gallery ...

Re: Different source path for a folder (aka folder aliases)

Posted: 18 Jan 2011, 09:27
by locher
Thanks. I will look at the 301 redirects for my web-server.

But the question with the internal links still remains open: I am unable to set a "view-independent" link-folder to some other page of my gallery: the link will either be flash-based ("/#/content/path") or html-based ("/?content/Maslo/"), so the link will work either in flash or in html, but not in both.
Is there a way to fix it?

Re: Different source path for a folder (aka folder aliases)

Posted: 18 Jan 2011, 10:58
by Nick
Good point, right now this is not implemented yet, but we're working towards it.