http://www.shadowbox-js.com/index.html
Today, I decided to add a photograph section to my website using a Flickr plug-in for WordPress. set up my Flickr API…Everything worked, but the stock lightbox gallery just felt too common. I then came across the shadow box plug-in for WordPress which is supposed to work along with the Flickr plug-in. However there was one glitch. The arrow buttons didn’t work in the gallery. The look of shadowbox was perfect so I needed to figure out a way to get this to work. I figured it was some type of JavaScript conflict. I cut out all of the JavaScript code inside of the head tag and then tested the shadow box. it worked. So what I did next was slowly added chunks of code back into the head tag. Using this process of elimination, I singled out the bgstretcher as the conflict. Now I was faced with a dilemma. Should I keep BG stretcher or shadowbox. I wanted to keep both. I tried to come up with a workaround for this somehow. But the thousands of lines of code for these plug-ins was too overwhelming. I tried to change the wrapper for the BG stretcher but that didn’t work either. After some googling I found the original shadowbox website. I figured I might as well give it a shot. I deactivated the shadowbox plug-in for WordPress and manually installed shadowbox to my WordPress theme. and finally it works with BG stretcher. I think I learned something from all of this. many WordPress plug-ins are actually based off of the original non-WordPress plug-in. It seems like the WordPress versions often come into conflict with other plug-ins and require a lot of tweaking whereas the original versions are less prone to bugs. I pretty much went through the same process when I was installing BG stretcher.