Wingers574

Just to be clear here, the behaviour on a iPhone using Contact Form 7 is what I am reporting here. Latest IOS, in my case an iPhone 6. The form bounces down to the bottom of the footer for the site. Not sure why. RIght now as far as I can tell, you cannot submit a Contact Form 7 from an iphone, and if the other reports here are correct, from any Apple device.

Agreed, however in a separate thread it used to be compatible with the TwentyTen WordPress template, it isn’t now, at least you have to go and make some changes. Yes TwentyTen is an old plugin, but if a client does not want to upgrade, then you are stuck with it.

A further comment on this. I have deleted Events Calendar pro and reinstalled it and revalidated the licence. I still have the same problem. The licence appears to be correct. So the only thing I can put this down to is the original site was staged somewhere else before it was turned on in its final location. I detached the licence from the development site and reattached it to the final site.

Additionally removing Events Calendar Pro so that the free version is live does not fix the problem either. However now there is just a grey box where the map was before with no error message.

Removing the free version of Events Calendar and reinstalling it has not resolved it either.

… in answer to the last question. I just visited an established site with an established sitemap and clicked on the link to generate a new site map and the page 404 error did not occur. So it is behaving normally.

I just wanted to flag up that I use this plugin on lots of sites and have had no issues with it at all until yesterday. I too got the page 404 error. I have just turned it on in another (single) site and the same thing happened which is why I came to here. I followed the instructions above about deselecting and reselecting permalinks and saving. That cleared it in my case. So thanks for that. However I use this on 70 sites and it was worked without any problems so sounds like there is a bug in there somewhere. Thanks for building and supporting the plugin.

Just adding more grist to the mill here. I have over 90 WordPress websites that use this firewall. Love the plugin, however as with some other developers that add features into their products, I really do not want something that I have to go around every site and turn on/off because it is flooding me with emails because a new feature has been added. It is not a problem when you have a couple of sites. But for those of us that support lots of people it is a major issue. I have the index.php being reported from all locations. I also do not want to use iControl for security reasons. I am not implying it is insecure, however I do not want multiple methods of accessing all sites through one central console. So that is not a solution for me.
So if you add a feature into a plugin please do it quietly. Don’t add something in that sends out lots of messages. Because the only way to turn it off is to enter each site and change something. I do visit every site at least once every 3 months. At this time I could turn something new on, or generally review the plugins and make changes. Please do not misunderstand my comments, great plugin, great work, just bear in mind that there might be some heavyweight users out there, and not everyone has a couple of sites to tweak.

Paul and whoever else happens to come across this post, I have found out what the reason was in my case. It turns out it was nothing to do with the installation. I copied the whole site to another hosting company I use and it worked fine. I have spent over 6 hours taking this apart and trying different things, however at the end of the day it was the hosting company that caused the problem, not MailPoet or the WordPress installation. In this case I was using NameCheap who seem to have introduced a ModSecurity rule that affects MailPoet installations. The odd thing here is this all worked at the point it was installed. So they introduced this block over the past couple of weeks. The reason is because of a vulnerability which was fixed some time ago. Suggest you ask your hosting company to check any ModSecurity rules that might apply to MailPoet. Once it was identified and the rule whitelisted the site worked fine. Here is the exchange with the hosting support person:
19:23 NameCheap: So it was triggered by ModSecurity rule that our technicians have whitelisted.
19:23 ME: Who put the modsecurity rule in place?
19:24 NameCheap: It is triggered automatically.
19:25 ME: If that is the case why does it not create this error on the other sites I have in your hosting.
19:25 ME: I use the same plugin on multiple sites
19:27 NameCheap: Unfortunately, I cannot answer you as it is triggered in different cases that there is no the exact answer on the questions why and when.
19:28 ME: So what is the current position on this hosting, is it whitelisted now?
19:28 ME: Is there any further action I need to take?
19:29 NameCheap: Yes, it is whitelisted already and it should work in the future. But if you have such issue again, please contact us.
19:29 ME: Can you tell me what the ModSecurity rule was that triggered this?
19:32 NameCheap: It was Access denied with code 403, CSRF vulnerability in the MailPoet Newsletters WordPress plugin before 2.6.11
19:33 ME: But that was a very long time ago, that bug has been fixed for some time. This version is up to date. 2.6.16
19:34 NameCheap: Yes, I understand. But as you can see it triggered that issue.