• Resolved Ovidiu

    (@ovidiu)


    upon activation of the new version I am getting:

    Plugin could not be activated because it triggered a fatal error.

    Warning: require_once(/var/www/knightsenglish.com/wp-content/plugins/bad-behavior/bad-behavior/version.inc.php): failed to open stream: No such file or directory in /var/www/knightsenglish.com/wp-content/plugins/bad-behavior/bad-behavior-wordpress.php on line 159 Fatal error: require_once(): Failed opening required '/var/www/knightsenglish.com/wp-content/plugins/bad-behavior/bad-behavior/version.inc.php' (include_path='.:/usr/share/php:/usr/share/pear') in /var/www/knightsenglish.com/wp-content/plugins/bad-behavior/bad-behavior-wordpress.php on line 159

    https://www.ads-software.com/extend/plugins/bad-behavior/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter Ovidiu

    (@ovidiu)

    I have deleted the plugin and re-installed and I am getting he same behavior.
    For now I downgraded again to 2.0.44

    That’s strange, because that line contains this…

    require_once(BB2_CWD . “/bad-behavior/core.inc.php”);

    And the error you got indicates it’s looking for the file “version.inc.php”. Does line 159 in your bad-behavior-wordpress.php file say “core.inc.php” or “version.inc.php” ?

    Thread Starter Ovidiu

    (@ovidiu)

    I figured it out and it was all my fault. I’ll explain in detail in case someone else has a similar problem:

    I am using APC on my server and had enabled this variable:

    apc.stat

    this is its definition:

    Be careful changing this setting. This defaults to on, forcing APC to stat (check) the script on each request to determine if it has been modified. If it has been modified it will recompile and cache the new version. If this setting is off, APC will not check, which usually means that to force APC to recheck files, the web server will have to be restarted or the cache will have to be manually cleared. Note that FastCGI web server configurations may not clear the cache on restart. On a production server where the script files rarely change, a significant performance boost can be achieved by disabled stats.

    For included/required files this option applies as well, but note that for relative path includes (any path that doesn’t start with / on Unix) APC has to check in order to uniquely identify the file. If you use absolute path includes APC can skip the stat and use that absolute path as the unique identifier for the file.

    I had disabled checking for changed scripts since all apc ttl settings on this particular site are set to 1h and nothing much changes except for plugin updates of course. Once I emptied the opcode cache everything was good ??

    @treydock: it was you who was maintaining that modified wpmu bad behavior version, wasn’t it? Is there any way of subscribing to news and updates about it?

    I’m in the process of making the updates to the WPMU version more readily available. For now I’d look at https://itscblog.tamu.edu/bad-behavior-wpmu/. I posted yesterday an updated version that just incorporates the changes from 2.1.14.

    – Trey

    Thread Starter Ovidiu

    (@ovidiu)

    thx!

    Thread Starter Ovidiu

    (@ovidiu)

    there is a new version of BB out – do you by any chance have a new version planned too? ??

    I haven’t yet updated mine to 2.1.15. It’s on my to-do list. Be probably a few days.

    There’s a few changes I’ve made that may be added to it , or as a separate download. One allows the whitelist to be specified in the Admin interface via dashboard rather than the whitelist.ini file. The other also allows for the email address shown to blocked clients to be changed. I’m sending them to the BB dev to hopefully be added to the core product.

    – Trey

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘[Plugin: Bad Behavior] upgrade from 2.0.44 to 2.1.14 breaks functionality’ is closed to new replies.