Hi @johnmichaelpacholli,
I see there is a confusion, let me clarify it for you. You initially shared that you’re encountering an issue, showing a 404 not found error on https://tooraktimes.com.au/shop/?jb-disable-modules=all. Given that we’re talking about Jetpack Boost, I assume you were trying to regenerate Critical CSS with Boost and that was where you saw this issue. To explain, that parameter ?jb-disable-modules=all
is added by Boost to bypass its optimization features temporarily, allowing for an accurate generation of Critical CSS based on the page’s content as seen without any enhancements. It’s part of the process taken by Jetpack Boost to regenerate Critical CSS on your site.
Now, if you check that URL without the parameter, https://tooraktimes.com.au/shop/, you will see the same error, 404 Not Found
. This indicates that the page really does not exist or is not accessible, which is why both URLs are showing a 404 error. Since you use a caching system on your site, I would recommend clearing the cache first. This action ensures that no stale data is causing this issue. After clearing the cache, please allow Jetpack Boost to attempt regenerating the Critical CSS again.
Would you like to give this a try?
I disabled boost because I installed it incorrectly and broke my sites
As you might be aware, Jetpack Boost is equipped with a range of features aimed at improving your site’s load speed. However, these features can sometimes interact in unexpected ways with certain themes or plugins, potentially leading to issues such as incorrect display or layout disruptions.
For example, if your theme relies heavily on JavaScript and you have enabled the “Concatenate JS” feature, this could affect how scripts are managed and executed, potentially disrupting your site’s functionality. If you encounter such issues, you have the option to exclude specific JavaScript files from concatenation to prevent these problems.
I’d be more than happy to help. Would you like to give Boost a second try?