Jetpack update damaged our CSS
-
Hello,
Today I did an update on our jetpack plugin and we immediately received an email from WordPress notifying us that wordpress caught an error with our jetpack plugin.
We noticed that the heading images on our site are no longer showing up. When you go to bellharbourdental.com – each of the heading images on each page flash for approximately 1 second while loading and then they go blank.
We contacted our host and they notified us that it looks like the CSS was damaged due to Jetpack update.
Does anyone know how we can remedy this issue?
Thank you!
Derrick
The page I need help with: [log in to see the link]
-
Hi @bellharbourdental –
We noticed that the heading images on our site are no longer showing up. When you go to bellharbourdental.com – each of the heading images on each page flash for approximately 1 second while loading and then they go blank.
I see this happening. It looks like the header images are having a class applied dynamically that is hiding them by setting the opacity to 0. You can see that in this screenshot:
It looks like the CSS rule is in a cached file created by your caching plugin. You can try resetting the cache to see if that fixes the issue.
That said, it doesn’t seem that this CSS would be generated by Jetpack as it doesn’t correspond with the functionality in Jetpack. To be sure, please test with only Jetpack activated.
The Health Check plugin’s “Troubleshooting Mode” is a good way to do this. It allows you to make changes to your site without them reflecting on the frontend. You can download that plugin here:
https://wordpress.org/plugins/health-check/
Once you’ve installed and activated the plugin, you can go to Tools → Site Health:
* Select the Troubleshooting tab and then click Enable Troubleshooting to automatically disable all plugins and add a new Troubleshooting Menu item in the toolbar at the top of the wp-admin dashboard.
* From here, you can enable and disable plugins and change the theme for your site, but without affecting normal visitors to your site.Within Health Check, please disable all plugins other than Jetpack and test again. If it works as expected, you know that the issue is with one of your plugins. Please enable your plugins one at a time, testing after each one, until you encounter the issue again. Once you do, you will know which plugin is causing the issue. At that point, you can either leave it disabled or reach out to the developers for a fix.`
Today I did an update on our jetpack plugin and we immediately received an email from WordPress notifying us that wordpress caught an error with our jetpack plugin.
Could you share the error message that you received? That would help us to figure out what is happening here. At present, it seems the Jetpack plugin is working correctly.
Hi @lastsplash thank you so much for your helpful response.
I went ahead and downloaded the Health Check plugin, entered troubleshooting mode and disabled all of the plugins. Before even enabling any of the plugins. I noticed that, after making sure the correct theme was chosen, the site had a “fatal error” showing which can be seen below.
file:///C:/Users/Rhonda/Desktop/website%20plugins%20disabled%20step%201%20fatal%20error.png
Then, it wasn’t until I enabled the “Advanced Custom Fields Pro” plugin that the site looked nearly back to normal again. Except! that the issue with the blank background picture was already happening.
Using Health Check, I wasn’t able to determine if or which plugin is affecting the background picture.
Here is the message that we received from WordPress after updating our site notifying us that an error was caught within Jetpack:
Howdy! Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email. In this case, WordPress caught an error with one of your plugins, Jetpack. First, visit your website (http://email.bellharbourdental.com/c/eJxtjTsOwyAQBU9jymh3WWMoKNLkHnxlIgIW Jjl_nD7Sq0ajecmiUmjUyppEtBsgaSOKJSACLRE3YMabMeAkacYccjbKLww-1bq74ft7xNSmq7 fQX2K3iYNiv0LQJjr2oGFLmLXkNRpnKItq9zmPc5H3hR7X_oYuLoZ9upbm9XWkUXpprX_cLL2d P-ML-gw5Dw) and check for any visible issues. Next, visit the page where the error was caught (http://email.bellharbourdental.com/c/eJxtjTsOwyAQBU9jymh3WWMoKNLkHnxlIgIW Jjl_nD7Sq0ajecmiUmjUyppEtBsgaSOKJSACLRE3YMabMeAkacYccjbKLww-1bq74ft7xNSmq7 fQX2K3iYNiv0LQJjr2oGFLmLXkNRpnKItq9zmPc5H3hR7X_oYuLoZ9upbm9XWkUXpprX_cLL2d P-ML-gw5Dwwp-admin/update.php?action=update-selected&plugins=advanced-cust om-fields-pro%2Facf.php%2Cakismet%2Fakismet.php%2Cautoptimize%2Fautoptimiz e.php%2Cclassic-editor%2Fclassic-editor.php%2Cjquery-collapse-o-matic%2Fco llapse-o-matic.php%2Ccontact-form-7%2Fwp-contact-form-7.php%2Cflamingo%2Ff lamingo.php%2Cgoogle-analytics-dashboard-for-wp%2Fgadwp.php%2Cwidget-googl e-reviews%2Fgrw.php%2Cgoogle-sitemap-generator%2Fsitemap.php%2Cinsert-head ers-and-footers%2Fihaf.php%2Cbetter-wp-security%2Fbetter-wp-security.php%2 Cjetpack%2Fjetpack.php%2Cmailgun%2Fmailgun.php%2Cninja-forms%2Fninja-forms .php%2Cpixelyoursite%2Ffacebook-pixel-master.php%2Cplugin-organizer%2Fplug in-organizer.php%2Cpure-chat%2Fpurechat.php%2Cregenerate-thumbnails-advanc ed%2Fregenerate-thumbnails-advanced.php%2Cshortpixel-image-optimiser%2Fwp- shortpixel.php%2Csimple-301-redirects%2Fwp-simple-301-redirects.php%2Cstri ng-locator%2Fstring-locator.php%2Cthe-post-grid%2Fthe-post-grid.php%2Cw3-t otal-cache%2Fw3-total-cache.php%2Cwp-fastest-cache%2FwpFastestCache.php%2C wp-file-manager%2Ffile_folder_manager.php%2Cwp-mail-smtp%2Fwp_mail_smtp.ph p%2Cwp-migrate-db%2Fwp-migrate-db.php%2Cwordpress-seo%2Fwp-seo.php&_wpnonc e=8d7cc9ed33) and check for any visible issues. Please contact your host for assistance with investigating this issue further.Unfortunately we can’t see the image you shared as that is a path to a local image file on your computer. If you need to share a screenshot, here are a few options:
* https://snipboard.io
* http://skitch.com/
* http://getcloudapp.com/
* http://awesomescreenshot.com/I’m not seeing an issue with your background images currently, but I also see that Jetpack does not have a user connection. Could you try connecting Jetpack via Jetpack > Dashboard, and let us know if you still have trouble?
Hi there,
It has been more than one week since we have heard from you, so I’m marking this topic as resolved.
But if you have any further questions or need some more help, you’re welcome to reply here or open another thread.
The topic ‘Jetpack update damaged our CSS’ is closed to new replies.