1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

XF 1.2 Google Chrome

Discussion in 'Troubleshooting and Problems' started by Luís Ramalho, Dec 2, 2013.

  1. Luís Ramalho

    Luís Ramalho New Member

  2. Mike

    Mike XenForo Developer Staff Member

    The site displays properly for me in that version of Chrome.
  3. Luís Ramalho

    Luís Ramalho New Member

    Mike, I just opened the forum and still has the same problem (as it's been having since I installed XenForo). Please try again, or enter a forum such as http://www.fisiozone.com/forums/noticias.27/

    Also, sometimes it displays like the following (like it did for me just now after a few refreshes)

    FisioZone.com - Google Chrome_007.png
  4. Mike

    Mike XenForo Developer Staff Member

    From what I can see, your server is returning a 304 not modified response from the CSS when it shouldn't be (even when the browser is sending a header saying it doesn't have a cache). The result doesn't even appear to be served via PHP, based on the headers returned. I can only guess that you have some caching applied somewhere that is causing this.
  5. Luís Ramalho

    Luís Ramalho New Member

    I just checked with my hosting provider and they confirmed that there's no cache settings in the server, and I certainly didn't apply cache anywhere. Do you have any idea how I can fix this problem? I am lost here.

    Thank you very much!
  6. Mike

    Mike XenForo Developer Staff Member

    I just had a page load where the base tag and the JS URL for the base tag were inconsistent. This must have been from a manual edit as it's the same URL in both places.

    Otherwise, unfortunately I don't have any recommendations. If you look at the request in Chrome, you can see the server returning a 304 response and the headers don't indicate that XenForo is being executed (XF could return a 304 but there are specific headers it checks). There's definitely something above XenForo that is triggering this but I'm not sure what.
  7. Lawrence

    Lawrence Well-Known Member

    Hi, works for me in Chrome from Canada. Have you tried doing a MTR (let run for about 20 mins)? I had a similar problem a month ago, my site would load fine in Opera Next, but not in the other major browsers, turned out there were packet losses (from my home to my server, it didn't affect users from other locations).

    Just something you can try and eliminate.
  8. Luís Ramalho

    Luís Ramalho New Member

    Thank you both for the help.

    I think I've tracked the problem down to Google's DoubleClick for Publishers. It requires the following code to be added to the <head>

    <script type='text/javascript'>
    var googletag = googletag || {};
    googletag.cmd = googletag.cmd || [];
    (function() {
    var gads = document.createElement('script');
    gads.async = true;
    gads.type = 'text/javascript';
    var useSSL = 'https:' == document.location.protocol;
    gads.src = (useSSL ? 'https:' : 'http:') +
    var node = document.getElementsByTagName('script')[0];
    node.parentNode.insertBefore(gads, node);
    <script type='text/javascript'>
    googletag.cmd.push(function() {
    googletag.defineSlot('/25227634/FisioZone_Horizontal', [728, 90], 'div-gpt-ad-1387627222181-0').addService(googletag.pubads());
    I have noticed that when I remove it from the <head> the styles display correctly.

    Is there any way around this issue so I can keep DoubleClick for Publishers in my forum?

    Thank you so much.

Share This Page