Venkat Raj
Forum Replies Created
-
@dmvisuals As per the debug log, it says an
objectis given instead ofarraytoarray_key_existsfunctions. The given$headersis the return value ofget_stylesheet_headersfunction.
In3.2.13it is directly returned . As you can see here.
https://plugins.trac.wordpress.org/browser/wp-optimize/tags/3.2.13/wp-optimize.php#L1648
However, in3.2.14the return value was made sure an array which you can see here.
https://plugins.trac.wordpress.org/browser/wp-optimize/tags/3.2.14/wp-optimize.php#L1648
So, I’m not sure how the issue persist. May be the update is incomplete?Hi @fkoomek
You can use this hookwpo_cache_flushto do that.@edviser Thanks for the details. I’ll try to reproduce the issue and update you.
@dmvisuals As per your debug log, it says you are using
3.2.13Aktuelles Plugin: WP-Optimize - Clean, Compress, Cache (Version 3.2.13)@andreas-2013 Please add following line in your
wp-config.phpfiledefine('WP_OPTIMIZE_SET_TIME_LIMIT', 300);This will result in 5 minute preload chunks
@jidwictut9 Found the issue in your
.htaccessfile and replied in email@vladimirvuch I have tried to reproduce the issue with no luck.
I have tested with setting
serve cached pages to logged in usersboth turned ON/OFF.
https://prnt.sc/8KzWPfJV9jVw
I used Elementor Pro and Hello Elementor theme@jidwictut9 Could you please share you
.htaccessfile? You can send it to support.wpo@updraftplus.com
I’ll test and let you know what causes the issue@andreas-2013 When you reduce the time limit, the usage spike will be for short periods rather than long. One possible explanation for high memory usage is that if your site uses lots of different set of scripts/styles in each pages, then minify assets will be created for those sets separately.
Could you please deactivate/activate the WP-Optimize and see if that fixes issue?
That said, it seems system (disk I/O, network communication, etc) too take lot of resource apart from WP-Optimize’s PHP process?@dmvisuals There was a compatibility issue with WordPress 6.2 Which is fixed in version 3.2.14. You are still using 3.2.13, Please update
@andreas-2013 All
preloadis doing that it visit’s your site programmatically. So, it will take the same amount of resources if you visit the pages manually.
The preload doesn’t run as a single task. Once the PHP script reaches the time limit (max_execution_time), the remaining URLs are scheduled to preload later. We do see the possibility and increase the time limit to 30 minutes. What you have done is that increase the interval between batched preload tasks.
If you don’t want to run a single preload task for 30 minutes, then you can reduce it by defining a constantWP_OPTIMIZE_SET_TIME_LIMITto your desired seconds.@edviser Could you please tell me the versions of
WordPress
PHP
WP-Optimize?
Thanks!@vladimirvuch What theme and plugin you are using for that functionality?
You can send it here: support.wpo@updraftplus.com
@fkoomek You could use
Schedule preloaderoption and setschedule typeassame as cache lifespan
This runs preload whenever the cache is purged.