[Plugin: Bad Behavior] Errors on Activation -headers already sent and Notice:

wpsecuritylock
(@wpsecuritylock)

12 years, 11 months ago

Just did a fresh install of WordPress 3.1.3. I installed and activated Bad Behavior 2.0.43.

After activation, I received this error:

The plugin generated 444 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.

I deactivated the plugin and then reactivated and the same error (above) appeared.

Also, in debug mode, I received these errors:

Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /home/test/wp-includes/functions.php on line 3303

Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /home/test/wp-includes/functions.php on line 3303

Warning: Cannot modify header information – headers already sent by (output started at /home/test/wp-includes/functions.php:3303) in /home/reggie64/public_html/wpsecuritylock/rsnew/wp-content/plugins/bad-behavior/bad-behavior/screener.inc.php on line 8

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/test/wp-includes/functions.php on line 3387

Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/test/wp-includes/functions.php on line 3387

http://wordpress.org/extend/plugins/bad-behavior/

Viewing 3 replies - 1 through 3 (of 3 total)

treydock
(@treydock)

12 years, 11 months ago
The “get_settings” and “has_cap” I believe are related to the use of older WP methods for determining a user’s privileges. If you run this shell command under wp-content/plugins it will output all instances of this deprecated usage…

grep -HnR "add_[a-zA-Z].*_page.*, [0-9]*," ./

See here for the original discussion, http://wordpress.org/support/topic/has_cap-was-called-with-an-argument-that-is-deprecated?replies=13#post-2074323 .

The mod bad behavior I’m working on will correct this , at least for wpmu users. Here’s the offending code…and followed by the solution…
```
add_submenu_page('ms-admin.php', 'Bad Behavior', 'Bad Behavior', 10, 'bb2_manage', 'bb2_manage');
add_submenu_page('ms-admin.php', 'Bad Behavior Options', 'Bad Behavior Options', 10, 'bb2_options', 'bb2_options');
```
new…
```
add_submenu_page('settings.php', 'Bad Behavior', 'Bad Behavior', 'manage_network', 'bb2_manage', 'bb2_manage');
add_submenu_page('settings.php', 'Bad Behavior Options', 'Bad Behavior Options', 'manage_network', 'bb2_options', 'bb2_options');
```
These are the replacement for the integer based permission levels…http://codex.wordpress.org/Roles_and_Capabilities

Hope that helps

– Trey
Thread Starter wpsecuritylock
(@wpsecuritylock)

12 years, 10 months ago

Thanks for looking into this Trey. Hopefully a new version will be out soon so.

Plugin Author error
(@error)

12 years, 8 months ago

You most likely have a plugin conflict. On line 8 of screener.inc.php Bad Behavior tries to set a cookie. This message means that some other function somewhere (i.e. in another plugin, or possibly in WordPress core (but that’s a bug in WP)) has started sending output to the browser too early. Try disabling plugins until you find the offending plugin. BTW you should contact the plugin author if you need support with the plugin.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘[Plugin: Bad Behavior] Errors on Activation -headers already sent and Notice:’ is closed to new replies.