As I've mentioned before here end here, things seem to be moving towards the use of the ../site/all/libraries path for storing external libraries (and gracefully falling back to local module path if that fails). I am referring to the Libraries API project. So, I am creating this issue as a to-do reminder.

I am aware that right now there are some quite serious issues that need to be addressed and the only/easy solution so far seems to be using our own, custom version of the plugin. I am talking about #745252: IE issues with 1.3.1 (slow-down/crashes) & #952668: Future upgrades, buggy Fancybox v.1.3.2 that strive to bring the latest 1.3.x version of the plugin into play. This solution might be perfect for releasing a stable(ish) version of the module sooner, but I think that it will come back and bite us later on. What I think sounds more promising and future-fail-proof is the use of code that overrides things we need to change during runtime (like what is mentioned here).

Anyways, here it is! Feel free to postpone it till after we get a stable out or even bump it to 7.x, but do keep in mind that most of our audience/beta-testers (in fact almost all of them) are in 6.x at the time of writing this.