I have been trying out the Fully skin and came across a problem - when I click on a thumbnail, it should change the main image to correspond with it. This happens when testing locally on my computer, but does not work when on a server.
I traced the problem to the code where the location.hash is changed in the onThumbClick function. The window.onhashchange function that is set in the initSkin function in main.js which is supposed to handle this event has been overridden by some hidden code in the widget container. Specifically it is set to:
I now have a license and I can confirm that using the standard Fully skin without widget support, having uploaded the album to a server, clicking on a thumbnail does change the main picture as intended.
With widget support enabled, clicking on a thumbnail does not change the main picture. However, this only happens on the second and subsequent visits to a page.
It's a caching problem. I've seen IE do things like this before - in trying to be "efficient," it caches things it shouldn't. In this case, the problem appears to clear up if you simply force a reload by hitting F5.
Pressing F5 to force a page reload restarts the skin's script and resets the onhashchange handler so that the click event works again. But if you click on another folder and back, then thumbnail clicking stops working again. Whether the page reloads from the cache or the server would do the same.
I can set a breakpoint in the script using the debugger at the point when the click event takes place and can see the onhashchange handler has been reassigned from what the skin's author intended, as I first pointed out.
What I can't see is the code in the widget container because that gets loaded by an unconventional means and in any case I don't think I should be trying to debug that. But it obviously interferes with the skin's script.