Elementor Pro edit not working with Wordfence

Wordfence Community:

Rearding my concerns stated above, I went through Wordfence Diagnostics and found this error. Is this causing my problem?

ERROR:
Connectivity:
Connecting back to this site via IPv6:
wp_remote_post() test back to this server failed! Response was: cURL error 7:

Hi @yqx709abc,

It’s unlikely that the IPv6 error is causing the issue you’re seeing. We recently added a diagnostics check for IPv6, although your site may use Cloudflare which assigns an IPv6 address to your site even if your host doesn’t give you an IPv6 address, so would be a likely cause for a connection failure to be reported.

To try allowing Elementor’s features, 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 the actions with Elementor that were causing issues. 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.

https://www.wordfence.com/help/firewall/learning-mode/ is an amazing resource for learning more about the WAF and learning mode.

Thanks,

Peter.

Hi Peter.

Thank you for your response. Regarding Cloudflare, I’m not familiar with it and do not think Bluehost use it.

I followed your suggestion and put Wordfence in Learning Mode; however, nothing changed.

Unfortunately, I’m not a computer tech person; howver, I did a little more troubleshooting and discovered:

(1) A new page using Elementor Pro cannot be created; originally, I thought only problem was editing existing Elementor pages

(2) Same issue happens “In Cognito” Mode

(3) I went through most of my pages in Wordfence Learner Mode, then reverted back to protecting setting. When I tried to edit one of the pages in Elementor, it went black (as usual); however, a different message showed… “Were sorry, but something went wrong. Click on Learn more and follow each of the steps to quickly resolve it. … click for preview debug” I did that, but could not resolve it.

(4) I also checked “Inspect” (a right click on the existing problem page that reads … (call “the content” function in the current template in order for Elementor to work on this page), and opened the “Console” which showed two red Xs: (BTW… None of the problem pages are templates)
[1] X Undefined web-cli.js?ver=3.7.4:10295
error @ web-cli.js?ver=3.7.4:10295
[2] X Uncaught (in promise) undefined post.php:1

Then, when I checked the two “Issues”, I got this message:

Audit usage of navigator.userAgent, navigator.appVersion, and navigator.platform

A page or script is accessing at least one of navigator.userAgent, navigator.appVersion, and navigator.platform. Starting in Chrome 101, the amount of information available in the User Agent string will be reduced.

To fix this issue, replace the usage of navigator.userAgent, navigator.appVersion, and navigator.platform with feature detection, progressive enhancement, or migrate to navigator.userAgentData.

Note that for performance reasons, only the first access to one of the properties is shown.

TWO AFFECTED RESOURCES
tinymce.min.js:1
wp-polyfill.js:1

I don’t know if anything above helps, just thought I’d let you know what I’ve trying.

Thanks for your patience and kind assistance.

Reards,
Rosalind

Hi Peter.

Oops… Regarding #3 above, I forot to mention the debug preview showed message:

“The $control_id argument is deprecated since version 3.5.0!“

Regards,
Rosalind