Venkat Raj
Forum Replies Created
-
@francoc30 Could you please post the content of
*.jsonfile in thewp-content/cache/wpo-minify/xxxxx/assets/*.jsonto fix the 2nd warning you have mentioned?Also, the 1st warning seems impossible to happen, because just before the line
mkdirwe make sure the dir doesn’t exists. Perhaps you have trigger the preload multiple times?Hi @ittone,
The minified assets such as js/css can only be requested/fetched because the html page being requested has references to those assets.
Is
Static file headersoption in cache section on or off?
When it is on all the HTML response has headerCache-Control: private, must-revalidate. So, theoretically, no client should cache the HTML page (which contains reference to minified assets). When you turn of Minify option, new HTML response will be served which as no reference to the old minified assets. 404 errors can’t be happen in this scenario.If
static file headersis off, in that case there is nocache-control or expiresheaders in the HTML response, so client shouldn’t cache the result.
Again, this is theoretical.So, We need more information about the user agents (ex. google bot) and the HTTP protocol they use in order to further investigate and fix this. Thanks.
@ittone Are you using a CDN? If so, which one?
Upon deactivation, we do delete the minification files. It is because, we can’t distinguish between temporary and permanent deactivation. Besides, if plugin is deactivated it means that there is some significant change is going to happen on the site. In that case the already cached files become obsolete, so fresh caching is needed. That is the the reason for file deletion.
The 404 errors can only happen when a CDN has old cached files which in turn refer to old minified js/css files. In that case upon deactivation, you also need to purge the cache in CDN
@didierjm I can confirm that this is a bug.
We’ll fix this in the next release by updating our uninstall / deactivation process. Thanks for reporting the issue
@lucycrisps Based on log file, it seems your server setup denies creating a cache config file on
wp-contentfolder. It is essential for using cache feature. If you think file permissions are write, you could try disable/enable cache feature or deactivate/activate our pluginBasically, you shouldn’t have
Cache config file is not presenterror to use this feature.Hello @fortis1
I’m not sure how
robots.txtended up with this content. We don’t write any comments to that file except this lineDisallow: /wp-content/uploads/wpo-plugins-tables-list.jsonBesides when considering headers serving
robots.txtshould be greater than 255 bytes.To fix you need to manually edit the file and remove the unwanted content.
Turn off debugging mode
define('WP_DEBUG', false);If problem persist, You may even add
robots.txtto Dashboard => Cache => Advanced Settings => URLs to exclude from caching textbox.I tried to create this problem at my end without success. So, if you could write down the steps to reproduce the issue, we can dive deep and fix the root cause.
You could see what files are processed and merged in this file
wpo-minify-footer-b7d9f3b4.min.jsin Advanced tab and by clickingshow informationWhen you see js files related to Yoast SEO, you can exclude them to single out which script is causing issue.
Since you choose to
mergethe individual scripts, if one of the script hasSyntaxErrorthen it will result in the same for minified and merged script as well.Let me know your findings
We’ll look into this.
Could you please let me know which WPO version you are using and whether Nginx server is already configured to use gzip compression or not? ThanksHi @francoc30
We have fixed the issue and next release will solve the issue.
If you want to try it (before release), please submit a support ticket here
https://getwpo.com/ask-pre-sales-question/@sonisitez Don’t defer jQuery loading with WP Optimize
@sonisitez From your screenshot, I can conclude that you ad showing script depends on jQuery. Since you deferred loading jQuery, it will load asynchronously, but you ad script is loading before jQuery and trying to execute (yet not available) jQuery.
May you want to load jQuery normally
@sonisitez Do you see any errors in browser console? May be Ad script needs jQuery and is loaded before it?
@tonyrobertsacer At this moment, you can change the location in code
wp-content/plugins/wp-optimize/cache/class-wpo-page-cache.phparound line 28Or you can define a constant in
wp-config.phpdefine('WPO_CACHE_FILES_DIR', '/path/to/your/cache/location/');- This reply was modified 3 years, 9 months ago by Venkat Raj.
@petraschier @naturfreundeschweiz Premium version 3.2.8 has been released with a fix. Sorry for the trouble
@spcspectre Sorry to hear that. You should be using premium version. It has been fixed with new release 3.2.8
To all others: Free version 3.2.7 is NOT affected by this issue