• From my understanding how the whitelisting of parameters is done on a specific url without a way to whitelist multiple urls. Respectively, this is done through learning mode or manually entering in the parameters to the whitelist table done in this manner:
    URL/Param:
    URL: /
    Param: POST Body
    Param Name: fl_builder_data][settings][html

    For us this creates an issue with front-end builder plugins like Beaver Builder and iframes since every page needs to whitelisted separately for every parameter to allow for front-user to embed iframes and not to have them get blocked. In order to whitelist across the site, you would need to add each and every page to the whitelist table.

    This is not practical for us since we give our clients to build their own pages with the page builder (Beaver Builder). From searching around on the forum, I know the topic of whitelisting parameters globally has come up before which the issue has been investigated in the past (with reference number: #3018). I am just looking into a more valuable solutions to tone down on frustration since our clients are nonprofits, who are not technical and can’t afford to have technical member on staff, from our side in which trying to whitelist several page for hundreds clients really builds up. I am just inquiring about the statues of this improvement, since for us whitelisting IP is an non option or is turning off XSS: Cross Site Scripting rules for our clients. Being a developer myself, I understand respectively if this is still being worked on and in is the pipeline.
    Thanks!

The topic ‘Whitelisting Global Params’ is closed to new replies.