Very strange. The problem seems to be triggered by a combination of factors - the
.top domain, plus something else. As I said, FB doesn't complain if I create a
Tiger album and post a link to it, but I have normal domains, like
.com and
.net.
Please do two tests, that will help narrow it down.
First, use a text editor to edit your index.html page manually, and remove the widget script lines, lines 90-106:
<script>
_jaWidgetBarColor = 'black';
$(document).ready(function(){
REL_PATH='';PAGE_NAME='index.html';
$.ajaxSetup({cache:true,contentType:false});
$('body').removeClass('stop-transitions');
$('#main').skin({"albumName":"Prywaciarze"....
if (window.innerWidth < 640 || Modernizr.touchevents)....
$('[data-tooltip]').addTooltip();
$('[data-modal-open]').on('click', function(e){
var t=$(e.target).data('modal-open');
if(t&&(t=$('#'+t)).length){$('body').modal(t);}
});
$('[data-ask-permission]').askPermission();
});
</script>
Now try to link to the album from FB. Does it still give an error?
(Laza, if you're reading this, why does
Tiger "helpfully" insert the widget code, even if I tell the jAlbum core
not to include widget support?)
Second, make an album with a non-Laza skin, and see if that also creates problems. Try something that doesn't rely on JSON files at all, like
Neptune.
