New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3rd Party Plugin Compatibility: Contact Form 7 #500
Comments
I tested this a while back... ProblemsContact Form 7 lacks a cache-friendly design. The author of this plugin has not implemented Short-Term WorkaroundAdd Possible Long-Term SolutionThe Contact Form 7 developer might want to consider using See also: wpsharks/comet-cache-kb#47 |
Bug Confirmed when
|
@renzms Thank you. So to reiterate, here's what needs to happen to improve compatibility with Contact Form 7 at this point:
I'm not sure if this is even going to be possible. I believe Contact Form 7 just provides a shortcode that you place on a Post/Page to show the form. If that's the case, then there might not be any way to know which Posts/Pages contain a Contact Form 7 shortcode without somehow going through all of the page content in WordPress looking for the shortcode (not an option given the high workload of such a task). A better workaround would be for the site owner to use the Comet Cache URI Exclusion patterns to exclude any pages that contain Contact Form 7 shortcodes from be cached, or if they prefer to cache the form for logged-in users, they should remember to manually clear the cache for that page after making any changes to the form on that page. I'm going to close this for now, as I'm not seeing anything actionable that we can do here. |
See: https://wordpress.org/plugins/contact-form-7/
This plugin has over 1 million active installs and is often used in conjunction with Really Simple CAPTCHA (see #499).
There have been some reports of issues between ZenCache and Contact Form 7 and it would be nice if ZenCache worked seamlessly (or at least provided the necessary Dashboard messaging to ensure smooth operation).
Support threads referencing this issue
The text was updated successfully, but these errors were encountered: