Inconsistent handling of URLs with iframe

[Filip]

Hi guys,

trying to wrap my head around this:

http://kelarova.com/test.html

The links lead to the same page - first via index.php straight, the other uses the Nginx-handled clean URL that goes back to Textpattern. There is no difference in the headers returned by either of the URLs, I confirmed that with curl.

Yet the latter link will never be picked up by Shadowbox, and will fall back to a standard link. Does Shadowbox perform any logic that decides where a link is handled or not?

Regards,

Filip

[Filip]

I should say I can force Shadowbox handle the URL by changing the href to a JavaScript call using Shadowbox.open(). It just won't pick it up on its own.

[Filip]

I've realized where the problem is: it's failing on an URL that has more than a FQDN hostname, but doesn't end in a defined extension linked to a player. I.e. it ends in '/en/' instead of something '/en/index.html'. Sounds like a bug here - it should definitely recognize and support clean URLs (e.g. '/section/article-name') too.

[Wizzud]

I believe that the most recent version of Shadowbox defaults to the iframe player if no player has been specified, and if no match is found for any other player (the iframe player no longer has extensions associated with it).

[Wizzud]

You could also simply specify the desired player...

rel='shadowbox;player=iframe'

[Filip]

Thanks, I didn't bother checking for an updated version, as I downloaded mine just a few days ago. I see 3.0rc1 superseded 3.0b now, so that explains. Also, thanks for the player= tip, I didn't see that in the docs.