• Every time I want to save my settings in the plugin in my sidebar. I got this.

    A background request to WordPress was just blocked for the URL /wp-admin/admin-ajax.php. If this occurred as a result of an intentional action, you may consider whitelisting the request to allow it in the future.

    It comes when I go in Appearance> Widget> and then when try to put widgets in my sidebars. (Recent Posts Extended Plugin)

    Hope someone can help.

    Kindest Regards

    Søren

    https://ww.wp.xz.cn/plugins/recent-posts-widget-extended/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Mike Clayton

    (@mike-clayton)

    I’m getting this too. And because I am using Thrive Content Builder, the dialogue is coming up under a layer that means I can’t click to white list. GRRRR. I use WordFence and wonder if this is part of the problem.

    Thread Starter Soren Guldberg Kjer

    (@fairsosworld)

    Hehe Mike thank you a lot it help to Deactivate wordfence. I owe you a big danish beer ;D
    But yes it’s still a problem….. https://ww.wp.xz.cn/plugins/wordfence/

    Mike Clayton

    (@mike-clayton)

    You’re welcome. In fact, on another WP thread, someone suggested setting WordFence to Learning mode – that way, the link will be whitelisted as well. That is also what Thrive recommended to me.

    sitedesigndev

    (@sitedesigndev)

    @mike Clayton

    If you cant click the “whitelist this action” button because it is under your content builder, may I suggest pushing it to the top or pushing your content builder to the bottom with z-index CSS.

    Use a browser such as Chrome and right-click on your page then click on inspect element. Then find the main container of either your content builder or wordfence notification and dynamically edit the z-index properties in CSS in the inspect element options to move one on top of the other.

    This should allow you to click on the “whitelist this action” button.

    Mike Clayton

    (@mike-clayton)

    sitedesigndev – Wow. What a cool tip. I had no idea you can do that. Thank you!

    Thanks a lot for both of you Mike and sitedesigndev.

    The Thrive builder works now when I set the Wordfence on learning mode.

    I suppose the instruction of sitedesigndev would have worked too but it got a little bit too tehcnical for me since it is working now.

    Hopefully I can soon set Wordfence firewall working normally and it wont conflict anymore.

    But great advices thank you!

    I think this is WordFence working normally. Until it detects the Thrive action in learning mode, it detects the activity as potentially harmful.

    I only needed WF in learning mode for one cycle of saving a TCG visual editor page. I then re-activated it, and now, I assume, it knows enough about the Thrive actions to see them as user-intended.

    @sitedesigndev – Yes, exaclty !! I’ve also followed this type of CSS trick. I’ve just set overlay ‘display:none’ from inspect element.

    And this was allowed me to click on “whitelist this action” button.

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Background Request Blocked’ is closed to new replies.