I just wanted to post this somewhere, maybe this helps somebody in the future …
I’m using W3TC together with “WordPress Newsletter Plugin” from Tribulant. I have database cache enabled for not-logged-in users.
I had the problem that when a user registered to my page and sign’s up for the newsletter he get’s an invalid authkey per email and so can’t process the double-opt-in.
The problem is that the process of generating an authkey is run multiple times and the function checks if there is already an authkey in the database. As this query is cached by W3TC it always returns the same result. So the function always incorrectly generates a new authkey, overriding the existing and so making it invalid.
This problem can be solved through addding “wp_wpmlsubscriberslists” to the ignored query stems in the database cache settings.
🙁 We purchased the plugin a few weeks ago for a site I’m helping with. When I found it wouldn’t allow buyers to purchase without logging in unless I bought another extension, I decided to ask for a refund. The reason for the extension was explained to me and it seemed reasonable, dealing with wordpress requiring creating a user account. I decided to stay with it as well as buy an other extension to help make the site easier to secure with our SSL certificate.
Since then I’ve run into a number of issues and the team there has been very responsive. However, I keep running into different small issues with different browsers and can’t continue to put time into a project that needs to be completed right away.
I asked for a refund again. Bad news I was told, I’ve gone past the short 7 day refund time. Beware.
Viewing 1 replies (of 1 total)
The topic ‘W3TC Database Cache & Tribulant WordPress Newsletter Plugin [SOLVED]’ is closed to new replies.