Jump to content

Archived

This topic is now archived and is closed to further replies.

richardjacruz

Google Cached Version Broken

Recommended Posts

richardjacruz

I noticed that the cached version of the website from a Google SERP has broken CSS:

http://webcache.googleusercontent.com/search?q=cache%3A1uyPM2gXGG0J%3Astevensoncrane.com%2F+&cd=16&hl=en&ct=clnk&gl=us

Any idea why? The site looks fine elsewhere.

Also, when using the Web Developer Toolbar in Mozilla Firefox, there are a BUNCH of warnings regarding CSS. I'm wondering that's the problem with the Google cache.

In a prior post, I had experienced similar "breaking" of the CSS, but that was due to some errors in DNS. I thought we resolved all of that, so this perplexes me.

Thanks,

Rich

Share this post


Link to post
Share on other sites
Simon

What css is broken? The page looks ok to me?

Share this post


Link to post
Share on other sites
richardjacruz

Here are some screenshots:

Share this post


Link to post
Share on other sites
Simon

You need to attach them to a post, or use a host like imgur 

Share this post


Link to post
Share on other sites
richardjacruz

Sorry about that. Here are those screenshots. These are from Firefox, but I see the same thing elsewhere.

Again, this is ONLY the cached version in Google: http://webcache.googleusercontent.com/search?q=cache:1uyPM2gXGG0J:stevensoncrane.com/+&cd=3&hl=en&ct=clnk&gl=us

But, I'm wondering if this might have any negative affect on our SEO.

 

I'm also on the Platform 5 user group. I'm wondering if I should convert all of my DMS sites to this new system. Thoughts? I'm usually a late adopter only because you guys usually shake the "bugs" out after some of the community feedback.

GoogleCacheProblem3.jpg

GoogleCacheProblem2.jpg

GoogleCacheProblem1.jpg

Share this post


Link to post
Share on other sites
richardjacruz

Also, the Developer Toolbar has given me these two warnings on the live site:

 

20160212_104452.jpg

20160212_104504.jpg

Share this post


Link to post
Share on other sites
Simon

Google also caches the css version if you view the source of the page you will see that the css files end like sections-75748.css obviously you have saved and regenerated the css since then so this file is now a 404.

If you really need the css to work on google cache (?) then go into the advanced options and enable the alternative css naming option.

Share this post


Link to post
Share on other sites
richardjacruz

Great. I just did that. We'll see how things go. FYI, I noticed that the same "break" in the CSS occurs in the Wayback Machine's cache as well.

Share this post


Link to post
Share on other sites
Simon

It'll be the same issue.

Share this post


Link to post
Share on other sites

  • Similar Content

    • Michael Kummer
      By Michael Kummer+
      Hi guys!
      I have noticed that my primary sidebar becomes intermittently invisible when browsing through various blog articles on michaelkummer.com/blog.
      See:
      https://www.dropbox.com/s/z646sgoa3mfjl1j/Screenshot 2018-07-12 15.57.46.jpg?dl=0 and https://www.dropbox.com/s/vdledzzgginvwgv/Screenshot 2018-07-12 15.57.57.jpg?dl=0
      Upon refresh, the sidebar appears. I have been using the following CSS code to hide the sidebar on mobile without any issues. 
      @media only screen and (max-width: 993px) {
      /* hide sidebars */
           .plsb {
              display: none !important;
          }
      }
      I tried to add the following CSS to force the sidebar to show on screens that are wider than 994 pixels but to no avail. Any clue what could be causing this issue?
    • Michael Kummer
      By Michael Kummer+
      Hi guys!
      I am using the LESS/CSS Pagelines extension and tried to add the following code to make use of FontAwesome:
      a.c2a:before {
          content: "\f07a\00a0";
          font-family: "Font Awesome 5 Pro";
          Font-weight: 900;
          font-style: normal;
          font-weight: normal;
          text-decoration: inherit;
          padding-left: 4px;
      }
       
      The issue is that as soon as I have the CSS via the Custom Styling text box, Pagelines (or the extension) strips out the backslashes (\). As a result, I had to abandon the CSS/LESS extension and instead add all my CSS code to a separate .css file.
      Is there a fix or workaround for this?
      Thanks
      Michael
    • glyph.marketing
      By glyph.marketing+
      Hello, I am having a problem similar to that experienced by Michael Kummer here. We have pages that show this automatic scrolling issue (examples here and here) and it is sufficiently annoying that we have seen customers bounce while trying to convert. Strangely, it only happens at specific resolutions, so it can be difficult to reproduce. In general we can only consistently reproduce it on a 4k resolution with a browser width between 1517 and 1536px. 
      Thanks to Michael Kummer's help we were able to set the overflow-anchor property to none in the entire body, which fixed the issue as far as we can tell, but also obviously disabled scroll anchoring for the whole site. I tried applying it to the specific element that looked like it was being reloaded, which was the PL Meganav extension, but that was unsuccessful. 
      Can anyone help us figure out which element or ID we can apply this property to, so that we can fix the scrolling issue but not disable scroll anchoring for the entire site?
      Thank you - 
      Glyph Language Services
    • chamois_blanc
      By chamois_blanc+
      Hello,
      Shouldn't the image PL5 component be using the srcset/picture css directives to pick the correct size for an image? or it does already and I don't know how to use it? Thank you for any advice or enlightenment.
    • Dan Haddock
      By Dan Haddock
      Plugins Active and installed: 
      Akismet Anti-Spam
      Coming Soon Page & Maintenance Mode by SeedProd
      Contact Form 7
      Cookie Law Info
      DMS Professional Tools  
      Enhanced Media Library  
      Flamingo
      Google Analytics for WordPress by MonsterInsights
      Google XML Sitemap
      Jetpack by WordPress.com
      Legull 
      Loginizer   
      MailChimp for WordPress
      PageLines Updater    
      Schema App Structured Data 
      Sucuri Security - Auditing, Malware Scanner and Hardening
      Uber reCaptcha    
      Yoast SEO
      Wordpress Version: 4.8.1
      Pagelines Version: 2.2.4
       
      Good Evening/Afternoon or Morning, 
      I am running into a problem with CSS styling not applying inside of most browsers (Safari, Firefox) when I am logged in to wordpress, and all browsers that I have tested when I am logged off and the site has been made public (Chrome, Firefox and Safari).
      As a result, I have managed to identify the probable cause. It looks as though these browsers are refusing to render my sites compiled CSS file due to it being a HTTP URL rather than HTTPS.
      I have attempted to change this URL to HTTPS in my browser, however it brings back an ERROR: File not found page - https://www.shortfilmblog.com/wp-content/uploads/pagelines/compiled-css-core-1505847507.css
      What would you suggest in this regard? Would this be resolvable from your end?
      Happy to provide any further details required.
×