Plugin Contributor
redsand
(@redsand)
Hi Maxime2,
I’m sorry to hear you had a problem, and I’ll be happy to help.
WP-SpamShield has been tested thoroughly and works quite well with WordPress 4.5, so, the problem is actually more likely due to something else. That’s not to say there isn’t a hidden conflict caused by a change in WP 4.5 that is triggered in edge cases. In these cases we do our best to find them and fix them as fast as possible. But we have tested it on quite a number of configurations with 4.5, in WP_DEBUG mode, and no errors, so it would have to be some very specific combination triggering this. (A perfect storm, if you will.)
Now, there could be quite a number of things causing the issue, and it may not necessarily be due to either the plugin or the WordPress version. It could be one of a number of things, such as plugin conflicts, undiagnosed PHP errors, or configuration issues, to name a few.
If you haven’t had a chance to yet, please take a few minutes to work through the Troubleshooting Guide and FAQs, as these solve over 90% of issues users have.
If those don’t solve the issue for you, we’ll need a bit more info from you on the specifics, and we’ll need to email back and forth, so please head over to the WP-SpamShield Support Form, and take a moment to fill out a support request. That will allow us to take care of this as quickly as possible for you.
– Scott
Please note that the WP-SpamShield Support page is our main support venue, not the WordPress forums here, so that will always be the best way to get a quick response and resolve any tech support issues.