We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 29703
    • 217 Posts
    Hi all,

    I’ve just finished a site, but am having problems with it displaying properly in IE7. It works fine in IE6 but in 7 it seems to partially load then displays an error.

    The site is www.gorselodge.com

    I can’t begin to work this out as I’m using IE8 beta in IE7 rendering mode and it just brings up an error which is relevent to IE8 (I think).

    Any help would be greatly appreciated.

    Thanks.
      • 32646
      • 87 Posts
      Internet Explorer cannot display the webpage

      Most likely causes:
      You are not connected to the Internet.
      The website is encountering problems.
      There might be a typing error in the address.

      Good old IE ! That is as specific as it gets. Could you try turning things off one at a time to pinpoint the problem? It has to be in one of the scripts. Replace the SWF with a static picture temporarily, etc.

      Beautiful website. Out of curiosity, why are you using flash when Smoothgallery in MaxiGallery would do the same thing?
        Just learning the ropes.
        • 10487 MODX Staff
        • 1,535 Posts
        I’ll put money on it being a javascript-related error - basically, you have some javascript that is trying to manipulate the DOM before it’s fully loaded. I suspect this code is the root of your problem:
           var so = new SWFObject("assets/templates/gorse/flash/banner.swf", "mySwf", "846", "293", "8", "#000");
           so.addParam("wmode", "transparent");
           so.write("mySwf");

        To sort it out, make sure you set the code to run when the DOM is fully loaded (looks like you have mootools available so you can use addEvent() and the ’domready’ event - check mootools documentation for correct syntax)
          Garry Nutting
          Senior Developer
          MODX, LLC

          Email: [email protected]
          Twitter: @garryn
          Web: modx.com
          • 29703
          • 217 Posts
          Quote from: garryn at Mar 25, 2008, 07:23 AM

          I’ll put money on it being a javascript-related error - basically, you have some javascript that is trying to manipulate the DOM before it’s fully loaded. I suspect this code is the root of your problem:
             var so = new SWFObject("assets/templates/gorse/flash/banner.swf", "mySwf", "846", "293", "8", "#000");
             so.addParam("wmode", "transparent");
             so.write("mySwf");

          To sort it out, make sure you set the code to run when the DOM is fully loaded (looks like you have mootools available so you can use addEvent() and the ’domready’ event - check mootools documentation for correct syntax)

          It seems that it is absolutely the SWFObject that is screwing it up.

          I don’t suppose anyone knows how to implement the AddEvent() and the ’domready’ from Mootools into this context. I haven’t really had a chance to look into Mootools and my javascript knowledge is way below average. I looked at the documentation to no avail.

          Thanks for the help by the way smiley
            • 10487 MODX Staff
            • 1,535 Posts
            Thought it would be wink Try this in place of your current code (untested but should work):
            window.addEvent('domready', function() {
               var so = new SWFObject("assets/templates/gorse/flash/banner.swf", "mySwf", "846", "293", "8", "#000");
               so.addParam("wmode", "transparent");
               so.write("mySwf");
            });
            
              Garry Nutting
              Senior Developer
              MODX, LLC

              Email: [email protected]
              Twitter: @garryn
              Web: modx.com
              • 29703
              • 217 Posts
              Quote from: garryn at Mar 25, 2008, 07:49 AM

              Thought it would be wink Try this in place of your current code (untested but should work):
              window.addEvent('domready', function() {
                 var so = new SWFObject("assets/templates/gorse/flash/banner.swf", "mySwf", "846", "293", "8", "#000");
                 so.addParam("wmode", "transparent");
                 so.write("mySwf");
              });
              


              Thanks for the help. I’m getting the following error:

              Parse error: syntax error, unexpected T_STRING in /content/DesignerPlus/g/o/gorselodge.com/web/manager/includes/document.parser.class.inc.php(769) : eval()’d code on line 18

              As I say, my javascript skills are substandard, so it is undoubtedly something simple. A live example is currently online.

              Thanks!
                • 6726
                • 7,075 Posts
                I use SWFObject for a website of mine and it works fine with IE7 with this call


                <script type="text/javascript">
                	// <![CDATA[
                
                		var so = new SWFObject("assets/flash/intro-sworld.swf", "sotester", "648", "357", "8", "black");		
                		so.write("flashcontent");
                
                	// ]]>
                	</script>


                You can see it running here :
                http://sworld.com

                This being said, I’ll try Garry’s code as it looks less "hack-ish" tongue

                Maybe the error has to do with the [tt]so.addParam("wmode", "transparent");[/tt] which I don’t have...
                  .: COO - Commerce Guys - Community Driven Innovation :.


                  MODx est l&#39;outil id
                  • 25663 MODX Staff
                  • 12,272 Posts
                  Since IE8 is also in beta, there is the possibility that it’s not 100% baked yet either.
                    Ryan Thrash, MODX Co-Founder
                    Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                    • 29703
                    • 217 Posts
                    Okay thanks for all the ideas.

                    Seemingly when I remove maxigallery from the page the problem stops, so it’s probably a conflict between the Mootools call and the SWFObject call?

                    Why would this be and is there a way to resolve it? Surely people have used SWFObject and Maxigallery on the same page before?

                    Thanks again.
                      • 29703
                      • 217 Posts
                      Thank you everyone for your quick and unwavering assistance!

                      In the end it seemed to be a conflict between ’Slimbox’ and ’SWFObject’.

                      I decided to change the Maxigallery call to use ’&embedtype=`lightboxv2`’ and everything works okay.

                      Thanks again!