cgclouds
Forum Replies Created
-
Thanks for the reply. I’ve been delving into the docs to understand all this. I now see and appreciate how much this plugin adds to the WordPress functionality, and, on the other hand, how far WordPress still is from being a complete content management tool for end users.
I’m sure though WordPress will keep on developing fast and incorporating more needed tools soon.
Thanks again for the great work.
I had the same problem with Contact Form 7 using the Contact Form to DB Extension. I was actually using the Contact Form to Database Extension with Fast Secure Contact Form, but still using Contact Form 7 for other site forms.
Contact Form to DB Extension interfered with Contact Form 7 and it left it hanging with the spinning arrow icon, and didn’t show the confirmation message.
Solution:
Edit the CF7DBPlugin.php in the Contact Form to DB Extension.
Comment out (add // to) the line:
add_action(‘wpcf7_before_send_mail’, array(&$this, ‘saveFormData’));Contact Form 7 will no longer hang (and of course, will no longer send info to the database).
Hope this helps someone. If this is not your particular case, then there’s a chance another plugin is interfering with Contact Form 7.
Thanks for the quick reply and also for the great plugin. I needed an immediate solution so I was forced to switch plugins, and am using DB Cache Reloaded.
Sincere apologies for not being able to help solve the problem, I can’t have the two cache plugins running simultaneously on the server.
If someone else going through this problem is reading this please try to help the author solve the issue.
Thanks.
Re-tested with wpsc 0.9.9.8 and wp 3.1. Same problem.
Same problem here. I updated to 0.9.9.9 and wp 3.1 and the code that uses the “dynamic-cached-content” tag, that worked previously with 0.9.9.8 and wp 3.0.x, is now returning blank pages with just wpsc’s timestamp on them.
Also, it does not allow me to delete these blank cached pages manually from the cache list (unless I delete the whole cache).
Note: something funny seems to happen with $wp_super_cache_late_init. After setting it to 1 and uploading the wp-cache-config.php file, it seems to reset it to 0 by itself after some time.
In any case, I re-tested it while the $wp_super_cache_late_init was set to 1 and it still returns the blank page with the timestamp, and does NOT return the phrase “Super Cache dynamic page detected but $wp_super_cache_late_init not set.”