davidlonjonxwp

@asafm7 This is great to hear that it is now working. It might have been indeed a caching issue that can sometimes cause unexpected behaviour.

Do not hesitate to reach out if you have any other questions or experiencing issues. The feedback is very valuable to us in order to improve Jetpack Boost ??

Hi @frankdoherty,

Thank you for your interest in Jetpack Boost and sorry to hear that you are having some trouble with it.

Could you please let us know a bit more about your site setup such as the theme you are using and the activated plugins? Also, could you let us know which of the modules you had enabled on the Jetpack Boost plugin when experiencing the issue you’ve described? Finally, could you also let us know the URL where the issue occurred as well if possible a screenshot before and after the issue?

You can create and share screenshots using something like Snipboard or Imgur and post the link here.

I am looking forward to your reply!

Best
— David
Jetpack Boost Developer`

• This reply was modified 3 years, 2 months ago by davidlonjonxwp.

Hi @asafm7,

Sorry for the delay in getting back to you. I got diverted to other tasks and I did not have the opportunity to look more into this.

I guess from here I will need more information such as the theme you are using and the plugins you are having activated while using Boost. Could you also confirm the version of the Jetpack Boost you are using? With this information, I may be able to try replicating your setup locally and investigate further.

Finally, you could try purging any caches that you might have (WordPress cache, Cloudflare cache, plugin cache). Also if you have other Optimization plugins (such as WP Super Cache, W3 Total Cache, WP-Optimize), they can also conflict, so try disabling any you have running to see if that allows you to generate Jetpack Boost’s Critical CSS correctly.

Best,
David
Jetpack Boost Developer

Hi @asafm7,

Currently, Critical CSS does not refresh automatically from time to time. At the moment, Critical CSS is generated by a user manual action on the Jetpack Boost setting page such as when activating the module or clicking on the regenerate button. It will also prompt the user to regenerate the Critical CSS after a theme change. The generation process is locally on the Jetpack Boost settings page.

We have been exploring generating Critical CSS automatically with an external process that would allow Critical CSS to be regenerated automatically from time to time without needing user input. This is something we might be able to release in a future version. We don’t have a time estimate at this point, but it’s on our radar for sure. Please Keep an eye on future updates of the plugin ??

Best,
David
Jetpack Boost Developer

Hi @asafm7,

Thank you for using Jetpack Boost.

I had a look again today at your site and it seems that the jetpack-boost-critical-css element now contains the Critical CSS. At least a lot more than when you reported the error. Here is a screenshot I took a few minutes ago: https://cloudup.com/c-hqV0FXSRe

I am not sure what could have happened the first time. Have you tried to generate Critical CSS again? Did you change anything in your site configuration such as activated/deactivated other plugins? In any case, it seems to be working now but more info is welcome so we could try to identify how it failed in the first place.

Best,
David
Jetpack Boost Developer

hi @artsitegallery,

Thank you for your interest in Jetpack Boost and sorry to hear that you are having some trouble with it.

The Jetpack Boost plugin uses an automatic internal mechanism in order to verify the page for the creation of Critical CSS. When it fails to find the proper identification on the page it will fail and display the type of error reported.

It seems the issue may be caused by a plugin creating some custom post type(s) that Jetpack Boost may not be compatible with.

In order for us to investigate further, we would need more details from your site setup such as the URL or your site, the theme you are using and the activated plugins on your site.

Best,
David
Jetpack Boost Developer

• This reply was modified 3 years, 2 months ago by davidlonjonxwp.

Hi @nbrplaza,

Sorry I’ll have to contradict myself one more time from my previous message. It seems you are indeed using Jetpack Related Posts. I was getting confused because of the Yet Another Related Posts Plugin that you also seems to use.

I also found from your site that you are using thE SG Window theme. So I set up a local environment with that theme, enabling Jetpack Related Posts modules and also activating and enabling multiple combinations of the Jetpack Boost plugin and could not replicate your problem. See my attempt in this video: https://cloudup.com/cZEUWqthYog

So in order to try finding out the root of the problem I would still need more information from your side on your setup as mentioned before.

Best,
David
Jetpack Boost Developer

Hi @nbrplaza,

Sorry for the previous message, I made the wrong assumption that you were using the Jetpack Related Post block to power the related post feature on your site. But it seems you might use a different plugin (Yet Another Related Posts Plugin) to display related posts on your site?

In any case, for us to investigate further we will need more information from you. As mentioned before, it would be useful to confirm which theme you are using, which plugin you have activated, how you have set up the related posts feature and which modules of Jetpack Boost were activated when you experienced the issue.

Best,
David
Jetpack Boost Developer

Hi @profosamaadmin,

Thank you for your interest in Jetpack Boost and sorry to hear that you are having some trouble with it.

First, may I confirm you are running the latest version (v1.2.0) of the Jetpack Boost plugin. This latest version should provide a bit more detailed information regarding the HTTP 500 error such as on which page of your site it is occurring.

Looking at your site, it seems there are already some technical issues with it as shown on this screenshot: https://cloudup.com/cawHpl2USRa which seems to break the design of your site. This might be one of the reasons you’ve encountered an issue while generating Critical CSS with Jetpack Boost.

I would recommend first that you are resolving these issues with your site before trying out Jetpack Boost again. In order to fix these issues, you might need to contact your host provider.

Please let me know how it is progressing.

Best
— David
Jetpack Boost Developer

Hi @k_b

Thank you for your interest in Jetpack Boost and sorry to hear that you are having some trouble with it.

Would you please let us know a little bit more about your current setup such as which theme you are using as well as which plugins do you have activated on your site? Please could you also let us know if you are using external services for improving the performance of your site such as Cloudflare as these types of services can interfere with the creation of the Critical CSS from Jetpack Boost?

If you want to go ahead with the troubleshooting meanwhile, you could try purging any caches that you might have (WordPress cache, Cloudflare cache, etc) and trying to log into your site in an incognito window (to prevent browser cache from interfering) and try it out. Also if you have other Optimization plugins (such as WP Super Cache, W3 Total Cache, WP-Optimize), they can also conflict, so try disabling any you have running to see if that allows you to generate Jetpack Boost’s Critical CSS.

If the above steps don’t change anything, can you take a screenshot of the DevTools Network tab and the Browser Console? Please make sure also to take a screenshot when you’re on the Jetpack Boost dashboard.

You can create and share screenshots using something like Snipboard or Imgur and post the link here.`

