Title: error's Replies - page 5 | WordPress.org

---

# error

  [  ](https://wordpress.org/support/users/error/)

 *   [Profile](https://wordpress.org/support/users/error/)
 *   [Topics Started](https://wordpress.org/support/users/error/topics/)
 *   [Replies Created](https://wordpress.org/support/users/error/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/error/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/error/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/error/engagements/)
 *   [Favorites](https://wordpress.org/support/users/error/favorites/)

 Search replies:

## Forum Replies Created

Viewing 15 replies - 61 through 75 (of 231 total)

[←](https://wordpress.org/support/users/error/replies/page/4/?output_format=md) 
[1](https://wordpress.org/support/users/error/replies/?output_format=md) [2](https://wordpress.org/support/users/error/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/error/replies/page/3/?output_format=md) 
[4](https://wordpress.org/support/users/error/replies/page/4/?output_format=md) 
5 [6](https://wordpress.org/support/users/error/replies/page/6/?output_format=md)…
[14](https://wordpress.org/support/users/error/replies/page/14/?output_format=md)
[15](https://wordpress.org/support/users/error/replies/page/15/?output_format=md)
[16](https://wordpress.org/support/users/error/replies/page/16/?output_format=md)
[→](https://wordpress.org/support/users/error/replies/page/6/?output_format=md)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Plugin: Bad Behavior] Bad behavior blocking Stumbleupon ?](https://wordpress.org/support/topic/plugin-bad-behavior-bad-behavior-blocking-stumbleupon/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [16 years, 10 months ago](https://wordpress.org/support/topic/plugin-bad-behavior-bad-behavior-blocking-stumbleupon/#post-1068685)
 * 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Plugin: Bad Behavior] it blocks download manager ?](https://wordpress.org/support/topic/plugin-bad-behavior-it-blocks-download-manager/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [16 years, 10 months ago](https://wordpress.org/support/topic/plugin-bad-behavior-it-blocks-download-manager/#post-1170975)
 * 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [Support for Bad Behavior standard in WP Super Cache?](https://wordpress.org/support/topic/support-for-bad-behavior-standard-in-wp-super-cache/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [16 years, 10 months ago](https://wordpress.org/support/topic/support-for-bad-behavior-standard-in-wp-super-cache/#post-998779)
 * 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Plugin: Bad Behavior] Conflicting wiht Robots-Meta](https://wordpress.org/support/topic/plugin-bad-behavior-conflicting-wiht-robots-meta/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [16 years, 10 months ago](https://wordpress.org/support/topic/plugin-bad-behavior-conflicting-wiht-robots-meta/#post-1193043)
 * Looks like a problem with the Robots-Meta plugin.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Plugin: WP Super Cache] Expired pages not being removed](https://wordpress.org/support/topic/plugin-wp-super-cache-expired-pages-not-being-removed-1/)
 *  Thread Starter [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [16 years, 11 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-expired-pages-not-being-removed-1/#post-1226848)
 * It’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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Plugin: WP Super Cache] Expired pages not being removed](https://wordpress.org/support/topic/plugin-wp-super-cache-expired-pages-not-being-removed-1/)
 *  Thread Starter [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [16 years, 11 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-expired-pages-not-being-removed-1/#post-1226827)
 * Ah, 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Plugin: WP Super Cache] Expired pages not being removed](https://wordpress.org/support/topic/plugin-wp-super-cache-expired-pages-not-being-removed-1/)
 *  Thread Starter [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [16 years, 11 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-expired-pages-not-being-removed-1/#post-1226825)
 * Very 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Plugin: WP Super Cache] Expired pages not being removed](https://wordpress.org/support/topic/plugin-wp-super-cache-expired-pages-not-being-removed-1/)
 *  Thread Starter [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [16 years, 11 months ago](https://wordpress.org/support/topic/plugin-wp-super-cache-expired-pages-not-being-removed-1/#post-1226824)
 * As 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [Unable to activate Bad Behavior](https://wordpress.org/support/topic/unable-to-activate-bad-behavior/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [17 years, 1 month ago](https://wordpress.org/support/topic/unable-to-activate-bad-behavior/#post-1156037)
 * Sorry, 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [Support for Bad Behavior standard in WP Super Cache?](https://wordpress.org/support/topic/support-for-bad-behavior-standard-in-wp-super-cache/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [17 years, 5 months ago](https://wordpress.org/support/topic/support-for-bad-behavior-standard-in-wp-super-cache/#post-998699)
 * 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](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Plugin: WP-SpamFree] Wp_Spamfree blocing legitimate comments](https://wordpress.org/support/topic/plugin-wp-spamfree-wp_spamfree-blocing-legitimate-comments/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [17 years, 8 months ago](https://wordpress.org/support/topic/plugin-wp-spamfree-wp_spamfree-blocing-legitimate-comments/page/2/#post-891640)
 * Bad 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](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [Digg submission of links not working with wordpress](https://wordpress.org/support/topic/digg-submission-of-links-not-working-with-wordpress/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [17 years, 11 months ago](https://wordpress.org/support/topic/digg-submission-of-links-not-working-with-wordpress/page/2/#post-662881)
 * Again, you should contact digg and ask them to fix their code.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Plugin: Bad Behavior] Range starting at 0 is legitimate](https://wordpress.org/support/topic/plugin-bad-behavior-range-starting-at-0-is-legitimate/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [17 years, 11 months ago](https://wordpress.org/support/topic/plugin-bad-behavior-range-starting-at-0-is-legitimate/#post-824653)
 * Update to Bad Behavior 2.0.23 or later, where issues with OpenID should be fixed.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Search Everything & Bad Behavior] WP database error searching in Manage Posts](https://wordpress.org/support/topic/search-everything-038-bad-behavior-wp-database-error-searching-in-manage-posts/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [17 years, 11 months ago](https://wordpress.org/support/topic/search-everything-038-bad-behavior-wp-database-error-searching-in-manage-posts/#post-798728)
 * 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](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
   
   In reply to: [[Plugin: Bad Behavior] Error after upgrading to WordPress 2.6](https://wordpress.org/support/topic/plugin-bad-behavior-error-after-upgrading-to-wordpress-26/)
 *  [error](https://wordpress.org/support/users/error/)
 * (@error)
 * [17 years, 11 months ago](https://wordpress.org/support/topic/plugin-bad-behavior-error-after-upgrading-to-wordpress-26/#post-824652)
 * I 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.

Viewing 15 replies - 61 through 75 (of 231 total)

[←](https://wordpress.org/support/users/error/replies/page/4/?output_format=md) 
[1](https://wordpress.org/support/users/error/replies/?output_format=md) [2](https://wordpress.org/support/users/error/replies/page/2/?output_format=md)
[3](https://wordpress.org/support/users/error/replies/page/3/?output_format=md) 
[4](https://wordpress.org/support/users/error/replies/page/4/?output_format=md) 
5 [6](https://wordpress.org/support/users/error/replies/page/6/?output_format=md)…
[14](https://wordpress.org/support/users/error/replies/page/14/?output_format=md)
[15](https://wordpress.org/support/users/error/replies/page/15/?output_format=md)
[16](https://wordpress.org/support/users/error/replies/page/16/?output_format=md)
[→](https://wordpress.org/support/users/error/replies/page/6/?output_format=md)