Plugin Support
wfmark
(@wfmark)
Hi @soolee, thanks for reaching out and sorry to hear you’re having trouble with this.
I tested this on my end, but I didn’t get any errors.
Could you please try adding it manually in Wordfence > All Options > Allowlisted URLs then set something like the below:
URL: /path/to/script.php
Param Type: Query String
Param Name: theme_name
This could also be an issue with plugin/theme conflicts too. The best way to test is to run Wordfence and Beaver Builder as your only enabled plugins and also revert to a default theme such as Twenty Twenty-Three. If you are able to create entries on Beaver Builder, then reenable your plugins and theme one by one until it breaks again to help find the cause.
Let me know how it goes.
Thanks,
Mark.
Thread Starter
soolee
(@soolee)
I just tried creating another Beaver Builder entry and received the message again. Here is the message without our actual site name:
https://www.xyz.com/?page_id=933&fl_builder
here is what was automatically added to the Allowlisted URLs via the false positive dialog
request.body[fl_builder_data][node_preview][items][8] 10/16/2023, 6:14:25 AM Allowlisted via false positive dialog
below you can see this false positive was previously added in learning mode a month ago:
request.body[fl_builder_data][node_preview][items][1] 9/17/2023, 10:07:19 AM Allowlisted while in Learning Mode.
please tell me the steps to deconstruct this entry and add it manually per your suggestion.
Thread Starter
soolee
(@soolee)
as a test, i deactivated Wordfence and was able to create Beaver Builder entries without a problem.
Plugin Support
wfmark
(@wfmark)
Hi @soolee, Thanks for getting back to us.
It looks like the parameter keeps changing and that might be why the allowlist doesn’t work. Could you please try disabling the “Admin Panel” option for “Monitor background requests from an administrator’s web browser for false positives”:
https://www.wordfence.com/help/firewall/options/#monitor-background-requests
As the plugin worked with Wordfence but has recently changed, it’s also likely the way Beaver Builder works was recently updated by the developers. We’ve seen an issue before where unique IDs in every POST/GET request struggle to be permanently allowlisted.
Let me know if this helps.
Thanks,
Mark.
Thread Starter
soolee
(@soolee)
we created a new page with a new module and it’s working without any problems. we also deleted all of the Allowlisted URLs rules without any problems.
we think we might have hit a limit in the number of module entries and that apparently caused these obscure errors.
thanks
Plugin Support
wfmark
(@wfmark)
@soolee, Thank you for the update.
If you ever need assistance with any other issues, please create a new topic and we will be happy to help.
Thanks,
Mark.