gaffer.wiles
Forum Replies Created
-
I will try that. Thanks!
A followup on the issue of the strange behavior of my Divi-based WordPress site WordFence when a podcast player script is embedded:
I got the following notification from WordFence today and it seems to point to WordFence blocking what it sees as an XSS attack:
105.233.84.247 (South Africa)
Blocked for XSS: Cross Site Scripting in POST body: modules=[{“type”:”et_pb_section”,”attrs”:{“_builder_version”:”4.5.1″,”_module_preset”:”default”,”background_…
Would there be some way to whitelist this particular activity without compromising on WordFence’s protection?
I will see if I can get the server logs from my hosting company.
Unfortunately this bulletin board does not accommodate screen shots so I can’t show you what I think is a crash.
1. The webpage is displayed with all the text and graphics in place, including menus, links, button etc.
2. I insert the code into the Divi Builder Code module and preview.
3. Page flashes briefly and the website background texture and the menus appear but all the other graphics and modules are gone and the Divi Builder appears with the error message I posted earlier.
4. I remove the code module and refresh the page and it displays normally with the RedCircle podcast player in place and working.
5. I go to the Worpress backend Plugins menu and Deactivate WordFence and go back to the page and reinsert the podcast player page into the Divi code module and refresh and display the page.
6. The player displays perfectly and plays correctly. I save the page and Reactivate the WordFence plugin and refresh the page and it flashes and displays only the background texture and the basic menu. all other content disappears.
I don’t think it is a server issue.
I have upgraded to a higher package on my hosting company which will give me a bit more PHP memory. Costs a lot more, but I hope the investment will be worth it albeit just to get WordFence to work.
No I don’t have SEO Ultimate installed as a plugin. My WordPress host 1&1 has a 32Mb limit on the memory available for WordPress installs. WordFence worked well up to it’s last version but now it bugs out with a memory error. I have disabled it. I could upgrade to a higher package with more memory, (at a higher cost to me) but that defeats the purpose of the issue – that being the latest version of WordFence uses more memory.