It seems that compatibility has worn off now as all I see is back-end markup going front end when it is using out-of-the-box features. It is disappointing to see symbols and meta characters coming up by default and having to manually edit the text in each and every post/page just to get the score to green as the plugin just fails to auto-populate absolutely ANYTHING correctly anymore. This makes the convenience of the choice disappear entireley.
Currently the worst part is AIO SEO cannot even detect focus keyphrases which ARE present in the places it calls for, however it seems to not know how Divi works? Also unlike how Google search spiders can, AIO SEO seems incapable of seeing words once they are pluralised – eg: service does not come up as a focus keyphrase, however services does, even though the word in totality is actually present within “services”.
Please help as this is on hundreds of my client’s sites and I am almost considering removing it and switching to Yoast! This includes several paid accounts because I need repeatability and reliability being a full stack developer, host and registrar internationally. I’m under high demand and don’t have time for stuff that does not work as described or is in beta test on the live public without their knowledge.
]]>What is going on? Why this discepancy?
]]>I am using Sucuri WP Plugin (Free) version. Yesterday, our infosec detected a malware on the site but Sucuri could not detect it. It was lately detected that my themes functions file was infected and it is not logged anywhere. I asked the hosting company to scan and clean the website but I want to know the reason of it not getting detected by the plugin.
]]>Am user of word fence freemium.; used word fence plugin for 1.5 years. in pass few day I have some malware in my site ALLAHCALL, upon cleaning the malware i saw 2 file word fence (in word fence folder named as wflogs) this folder typically found in your WordPress content folder dictionary (https://yoursiteurl/wp-content/wflogs).
Path of that suspicious files are ; https://allahcall.com/wp-content/wflogs/attack-data.php & https://allahcall.com/wp-content/wflogs/config-synced.php
I try to remove that suspicious code but could not remove them. Help me out.
]]>I am using Cloudflare Cache and Autoptimize.
]]>So far I’ve looked at file permissions, and uninstalled and reinstalled Wordfence, but I don’t know why it can’t detect the reverse shell, the changes to the index, and all the malicious plugins.
]]>
!
I know there is a specific functionality designed in Polylang to detect the browser language. But due to the fact that I have to use cache plugins to speed up my site, detection is disabled.
Is there a way to re-implement this functionality, perhaps with JavaScript, with a PHP snippet or something? It’s very useful and it’s a pity to have to sacrifice it for page speed.
Kind regards.
]]>I get poor performances on my website due to the lack of your CDN? According to Gtmetrix it is not enabled even though it is on my Nitropack dashboard?
Thanks in advance.
]]>Issue:
For some odd reason, Wordfence detected our Name Server IP (not Site IP), blocked it, and now displays it in Wordfence’s Widget (“Top 5 IPs Blocked”).
Details: https://ibb.co/2Kz6wJs
When the above happened, Wordfence was in learning mode. Also, our IP detection option was set to “Let Wordfence use the most secure method to get visitor IP addresses. Prevents spoofing and works with most sites. (Recommended)”
Our host is SiteGround and we’re using Cloudflare.
Questions:
(1) What caused Wordfence to block our Name Server IP?
(2) How can we clear the Name Server IP entry shown in our Widget?
(3) Should we Whitelist both our Name Server IPs and Site IPs?
(4) What can we do to prevent the above from happening again?
(Note: We have switched our Firewall from “Learning Mode” to “Enabled and Protecting.” Also, we have switched our IP detection option from “Let Wordfence use the most secure method …” to “Use the Cloudflare “CF-Connecting-IP” HTTP header to get a visitor IP. Only use if you’re using Cloudflare.”)
Help appreciated!
]]>