jQuery<\/a> library (currently 1.7.2, used by Lightbox 2), CSS styles and finally Lightbox’s JavaScript code. Due to the fact I could not insert link tags directly into the content, I accomplished this by printing the code using JavaScript. The latter does not influence on having multiple jQuery libraries on a page, but it needed to be done in my case and seems a nice workaround :).<\/p>\nThe problem was that CMS is using jQuery of version 1.5.2, but Lightbox needed 1.7.2. Because I could not upgrade 1.5.2 version to the latest, I had to separate these two libraries. I also could not just simply override the old one because other parts of CMS generated page stopped working. This can be achieved by loading the second library into a variable. Into the upper javascript I added the following:
\n
\nvar $jq172 = jQuery.noConflict(true);
\n<\/code>
\nAs you maybe know, the jQuery functions can be called by $()<\/em>. After this command, the formerly loaded jQuery can be accessed through $()<\/em> and last added library as $jq172()<\/em>. If the parameter to the noConflict function is true, the previous library is intact, otherwise it is overwritten.<\/p>\nLastly I needed to apply minor change to lightbox.js to instruct the script to use 1.7.2 library. Due to the nice coding style I just needed to change the line 46 into
\n
\n$ = $jq172;
\n<\/code>
\nBy applying all these I was able to have working Lightbox 2, working previous CMS scripts and having done everything without ant CMS code change. The Lightbox library can be then used completely normally.<\/p>\n