István

Hi,

Yes, you can.

In the following file: \wp-content\plugins\qtranslate-x\qtranslate-frontend.php
on line 523 you find “function qtranxf_postsFilter($posts, &$query) {”
– remove the “&” from that line,
so it should look like this: function qtranxf_postsFilter($posts,$query) {

Hi again!

I upgraded to version 1.4.0.2, and the problem is still there, so Wp Super Cache cannot cache pages on which your Ajax Product Filters plugin is loading.

My temporary workaround is that I wrote a small plugin by which I disable Ajax Product Filters on pages which do not need it, and changed a little bit the code of WP super cache plugin to this.

File: wp-cache-phase2.php
Line 1798
elseif ( $_SERVER[“REQUEST_METHOD”] == ‘POST’ || !empty( $_POST ) || get_option( ‘gzipcompression’ ) ) {
//wp_cache_debug( ‘Not caching POST request.’, 5 );
$cache_this_page = true;

Obviously this should be a temporary solution.

I’d like to buy the Professional version, if that is working well with wp super cache.

Did you test your plugin with wp super cache?

I hope that in the future this POST related issue will be fixed, because the older version of your plugin had no problem working with wp super cache.

No downside, just ignore the message – and don’t forget to update .htacess when you do an update on WP Super Cache.

Wp super cache settings -> Preload Tab, and there you have a select options, and there you can disable emails notifications.

Try advanced mode with mode_rewrite.

Try to disable plugins, probably you have a plugin which is in conflict with wp super cache.

Errors from wp-super-cache when I enable 1.4.0.1

Not caching POST request.
11:02:36 1122 /URL-TO_PAGE/ wp_cache_maybe_dynamic: returned $buffer

So it seems to me, that 1.4.0.1 is making POST request instead of GET, and that prevents WP-SUper cache from creating supercache files.

Making those changes on version 1.3.3.2 – does it resolve the security issue?
I cannot update to the latest version (1.4.0.1), beacause it breaks wp super ache.
I think the new version does POST request instead of GET, even if it is set to do GET instead of post, or maybe Output Buffering is in conflict with wp super cache, I don’t know. Anyway, 1.3.3.2 is working well with wp super cache, but 1.4.0.1 does not work.

Hi @razyrx, and thanks for the great plugin.

The newest version (1.3.4.2) is in conflict with wp super cahe. I had to downgrade the plugin. Maybe wp super cache is interpreting something wrong, but I cannot know for sure, and cant find the problem. The version before 1.3.4.2 is working well with wp super cache.

Maybe I will announce this problem to the wp-s-cache developers too. Let’s see, if noone else is having this problem, than maybe my case is exeptional – but I don’t think so.

Thank you