We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

Slimbox works fine in FF, but not in IE

    • 25876
    • 79 Posts
    s1Mon Reply #1, 18 years, 10 months ago
    hey there,

    sorry I have to bother you again. Worked several hours on my galleries and finally got them working like I wanted, UNTIL I opened the page with the Internet Explorer (7)

    the slimbox popup just doesn’t work properly ... watching it in FireFox, everything is alright, but in IE the background just doesn’t get darker, the images always load on the very top of the page and so on ...

    but I think it’s best if you go and see for yourself: http://ncd291.eden1.netclusive.de/simon/rw-interaktiv/index.php?id=50
    (click on the thumbnails)

    Does anyone know what that could be?

    Thanks a lot,
    Simon
      • 25876
      • 79 Posts
      s1Mon Reply #2, 18 years, 10 months ago
      doesn’t somebody know? sad
      Really don’t wanna stress, but it would be quite urgent ...
        • 27708 MODX Staff
        • 2,502 Posts
        Jay Gilmore Reply #3, 18 years, 10 months ago
        Are you calling MaxiGallery twice on the page? Your page seems to be calling slimbox and mootools twice this can cause problems in IE7 and Safari try eliminating the second call to the js files. There is a parameter to omit the JavaScript calls &disable_js_libs. If you are not calling MG twice did you put the js calls into your template?

        On looking at your HTML source I noticed that you have made no Doctype declaration and this will send IE7 into quirks mode and there can be unexpected rendering issues when in quirks mode.

        Never mind that you have a rather big bowl of tag soup with deprecated attributes such as bgcolor, leftmargin and more...

        Try removing the double calls first then move on to suggestion two.
          Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
          • 7923
          • 4,213 Posts
          doze Reply #4, 18 years, 10 months ago
          The javascript duplicating was a bug in 0.9.6.. I would suggest to update MODx to 0.9.6.1, though I cannot confirm if your issues happen because of the duplicated js libs..


            "He can have a lollipop any time he wants to. That's what it means to be a programmer."
            • 25876
            • 79 Posts
            s1Mon Reply #5, 18 years, 10 months ago
            thanks for the answers.

            just updates to 0.9.6.1, didn’t help anything.

            and yes, I have double MG calls on that page, because of the single thumbs I wanted there.

            the "main" call is:
            [!MaxiGallery? &display=`embedded` &embedtype=`slimbox` &pics_per_row=`0` &max_thumb_size=`60` &max_pic_size=`0` &thumb_use_dropshadow=`1` &thumb_shadow_bgcolor=`FFFFFF` &css=`assets/snippets/maxigallery/templates/default_sim.css` &galleryPictureTpl=`` &manage_target=`57`!]


            and then i got a few other calls where the thumbs appear:
            [!MaxiGallery? &pic_query_ids=`1,2,3` &display=`embedded` &embedtype=`slimbox`!]


            huh
              • 27708 MODX Staff
              • 2,502 Posts
              Jay Gilmore Reply #6, 18 years, 10 months ago
              Mootools, Prototype, and most other JS libraries require that the DOCTYPE Declaration be set above the <html> element. Most DOM related JS libraries will not work 100% when IE6 and IE7 are running in quirksmode because they treat such documents as legacy html.

              I was being a little rude before in my previous post about your code being tag soup but the fact of the matter is that if you are using strict doctypes and valid (x)HTML you will have a far easier time of debugging. You have some things that could throw off the DOM but you will not know which it is because there are general issues of outmoded html authoring being used.

              My suggestion is that you first try just setting a doctype of XHTML 1.01 Strict and see if that fixes it. It won’t validate but it will at least see if that is the problem with your slimbox.

              I have read that smoothgallery wont work without the Doctype declaration.

              Hope this helps.

              Jay
                Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup magician. Blog ✦ Twitter ✦ LinkedIn ✦ GitHub
                • 7923
                • 4,213 Posts
                doze Reply #7, 18 years, 10 months ago
                Yes, you need a doctype for sure.. transitional should work just as good.. if you don’t know what a doctype is, see http://www.w3schools.com/tags/tag_doctype.asp and http://www.alistapart.com/articles/doctype/


                  "He can have a lollipop any time he wants to. That's what it means to be a programmer."
                  • 25876
                  • 79 Posts
                  s1Mon Reply #8, 18 years, 10 months ago
                  guys, I thank you so much for the help!!

                  It really was because of the doctype ... never considered the doctype as much important, now i do.

                  I used XHTML 1.0 TRADITIONAL, cause STRICT caused problems with the tables in FF, however
                  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">


                  @smashingred: No, you’ve not been little rude ... you’ve been exactly right, this page is a tag soup because of several reasons ... I just implementet MODx afterwards and was somehow too lazy to re-code everything ... just wanted the side to quickly get working; A mistake maybe, but my lecture for the next few weeks will be XML and w3 standards wink

                  so, thanks again!