Maybe someone can confirm if this is a Shadowbox problem, but my images based on Shadowbox stopped loading after I applied the latest Drupal core security update 7.20. There is a warning and solution in the Release Notes:
Unfortunately suggested fix overwrites security measure provided by the 7.20 release.


Has anyone tried using it on D 7.20? Now 7.21 was released, but my photo gallery with shadowbox still doesn't work unless I set "image_allow_insecure_derivatives" to "TRUE" in settings.php. This is not a good thing and it has to be fixed. By "doesn't work" I mean that all thumbnails look fine, but when I click on any of them it just says "loading" and it stays like this forever.

Status:Active» Postponed (maintainer needs more info)

You can try the new dev version of Shadowbox, 7.x-4.x-dev

If with that version you still have problems then this issue is not a shadowbox issue but something else.

Shadowbox use the image_style_url function to create the derivative images so it should not be affected by that security update as explained in the security update documentation.

If this new dev version doesn't solve the problem then more information is needed about what you use to implement your galleries, any other module?

Status:Fixed» Postponed (maintainer needs more info)

Thank you very much for your reply. I just updated the Shadowbox to 7.x-4.0-rc1. I see that both rc1 and dev versions were released on the same day, so I decided to try RC1 first. I removed the line in my settings.php file which was meant to bypass security measure introduced with core 7.20 and tested the photo gallery. It works fine now. I guess the latest Shadowbox module update fixed the problem.
Thanks again.

Status:Postponed (maintainer needs more info)» Fixed

Status:Postponed (maintainer needs more info)» Fixed

There was a minimal change on the code that I was almost sure was the problem. Glad it was resolved.

Thanks for the review.

Status:Fixed» Postponed (maintainer needs more info)

I'd like to add this information to, so just to confirm, is the situation that 7.x-3.x versions of the module won't work, but upgrading to 7.x-4.0-rc1 or higher will?

Can others confirm that 7.x-3.x doesn't work with Drupal 7.20+? And if it doesn't, would it make sense to have a fix in that branch too (since it's currently the recommended release on the project page)?

I added the fix to 7.x-3.x branch too before releasing the new versions, so it should work fine too in 7.x-3.0-rc2. But indeed it will be better if someone can confirm it works.

Sorry for not adding the patch.

I link the corresponded commits where we can check the diffs.

The commit in the 7.x-3.x branch is the following:

The commit in the 7.x-4.x branch is the following:

Thanks. I can confirm that commit is in 7.x-3.0-rc2, so most likely it works, but I haven't tested it myself.

I'll update the Drupal 7 release notes, but mention there that it still needs final confirmation and testing.