Hi @oderycke, thanks for getting in touch.
It’s actually quite an unusual occurrence for it to appear like Wordfence is blocking all plugin updates. Naturally as updates are a normal function of WordPress, we don’t design the plugin to block those out-of-the-box.
If Wordfence is blocking them, you should be able to see the full reasoning in your Live Traffic page immediately after trying to update plugins while Wordfence is enabled. Wordfence logs all blocks it makes here and you can filter by “Blocked” if you like too.
You may find a specific firewall rule or Wordfence setting stated here. The block reason is shown in red text. Feel free to paste that reason here if you’re unable to manually allowlist it using the “ADD PARAM TO FIREWALL ALLOWLIST” button on the Live Traffic page, or by changing the setting within the plugin’s options.
If Live Traffic doesn’t contain an answer, your server/PHP logs could contain timestamped errors when plugin update failures occur. Let us know if that’s in a file/function that Wordfence was trying to use. Your host can help you out with that if you’re unable to access the logs yourself.
Let us know what you find out,
Peter.
Hi !
I need to apologize, the problem doesn’t come from your plug-in. The root problem was a memory limit for the execution of scripts set at 128M. I increased to 512M and all came back to normal. Thanks to Bookly support who found the problem. So that is a good point to know ! 🙂
