Anti-Spam, Spam-Schutz, ReCaptcha für alle Formulare und Logins

Änderungsprotokoll

4.1.2

• CSRF vulnerability fixed

4.1.1

• Improved Pattern recognition
• Solved: Warning for usage of empty keys

4.1

• Fail2Ban-Support added
• Problems with Thrive Comments and json-based submissions fixed

4.0

• The automatic mode has been removed. From now on, all form types require manual configuration of associated patterns and actions to ensure the spam protection functions correctly.
• During plugin installation, the appropriate actions and patterns for major form builders will be automatically added to the scope—provided the respective form builder is installed.
• Adding new form types to the spam protection, which are not yet included by default, can still be done via the analysis mode or direct analysis mode.
• If important patterns or actions are missing, I appreciate any feedback and suggestions for improvements.
• This update ensures targeted spam protection configuration while still allowing automatic detection of widely used form builders.

3.8.1

• Fixed: Erroneous error handling for file-uploads (i.e. Fancy Product Designer)

3.8

• Fixed: Problems with IP-Forwarding and load-balancing led to always false-positives

3.7.3

• SQL-Bug during installation routine fixed

3.7.2

• Optimized symbols in the settings menu

3.7.1

• Fixed: Bug with empty field „Skip fields from saving“

3.7

• Highly recommended security feature „Skip fields from saving“ on the tab „Saving Messages“ on the plugins options page added. This feature is intended to exclude fields (i.e. password fields) from beeing saved with messages. Background: The plugin is identifying password fields on the form and skips them from beeing saved already. But in the case of the event that JavaScript is crashing, the identification process may fail and thus the password will be saved nevertheless. Therefore this option shall be used to define password fields manually that shall be skipped from saving.

3.6.10

• Fixed: Bug with hiding the menu in initial state of the settings menu

3.6.9

• Fixed: Bug with the new feature to stop logging logins

3.6.8

• New feature: The admin area is turned to red as long as the simulation mode is on
• New feature: The messages inbox can be hidden, by setting its position to -1
• New feature: The logging of login-messages can be switched off

3.6.7

• Fixed: Variables that where not initialized caused warnings on higher debug-levels

3.6.6

• Problem with forminator and possibly other form builders too fixed: Bots where able to bypassed the pattern matching and thus the spam check too.

3.6.5

• Fixed: A dedicated spam-check for WordPRess-standard-requests was introduced, in order to treat them differently from other post-requests. It turned out that some spam showed up after the last release. This should not happen anymore

3.6.4

• Fixed: In v.3.5.5 the plugin was changed to apply the spam check always on WordPress standard submissions such as comments. Even in explicit mode. This behaviour is changed now, in a way that even for WordPress standard submission types patterns have to match, before they are checked for spam.
• This means: If you are using WordPress standard submission-types such as comments and posts, from now on you need to add the respective patterns for them, as for any other type of submission, in order to make the spam check work for them.

3.6.3

• Bug mit Eingangsboxen gefixt

3.6.2

• Performance für Administrationsbereich und Eingangsboxen verbessert
• Bug mit leeren Seiten für Eingangsboxen gelöst

3.6.1

• Ladefehler für direkten Analysemodus gefixt

3.6

• „Direkter Analysemodus“ hinzugefügt: Dieser Modus erlaubt eine einfachere Administration, da Übermittlungstypen ab jetzt direkt aus dem jeweiligen Formular dem Spam-Check hinzugefügt werden können
• Einstellungsseite in Tabs unterteilt