funkymonk145

CF7 version: 4.4
Wordpress version: 4.4.2

Having the same issue here, CF7 displays the message was sent successfully, but I am receiving neither the submission or the confirmation to the sender.

Interested to see what we all have in common as I am also experiencing this issue on a GoDaddy installation as JTwordpress is. Is everyone else using GoDaddy?

Intersting finding: On my local server, I reverted manually to CF7 version 4.3.1, tried a submission, which worked, then updated through the plugins screen to latest, tried a submission, and it still worked. Tried the same thing on the GoDaddy server but neither version worked.

CF7 version: 4.4
Wordpress version: 4.4.2

Having the same issue here, CF7 displays the message was sent successfully, but I am receiving neither the submission or the confirmation to the sender.

Interested to see what we all have in common as I am also experiencing this issue on a GoDaddy installation as JTwordpress is. Is everyone else using GoDaddy?

Intersting finding: On my local server, I reverted manually to CF7 version 4.3.1, tried a submission, which worked, then updated through the plugins screen to latest, tried a submission, and it still worked. Tried the same thing on the GoDaddy server but neither version worked.

Not exactly. Basically, you want to prevent W3TC from handling any of the user agents that are being handled by WPtouch.

So this means you take the list of user agents WPtouch is using, which is found under Active Theme > Mobile User Agents > Custom User Agents in WPtouch settings, and copy this list of user agents into W3TC’s Rejected User Agents under Page Cache > Advanced > Rejected User Agents.

That make sense?

@sadhaka – It’s under Page Cache > Advanced > Rejected User Agents in W3TC and under Active Theme > Mobile User Agents > Custom User Agents in WPtouch.

Hi Jonah,

Thank you very much for the reply.

I completely understand if it’s impossible to predict, but is there by chance any average turn-around time on tickets being implemented into updates?

We try to avoid modifying plugins as much as possible to avoid things breaking when updates do come along, so any ballpark estimate would help determine if it’s worth holding off for now or going ahead with a temporary fix.

Thanks again,
R.J.

Thanks for the reply, BraveNewCode.

After continuing to investigate, we discovered the interference was coming from Varnish, additional caching we are using on our server outside of WordPress. We’ll work on a solution for the conflict.

Thanks again for the detailed reply and additional information!

We are also experiencing this issue. Previously had been running WPtouch for years without issue.

We are also running W3 Total Cache but have added the WPtouch user agents to the rejected list in accordance to past reports of the same issue, however this has not solved the problem.

It seems to be happening intermittently and not specific to any browser (although all the reports we’ve heard are from Windows users). The site is: https://www.portent.com/blog.

We’re still looking into it but could definitely use a heads up if this is actually a bug that needs fixing.

*Edit: We are using WPtouch Pro so this is not specific to the free version.

For everyone who’s fed up with Digg Digg and its issues, I did a lot of testing and found Sharebar to be a great, lighter-weight alternative for floating share buttons: https://www.ads-software.com/extend/plugins/sharebar/

Had to go with a different plugin due to time constraints. Thanks anyway.