Bit51 (part of the iThemes family)
Forum Replies Created
-
Thanks! Will do.
Who is your host? Maybe I can look into it from that angle..
Hi Didier,
First, the 404s could very easily be found for quite a while after a plugin is removed. That isn’t necessarily something to worry about and is in fact normal in many cases.
Now for the other questions:
a.) I’m afraid I don’t know exactly what you mean here. It will look for changes in any file, block almost all bots, etc. It can’t however protect against every attack. Nothing can be 100% attack-proof
b.) No, I wouldn’t erase the database. The 404 errors will work themselves out over time and even cleaning the db won’t remove them from the sites that are linking to them.Forum: Everything else WordPress
In reply to: Plugin "broken" link being abused.Wow. That’s extremely frustrating. Is there anyway us devs could see a list of IPs that submitted and the timestamp? I would be willing to bet, in my case anyway, that there will be quite a similarity.
You can turn off automatic blacklisting however, as the feature is intended for security rather than anything else, you cannot turn off the lockouts. Perhaps adjusting the values to a very high threshold in a very limited time period would do the job for you?
I will take a look. Thanks for the suggestion.
Haha! Welcome to WordPress. In their defense many other important paths such as wp-content can be overridden. wp-login.php is one of the few exceptions.
Thanks Sally!
There had been a missed variable the didn’t sanitize the user_agent displayed in the dashboard. It was fixed within a few hours of being noticed.
That is correct. There really is no good way around this short of hacking core to work around it. That’s something I really don’t think should be in a plugin 😉
Hi Sally,
That’s actually been an issue on and off for a while. Currently, with WP 3.4 it’s come back with the fix I needed to make to make hide backend work at all. I do know about it though and I do hope to have a complete fix for it in the next release (probably a week or two as I don’t want to start rapid-fire releases again).
if am_enabled is 0 it shouldn’t work unless the query is somehow cached (ie you have db query caching turned on). You can also overide by deleting bwps_awaymode from the options table.
Thanks for the idea. I’ll take a look at incorporating it.
Yes, please upgrade. 3.4.1 are just the official push of that fix and a couple others.
What is WP Robot and how does it not work? Is it conflicting with a specific feature, causing an error message, or something else?