Topic: troubleshooting the debug.log · BuddyPress.org

Skip to:: Content; Pages; Categories; Search; Top; Bottom

troubleshooting the debug.log

Paul-tCGs
Participant

@paul-tcgs

8 years, 10 months ago

Hey folks,

Still trying to track down a problem with the activation of BuddyPress on our site. In the debug.log which was suggested I turn on and review, have lots of these..

[29-Dec-2015 20:12:48 UTC] PHP Notice: bbp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). Please see Debugging in WordPress for more information. (This message was added in version 2.3.) in /home/content/p3pnexwpnas04_data03/90/2440390/html/wp-includes/functions.php on line 3787

and some of these..

[29-Dec-2015 20:12:48 UTC] PHP Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use __construct() instead. in /home/content/p3pnexwpnas04_data03/90/2440390/html/wp-includes/functions.php on line 3619

and these too.

[29-Dec-2015 20:12:49 UTC] PHP Notice: Trying to get property of non-object in /home/content/p3pnexwpnas04_data03/90/2440390/html/wp-content/plugins/jetpack/modules/gravatar-hovercards.php on line 238

………

I guess the bottom line question, is there a way to find older versions of plugins of various sorts to go backwards in time on them?

Or are we regularly tweaking the php files of plugins?

If anyone has any ideas for fixes, we’ll I’d appreciate any minutes you can spare.

Trudging along,
Paul

Viewing 1 replies (of 1 total)

shanebp
Moderator

@shanebp

8 years, 10 months ago

The first one refers to bbPress.
And can be difficult to track down. It may be in the bbPress plugin or another plugin that calls bPress .

2. Something, not BuddyPress, is creating a Widget using a deprecated constructor method.

3. Is related to a JetPack module.

The first step to getting rid of those Notices is identifying the source, so:
– switch momentarily to a WP theme like 2013 and see if any persist
– turn off plugins one at a time and see if any persist

Time consuming…

Viewing 1 replies (of 1 total)

The topic ‘troubleshooting the debug.log’ is closed to new replies.