I am looking forward to your reply!

Best
— David
Jetpack Boost Developer

Hi @agenciafun,

Thank you for your interest in Jetpack Boost and sorry to hear that you are having some trouble with it.

First, may I confirm you are running the latest version (v1.2.0) of the Jetpack Boost plugin. This latest version should provide a bit more detailed information regarding the HTTP 500 error such as on which page of your site it is occurring.

In order for Jetpack Boost to generate Critical CSS, it loads pre-selected posts and pages of your site in a hidden container. An HTTP 500 error means that while trying to load one of your site pages, the server returned an error. These types of errors can sometimes be temporary and if you try again generating the Critical CSS on your site using Jetpack Boost, it might work the second time around.

If it does not, making sure to run the latest version (v1.2.0) of Jetpack Boost, you could try purging any caches that you might have (WordPress cache, Cloudflare cache, etc) and trying to log into your site in an incognito window (to prevent browser cache from interfering) and try it out again.

If the above steps don’t change anything, can you take a screenshot of the DevTools Network tab and the Browser Console? Please make sure also to take a screenshot when you’re on the Jetpack Boost dashboard.

You can create and share screenshots using something like Snipboard or Imgur and post the link here.`

I am looking forward to your reply!

Best
— David
Jetpack Boost Developer

• This reply was modified 3 years, 2 months ago by davidlonjonxwp.
• This reply was modified 3 years, 2 months ago by davidlonjonxwp.

Hi @nbrplaza,

Thank you for trying out Jetpack Boost and sorry to hear you are encountering some issues with it.

I tried to replicate the problem on a test site using the Jetpack Related Post block and Jetpack Boost enabled (with the “Optimize CSS Loading”, “Defer Non-Essential Javascript” and “Lazy Image Loading” modules enabled) but I was unable to observe the same issue.

Could you please let us know a little bit more about your setup such as the theme you are using, how you’ve set up Jetpack Related Posts, the modules enabled on Jetpack Boost and also the other plugins you have installed? This information will help us in trying to investigate the issue further.

Best,
David

• This reply was modified 3 years, 2 months ago by davidlonjonxwp.

Hi @ktaylor310,

Just to let you know that we have released version 1.1.1 of the plugin which fixes the plugin deletion issue.

Thank you for your patience.

Best,
David

Hi @silverfox93,

Just to let you know that we have released version 1.1.1 of the plugin which fixes the plugin deletion issues.

Thank you for your patience.

Best,
David

Hi @ktaylor310 ,

We are sorry you have been experiencing an issue with the deletion of the plugin.
We have investigated further and have found the cause of the issue. During deletion, the plugin is trying to clear up a few things, but one of them fail due to leftover legacy code. This will be fixed in the during the next release.

In the meantime, you can either:
1. Delete the plugin manually. The process of doing it might depends on your hosting. You might be able to do it via FTP, or via SSH access.
2. Delete the plugin via the Dashboard by following the instructions in this video clip: https://cloudup.com/cLf_E6ZSS8F

Again sorry for the trouble. I hope this is an acceptable solution for now until the next release of the plugin. Please do not hesitate to get in touch if you have more questions or have any issues.

Best,
David