BuddyPress incompatibility

Hi Herbovec,

I’ve not explicitly tested BTF with Buddypress.
It sound’s like buddypress is highjacking WordPress cores $query->is_main_query() causing an issue with BTFs conditional checks.

you’ve not provided the whole debug entry tho. What file is this occurring in and on which line? It’s possible I can add support for Buddypress simply by checking for it and using it’s functions instead but I need to know a bit more ??

Hi.

Looking at your automagic_insertion method — assuming that’s where the error is coming from, we can’t see the whole backtrace so I can only guess — you have this hooked to loop_start. For some legacy reason, BuddyPress calls that action in two places (one is in its BP_Groups_Group_Members_Template class, the other is in the BP_Groups_Invite_Template class).

This unfortunately dates back to about 7 years ago, so I can’t say why the original BuddyPress developer decided to use these. I’ll create a BuddyPress trac issue to see about getting these changed, but at the earliest, the next release wouldn’t come out until October 12.

BuddyPress trac issue created @ https://buddypress.trac.www.ads-software.com/ticket/7247#ticket

Hi Paul,

Thanks for chiming in so fast! Seems the updated forums are a bit better for collaboration than previously ??

Hopefully we’ll see a fix coming in October then.
In the meantime Herbovec you can avoid using the automagic method and manually add the filter using either the do_action hook or the provided widget (if there’s a widget area that would work for you).

Happy to help. You’d actually be surprised how infrequently people mention “BuddyPress” on this forum — I set my email profile up to get email alerts for it, and most come from the Theme Review team area.

Thanks a lot for your quick responses. Here is the result of turning debugging on in WP:

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 /srv/www/radius.philo.at/html/wp-includes/functions.php on line 3995

Notice: bp_setup_current_user was called incorrectly. The current user is being initialized without using $wp->init(). === Trace: #6 /srv/www/radius.philo.at/html/wp-content/plugins/podlove-podcasting-plugin-for-wordpress/includes/modules.php(19): Podlove\Modules\Logging\Logging->load() #7 /srv/www/radius.philo.at/html/wp-includes/plugin.php(524): {closure}(”) #8 /srv/www/radius.philo.at/html/wp-settings.php(295): do_action(‘plugins_loaded’) #9 /srv/www/radius.philo.at/html/wp-config.php(89): require_once(‘/srv/www/radius…’) #10 /srv/www/radius.philo.at/html/wp-load.php(39): require_once(‘/srv/www/radius…’) #11 /srv/www/radius.philo.at/html/wp-blog-header.php(13): require_once(‘/srv/www/radius…’) #12 /srv/www/radius.philo.at/html/index.php(17): require(‘/srv/www/radius…’) #13 {main} === Please see Debugging in WordPress for more information. (This message was added in version 1.7.) in /srv/www/radius.philo.at/html/wp-includes/functions.php on line 3995

In the meantime I checked: the problem does not depend on a particular theme. The widget solution enables group views in Midori, but neither in Chromium, nor Firefox (in Kubuntu). Chrome in MS Windows also works. So this is quite uneven.

Best,

h.h.

• This reply was modified 8 years, 2 months ago by herbovec.

Those other messages come from the podlove-podcasting-plugin-for-wordpress plugin calling some code too early. Other than representative of probably doing something wrong, it doesn’t cause problems most of the time, so you can disable the debugging again and ignore those.

The loop_start/end name clashes has been fixed in https://buddypress.trac.www.ads-software.com/changeset/11083/ due for BuddyPress 2.7 this October.

Fantastic. Thank you Paul for quick help ?? With that both BTF and Buddypress become a bit better.