Hi @awdwadwadwad, thanks for reaching out.
With paid plugins, we rarely get the opportunity to run our own tests unless the developers are willing and able to work with us. The good news is that troubleshooting the false-positive could result in resolving the issue without any further action or development from either side.
You may be able to identify and confirm the blocks by observing the records in your Live Traffic page (more info via that link). When clicking any block line (or “eye” icon) to expand it, it will state the reason in red text.
Sometimes an “ADD PARAM TO FIREWALL ALLOWLIST” button appears in this section which you can click to allow these types of request in future.
Also, Learning Mode can help easily allow normal site/plugin operations if they’re being blocked. From the Wordfence Dashboard click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. You could then attempts to replicate the previously blocked actions to teach Wordfence these are normal and should be allowed in future. After your testing, switch the WAF from Learning Mode back to Enabled and Protecting to see if they continue to work.
If you still encounter problems, it’d be helpful to see the block reason message you’re getting in Live Traffic so we can take a look.
Thanks,
Peter.
