We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 15914
    • 145 Posts
    Well spotted... I need new eyes.
      Kunal Kapoor
      Technical Director
      Limesharp Internet Limited - Effective, Functional, Standards Compliant

      IRC Nick: KingKoopa
      Skype ID: KingKoopa16
      • 16429
      • 254 Posts
      A question.
      Looking at the times the snippet was posted, I’m wondering if I’ve to replace the document.parser.class.inc.php file in MODx version 0.9.2.1or it is up-to-date and doesn’t need replace with yours.
        kudo
        www.kudolink.com - webdesign (surprised?)

        [img]http://www.kudolink.com/kudolinkcom.png[/img] [sup]proudly uses[/sup] [img]http://www.kudolink.com/modx.png[/img]
        • 15826
        • 160 Posts
        I just had a duplication of the problem Briggsy had. Product two almost immediately pops up the popup window with the larger image, where product one just darkens the screen and the loading bar just sits and spins. Win2k and Firefox 1.5.0.4, and I opened in a new tab.

        I’ll try clearing cache.

        I just cleared cache, and clicked the link, and this time it opened in a new window. I clicked product one, clicked the image and everything was fine. Weird.

        So it’s definitely a caching issue.
          "I’d love to change the world but I can’t find the source code . . ."

          Custom ModX Templates
          • 7923
          • 4,213 Posts
          Quote from: kickass at Jul 26, 2006, 02:46 PM

          I just had a duplication of the problem Briggsy had. Product two almost immediately pops up the popup window with the larger image, where product one just darkens the screen and the loading bar just sits and spins. Win2k and Firefox 1.5.0.4, and I opened in a new tab.

          I’ll try clearing cache.

          I just cleared cache, and clicked the link, and this time it opened in a new window. I clicked product one, clicked the image and everything was fine. Weird.

          So it’s definitely a caching issue.
          This can happen if the javascript haven’t fully loaded yet. So if the connection was sluggish at some random page request and you click the image very quickly, it can happen.

          This can be avoided though by using dynamicCSS.js for example to hide the images until the needed scripts are loaded. This is done in the newest Slidebox and you could modify this snippet to use slidebox or better, modify lightbox to use dynamicCSS. It’s easy to do and takes just couple of minutes, take a look at slidebox-setup.js to see how its done (i.e. remove unneeded slidebox configurations and change .class selector name and slidebox_end_init() function name, save it as new and add to be included in site template as the first script to run) then in the end of lightbox init function call the renamed slidebox_end_init() function. Then wrap the images that needs to be hidden with divs that has the class name what you set in createStyleRule function.


            "He can have a lollipop any time he wants to. That's what it means to be a programmer."