error
Forum Replies Created
-
Forum: Plugins
In reply to: [Plugin: Bad Behavior] Bad behavior blocking Stumbleupon ?You can see by looking up the IP address for that request that it did not really come from Google, but from some other ISP in China or Korea or Vietnam or wherever else. Therefore you can know that the request was blocked appropriately.
Forum: Plugins
In reply to: [Plugin: Bad Behavior] it blocks download manager ?Bad Behavior intentionally does not target download managers, as these are most often user-directed and not explicitly malicious. They can be used maliciously, as can most any piece of software, but the vast majority of their use is legitimate, making them inappropriate for blocking within Bad Behavior.
Forum: Plugins
In reply to: Support for Bad Behavior standard in WP Super Cache?Whether to use half-on or full-on mode is up to you. I use both modes on various different sites, all of which also use Bad Behavior.
Forum: Plugins
In reply to: [Plugin: Bad Behavior] Conflicting wiht Robots-MetaLooks like a problem with the Robots-Meta plugin.
Forum: Plugins
In reply to: [Plugin: WP Super Cache] Expired pages not being removedIt’s disabled by default but – as I understand the code – still ends up getting used if semaphores aren’t available for some reason (as on my server). So there are probably a lot of people in this situation that don’t even know it.
Forum: Plugins
In reply to: [Plugin: WP Super Cache] Expired pages not being removedAh, I think I have the problem, let’s see if you agree. In wp-cache-phase1.php there is the following code:
if(defined('DOING_CRON')) { require_once( WPCACHEHOME . 'wp-cache-phase2.php'); return true; } $mutex_filename = 'wp_cache_mutex.lock';So if we’re called from cron, $mutex_filename never gets set! I think instead this should be:
$mutex_filename = 'wp_cache_mutex.lock'; if(defined('DOING_CRON')) { require_once( WPCACHEHOME . 'wp-cache-phase2.php'); return true; }Making this change locally appears to have resolved the problem. The mutex is acquired every time, and the directories are being traversed, and old files are being deleted.
Forum: Plugins
In reply to: [Plugin: WP Super Cache] Expired pages not being removedVery strange, as soon as I added some debugging code, it starts deleting files – at least some of the time. Most of the time, though, wp_cache_phase2_clean_expired() is doing absolutely nothing. It seems that every so often, $mutex_filename is unset, as I occasionally see this error:
wp_cache_mutex_init failed: Array ( [type] => 2 [message] => fopen(/var/www/bad-behavior.ioerror.us/html/wordpress/wp-content/cache/) [<a href='function.fopen'>function.fopen</a>]: failed to open stream: Is a directory [file] => /var/www/bad-behavior.ioerror.us/html/wordpress/wp-content/plugins/wp-super-cache/wp-cache-phase2.php [line] => 156 )Not entirely sure why that’s happening, as it seems it should be set.
Forum: Plugins
In reply to: [Plugin: WP Super Cache] Expired pages not being removedAs far as I can tell, no expired files are being deleted automatically, at all. I’ll check the function you listed and see what it’s doing and if it’s actually even being called.
Forum: Plugins
In reply to: Unable to activate Bad BehaviorSorry, you have not provided enough information to resolve this problem.
What is the URL of the web site on which you installed Bad Behavior?
Who is your web hosting provider?
What operating system are you running on your computer?
Who is your Internet service provider?
Forum: Plugins
In reply to: Support for Bad Behavior standard in WP Super Cache?Indeed, it should be lowercase. If it’s in mixed case on my site, then that’s an error that should be fixed, but no one ever brought it to my attention.
Forum: Plugins
In reply to: [Plugin: WP-SpamFree] Wp_Spamfree blocing legitimate commentsBad Behavior doesn’t strictly require the modification to WP-Super Cache in order to operate. However, without the modification, email harvesters and content scrapers cannot be blocked from cached pages. Since cached pages (different from super cached pages) are usually generated only for HTTP clients which have cookies, and most bots don’t, this has minimal impact, especially in light of the following: Bad Behavior cannot protect super cached pages regardless, since they are delivered to the HTTP client by web server rewrite rules, bypassing WordPress completely.
In any case, it could be added to WP-Super Cache; the modification is designed to do nothing if Bad Behavior is not installed.
Forum: Fixing WordPress
In reply to: Digg submission of links not working with wordpressAgain, you should contact digg and ask them to fix their code.
Forum: Plugins
In reply to: [Plugin: Bad Behavior] Range starting at 0 is legitimateUpdate to Bad Behavior 2.0.23 or later, where issues with OpenID should be fixed.
After taking a second look at that message, the error in the SQL query is quite obvious. You should report this to the author of the Search Everything plugin.
Forum: Fixing WordPress
In reply to: [Plugin: Bad Behavior] Error after upgrading to WordPress 2.6I can’t imagine where that error would be coming from. As another person mentioned, that table no longer exists. My guess is it’s another plugin you’re running that you need to update.