Options
Custom URL in Gallery settings should check for special characters
phaserbeam
Registered Users Posts: 452 Major grins
Hi...
When using a Custom URL in the GallerySettings with special characters depending on the local language the SmugMug view might not open a photo when click on a thumbnail. This depends on the browser being used.
It took me a while to figure that out, see Screenshot. Ü is a special character that can be replaced be ue in germany.
I was selecting the local event name as title which contains special characters (part of the German language). I did not take care about the CustomURL.
When i open that gallery in Opera browser a click on a thumbnail will not open the photo in bigger resolution on the right. In Firefox that is working. If i change the CustomURL only using characters from a-z and 0-9 everything is fine, even in Opera.
Not sure if that is a bug or a feature request. Would be nice if there is a URL-check in the gallery settings which will warn the user about characters that my not work in URLs in any browser.
When using a Custom URL in the GallerySettings with special characters depending on the local language the SmugMug view might not open a photo when click on a thumbnail. This depends on the browser being used.
It took me a while to figure that out, see Screenshot. Ü is a special character that can be replaced be ue in germany.
I was selecting the local event name as title which contains special characters (part of the German language). I did not take care about the CustomURL.
When i open that gallery in Opera browser a click on a thumbnail will not open the photo in bigger resolution on the right. In Firefox that is working. If i change the CustomURL only using characters from a-z and 0-9 everything is fine, even in Opera.
Not sure if that is a bug or a feature request. Would be nice if there is a URL-check in the gallery settings which will warn the user about characters that my not work in URLs in any browser.
0
Comments
Facebook
Google+
Twitter
Photo Blog
Maybe a problem with a certain template?
For sure not because after update ü by ue everything works. This is not a template problem.
As i mentioned it works in Firefox so i'm sure it is a browser specific problem.
That's why i mentioned a small warning like a little red text above the CustomURL-field that pops up when special characters are being used and that shows something like this: (Sorry for my english, the developers can use a better text if needed)
I'm now aware of this problem and will hopefully never use anything else then a-z and 0-9. Since the URLs are now case sensitive in new SM special characters may just be another problem.
When I said it might be a template issue, than because as said browser should be aware of special chars (e.g. umlauts), but maybe a template behaves different and prevents browser to escape / encode the characters. According to RFC 3986 special chars have to be percent-encoded. For example "ü" to "%FC".