Hi @danielx147, thanks for your message.
I may need to check whether the “/wp-content/themes/rehub/functions/rhpostviewcounter.php” file accepts the “ID” POST parameter that the “/rehub-ajax.php” file accepts because that’d be the easier one to add to the allowlist. I say this because rehub-ajax may have been relocated as per those instructions. If you have, you could add:
- URL: /rehub-ajax.php (alter path if this file isn’t in root)
- Param Type: POST Body
- Param Name: ID
You could also try swapping in /wp-content/themes/rehub/functions/rhpostviewcounter.php as the URL in case this also accepts the ID parameter as discussed above.
Learning Mode might help, although the firewall is usually in this mode by default for 7 days after installation so I’d have expected this to be allowlisted already if that method was going to work.
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. Now perform actions such as viewing pages that trigger the counter script(s). This will help Wordfence learn that these actions are normal and it will allow them in the future. After you have finished performing the actions, switch the WAF from Learning Mode back to Enabled and Protecting. Now test to see if these actions work correctly.
Let me know how you get on!
Thanks,
Peter.