What happened: your plugin seems has recently updated.
Since a very long time that your plugin captured 100% of spam, today from different websites that run your plugin, I start to get spam delivered. Something very bad to see and this seems related to your recent update.
What I can see is that the spam message has been delivered in forminator form and this never happened before and is happening on more websites.
What also expect if your plugin is working well is to find in your plugin messages section, this spam messages that was not spam for your plugin but no messages are listed in Messages. The delivered spam message is not there and is not also in the spam section of your plugin.
I want having back the good plugin that was in the previous version, the new one is delivering spam and seems is not working correctly.
I’m replacing in all websites the version 3.6.4 with 3.6.3 and renaming in the plugin the version to be the latest one and prevent WordPress to update it. I hope you will be able to figure out why.. your plugin is not working well as before and is delivering spam. This is the first time your plugin stopped to protect well from the spam. Is not a good sensation and experience.
Ciao.
I have fixed a bug and by that created a new one. Sorry for that!
Now I have just fixed the new one too. But the new release has a major change:
Some submission types up to now where checked for spam in explicit mode, even if you didn’t recognize them with a specific pattern. I have changed this behaviour, due to an erroneous behaviour with some form builders. Therefore these submission types now require for a pattern too.
You mentioned that you cannot see them in your inbox, this should have changed with the latest release.
Ciao, Matthias
Hi, thanks for the reply.
I’m scared now to update.. also if the update will be done automatically from WordPress.
what happen in the version 3.6.4 to allow spam coming in my inbox?
I read about last change that never include anymore something that was included. Sound not very nice this change but I should be not affected by this has I have already configured the explicit mode for WordPress comment and Forminator so.. I believe I should not having issues. Thanks for explain that the change was necessary due to some plugin compatibility.
Do you found a bug after my topic here? Was the bug that cause spam able to coming in in ox? What happened?
I hope the new version 3.6.5 never allow spam to coming again in the inbox. There are a lot of spam bot that generate spam 🙂 without a spam protection mailbox can be very stressed.
Thank you! I hope the update will work… I had to restore in all website the previous version after more then one website and messages has been delivered to inbox disturbing web admins.
Hi.
I can understand that.
What has happened was the following:
Up to now, some standard types of WordPress-Post-Requests where always checked for spam, as I was thinking they are always the right choice. But it has turned out, that in some circumstances they are not. Therefore I have changed that behaviour in a way, that you now have to register a pattern for them too.
But with the release of Yesterday I have reactivated a former bug for these standard types: In some cases these standard calls, seem to be processed on another path of application than the “pattern check”. Therefore it occured, that the superglobal $_POST which on server side represents the parameters passed by a post-calls, arrives empty at both points: The point when the patterns check is processed and the point when the message is saved. Nevertheless at this point I am setting a so called hook, that is catching the standard calls. And if they catch them the superglobal $_POST is always filled. In the past, when the respective hook was triggering the spam check was processed always. With the last released I have conditioned the call of the hook, which led to the problems that you mentioned.
Now instead I have changed
- that the hook is still called always,
- but when the hook is triggering the pattern matching and the saving of the analysis messages are processed and the spam check is only processed if the respective pattern is found
Therefore now for these types of standard calls patterns have to be formed. These calls are for instance mainly “comments” and “blog-entries”, which are two types of WordPress- standard calls.
I hope that explanation can be understood :-). If you face problems with the 3.6.5 release, we can have a look on it during a teams session, if you like.
Ciao, Matthias