We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 36644
    • 22 Posts
    A month ago (I think) it was the first time that I notice that there were problems with viewing some website made with CMS MODX in Chrome and Safari (Firefox does well). All the websites have the newest update of MODX. (2.2.6).
    I thought maybe there is a problem with the newest php 5.3 and modx. Last year there was a update done by our hostingcompany. Do I have to change something in a (html) code to fix this and make php 5.3 works? Is there somebody who can help me to fix this problem?

    Thanks!

    regard, Henk-Jan
      • 3749
      • 24,544 Posts
      MODX doesn't do anything with your HTML and CSS code except send it to the browser. If there's a problem, it's likely something in your HTML and/or CSS code that is not completely cross-browser compatible. Have you validated your code here: http://validator.w3.org/? That would be the first step.
        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        If something works in one browser but not in others that means a Javascript or HTML error. Firefox is very forgiving; it will more-or-less render a page even if you have some bad HTML. If you do a "view source" in the latest versions of Firefox, it shows things in red to let you know there's something wrong. Some false positives, but still a quick way to generally validate your HTML.
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 3109 ☆ A M B ☆
          • 894 Posts
          Got a link and a better description of what exactly is the problem your experiencing? Browsers have different rendering engines and both Safari and Chrome use Webkit which seems to be the browsers your having issues with.
            Benjamin Marte
            Interactive Media Developer
            Follow Me on Twitter | Visit my site | Learn MODX
            • 36644
            • 22 Posts
            Quote from: BobRay at Jan 27, 2013, 07:08 PM
            MODX doesn't do anything with your HTML and CSS code except send it to the browser. If there's a problem, it's likely something in your HTML and/or CSS code that is not completely cross-browser compatible. Have you validated your code here: http://validator.w3.org/? That would be the first step.

            Hi Bob, Thank you for this information.
              • 36644
              • 22 Posts
              Quote from: sottwell at Jan 27, 2013, 11:35 PM
              If something works in one browser but not in others that means a Javascript or HTML error. Firefox is very forgiving; it will more-or-less render a page even if you have some bad HTML. If you do a "view source" in the latest versions of Firefox, it shows things in red to let you know there's something wrong. Some false positives, but still a quick way to generally validate your HTML.

              Thank you very much.

              Henk-Jan
                • 36644
                • 22 Posts
                Quote from: benmarte at Jan 28, 2013, 07:49 AM
                Got a link and a better description of what exactly is the problem your experiencing? Browsers have different rendering engines and both Safari and Chrome use Webkit which seems to be the browsers your having issues with.

                Hi Ben,
                Our technical person for the websites did change something so the preview in Chrome seems oke but safari still is a mess. After refreshing the browser everytime something else is missing. (pictures missing, design changed)
                (website: www.etalageduet.nl).

                We are checking now all the suggestions above.

                Thanks, Henk-Jan
                  • 28042 ☆ A M B ☆
                  • 24,524 Posts
                  Definitely check your source and run it through the W3C validator.

                  <!DOCTYPE html>
                  <html lang="en">
                  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
                  <html>
                  <head>
                  <title>Duet etaleren & styling bureau | Duet is een jonge onderneming met verstand van etaleren</title>
                    Studying MODX in the desert - http://sottwell.com
                    Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                    Join the Slack Community - http://modx.org
                    • 27708 MODX Staff
                    • 2,502 Posts
                    Well that will break stuff. Should it be rendered as HTML5 or XHTML 1.0 Transitional (which should never ever be used—evar. IMO). Two opening html tags.
                      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
                      • 6955 ☆ A M B ☆
                      • 147 Posts
                      Yup - I always use the W3 Validator - it is very easy to overlook something at times. Nice site btw!
                        Billy Koch
                        Follow me on Twitter: @DefKoch
                        Skype: billyk0ch