statyanenko
Forum Replies Created
-
Thank you for confirming, that’s very helpful.
Hi @mochilaalparaiso ,
Thank you for reporting this issue. We are already aware of a problem related to the WP-Optimize cache feature and Elementor and we are currently working on a fix. The fix will be included in one of the upcoming releases.
Could you please confirm whether the WP-Optimize cache was enabled when you encountered this issue? We just want to verify that it is the same problem.
Thank you.
The issue has been fixed, and the fix will be included in an upcoming release.
https://wordpress.org/support/topic/wp-remote-blogvault-compatibility-issue-2/
Hi @bsklenarbhm,
Thank you for checking this and for your response!Hi @bsklenarbhm ,
I’ve done some research and the fix will be included in one of the upcoming releases. In the meantime, could you please try editing the file below and adding the following code?
File:
/wp-optimize/includes/class-wpo-page-optimizer.phpAdd this line inside the
should_initialise()function:private function should_initialise() {
if (!function_exists('wp_get_current_user')) return false;
...Please let me know if this resolves the issue.
Thank you.
@kingofrocknroll Thank you for your research. I’ll check for possible compatibility issues with the WPML plugin and get back to you later.
@kingofrocknroll Try to add debug into run() method in the /includes/class-wp-optimize-preloader.php
@kingofrocknroll That’s very strange. It seems like preloading isn’t even starting, perhaps it’s failing while collecting URLs from the sitemap. There should be at least a “N urls found.” message when preloading starts, but there’s nothing. Do you see any other errors in the debug.log?
Do you see any other lines related to preloading? Did you click preload button?
Best regards
Hello @benjaminb391,
Looks like your site pages are being cached, either by a browser cache set on the server side or by a caching plugin.
If it’s a plugin, you can just clear (purge) the cache from its settings.
If the caching is set up on the server, clearing the cache might help too. To make sure the browser always checks for updates, you can also add this to your
.htaccessfile (if you’re using Apache):<IfModule mod_headers.c>
<FilesMatch "\.(php|html)$">
Header set Cache-Control "max-age=0, must-revalidate"
</FilesMatch>
</IfModule>This tells the browser to recheck with the server before showing a cached version of the page.
Hello,
Can you try disabling Minify > Process JavaScript files and check if the errors still persist?
Hello,
In the Preload tab, you can find the ‘Activate scheduled cache preloading’ option. When this option is enabled, the cache will be preloaded automatically in the selected time period.
Please try disabling the “Automatically preload content after it is purged” option (Cache > Page Cache > Purge the Cache section) and see if the issue still occurs.
If that helps, you can set up scheduled preloading instead of immediate preloading (Cache > Preload tab).The issue has been fixed by our team, and the fix will be included in the next release.
