Hello @archicoders
Thank you for reaching out and I am happy to assist you with this. Can you please share where exactly you added define( ‘W3TC_DYNAMIC_SECURITY’, ‘mysecurestring’); ?
All 500 errors should be logged so can you please check the WP_DEBUG log and see what may be causing the problem?
I’ve tried to replicate this on several instances, however, I am not able to replicate the problem.
Thanks!
Thanks @vmarko,
I checked /wp-content directory but there is no debug.log file in it. I also tried to add this define(‘WP_DEBUG’, true); in wp-config.php file but still no error showing aside from “HTTP ERROR 500”. Do I need to upgrade to Pro Version to use the Page Fragment Cache?
Hello @archicoders
Thank you for your feedback. No, you do not need the Pro version to use Page Fragment Cache. Please check more in our FAQ for more details about Page Fragment Caching.
Either the code is misplaced or something is causing the conflict, and this should be logged when 500 errors occur.
Again I was not able to replicate the problem.
Thanks!
Thanks @vmarko
I’ve retried adding the codes on wp-config, unfortunately, a 500 error still occurs. Is there another way to set up page fragment cache? We just want to exclude the search form on caching at the homepage.
Hi @vmarko,
Regarding my question last time, is there any other way to exempt search form from caching without using fragment cache?
Thanks!
Hello @archicoders
Sorry for the late reply.
Yes, you can fire the code using Ajax calls. This way this part of the page will bypass the cache.
Thanks!
