WP Tavern › Forums › Create Topic
Scott Allen Hi @pepe, at first glance there is nothing that directly interferes with WPSS Maybe at first glance, but WP-SpamShield is a finely tuned and complex plugin. Plugin Organizer breaks a lot actually. It’s very difficult to provide a rock-solid software, when another developer decides to make it easy to interfere with your code. (People would never consider this type of interference on their desktop computer’s software.) Depending on how the user configures PO, it can break miscellaneous form protection (one of WPSS’ key features: protection for third party contact forms other than CF7 and Gravity / protection from a number of random hacking attacks), advanced human spam detection features, and it causes JS not to load on non-form pages, which causes validation errors/false positives when forms are submitted, depending on the site’s caching setup. (To name a few.) We’ll post more details about all this soon. The code disabling WP-SpamShield was removed in October 2017. To clarify, the malware code that deactivated WP-SpamShield and kept it deactivated — even while Plugin organizer was deactivated — was removed in PO v9.2.4. However, it still breaks WP-SpamShield, and a lot of other plugins. Over the years, we’ve dealt with tons of tech support issues on WordPress sites that used Plugin Organizer, that were not even using WP-SpamShield.
Scott Allen
Hi @pepe,
at first glance there is nothing that directly interferes with WPSS
Maybe at first glance, but WP-SpamShield is a finely tuned and complex plugin.
Plugin Organizer breaks a lot actually. It’s very difficult to provide a rock-solid software, when another developer decides to make it easy to interfere with your code. (People would never consider this type of interference on their desktop computer’s software.)
Depending on how the user configures PO, it can break miscellaneous form protection (one of WPSS’ key features: protection for third party contact forms other than CF7 and Gravity / protection from a number of random hacking attacks), advanced human spam detection features, and it causes JS not to load on non-form pages, which causes validation errors/false positives when forms are submitted, depending on the site’s caching setup. (To name a few.) We’ll post more details about all this soon.
The code disabling WP-SpamShield was removed in October 2017.
To clarify, the malware code that deactivated WP-SpamShield and kept it deactivated — even while Plugin organizer was deactivated — was removed in PO v9.2.4. However, it still breaks WP-SpamShield, and a lot of other plugins. Over the years, we’ve dealt with tons of tech support issues on WordPress sites that used Plugin Organizer, that were not even using WP-SpamShield.
Name *
Email *
Website:
Topic Title (Maximum Length: 80):
Forum: — No forum —AI and WordPress Articles Blocks Showcase Discussions Events Introductions Jobs and Working in WordPress Podcast Episodes Site and Block Editor
Enter your email address to subscribe to this blog and receive notifications of new posts by email.
Email Address
Submit
Enter the destination URL
Or link to existing content