agxtimo
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] [Plugin: Contact Form 7] 3.1, W3 Total cache, WP nonces@takayuki Miyoshi,
I’ve tested the dev version with default caching settings activated in w3 total cache (page, browser, object and database caching activated with default settings) and every submit is successfully posted.
I’ve tested this multiple times in different browsers, so I think this dev version is OK.
Forum: Plugins
In reply to: [Contact Form 7] [Plugin: Contact Form 7] 3.1, W3 Total cache, WP noncesPerfect! Thanks!
This would be really awesome. Thanks for the fast follow up.
We’ve been able to reproduce the problem jelleverspurten described by enabling the page cache in the W3 total cache plugin.
When trying to submit a form on a cached page, the user gets redirected to an empty form first, but after reloading and reposting the form the form gets submitted correctly. Offcourse this is not acceptable.
This is the first time we’ve encountered such a problem in combination with the W3 total cache plugin. After all, this plugin does not cache posted data, so there never should be any problem in the first place.
We generally use Contact Form 7 with our websites and never had any issue with it, just so you know.
Again, the GentBC website could really use some caching, so as long as this issue is not resolved, we can not enable caching on this website.
Could you please respond?
We at AGX are responsible for the maintenance of the GentBC website mentioned in the above comment from jelleverspurten.
As we just reviewed the plugin, we noticed that the plugin throws a javascript error on page load in all browsers on line 143 of the following script: /wp-content/plugins/wordpress-form-manager/js/userscripts.js
While this might not be a severe error, some people running this page in IE might disable javascript when presented with this error, so perhaps this is what went wrong in the first place?
For the sake of clarity, the site is using W3 total cache and the form pages are not cached while we run our tests.
Could you please respond to this issue?