BuddyPress.org

Thanks for the report. Is this true across all browsers?

I had the same exact problem. I had updated it via WordPress from BPGES ver. 2.8.5 (on BP 1.2., and I got the same exact result as Pisanojm. However, a clean install of the plugin seems to have fixed it. I haven’t really had a chance to test it on a live server yet, but everything appears normal on my test server.

I still have the old folder zipped and tucked away in case anybody wants to take a look at it.

Not at all, will fire it your way now.

@Pisanojm and @boonebgorges

It seems I spoke too soon. It turns out that, even with the clean install, the plug-in would load inconsistently. How I found this was, when I refreshed the screen and things went haywire again; but then after several refreshes it would go back to normal. My thoughts were that perhaps the plugin wasn’t consistently loading for some reason.

I tried something that appears to have “fixed” it, but I’m still too green to really know for sure. Here’s my “solution” @Pisanojm Let me know if it helps or makes matters worse (it appears to have worked for me):

In the file named bp-activity-subscription-main.php (which can be found in the plugin’s folder) at the very end of the file, you’ll find the following function:
`function ass_activate_extension() {
$extension = new Group_Activity_Subscription;
add_action( “wp”, array( &$extension, “_register” ), 2 );
}`

Add the following line to it so it looks like this

`function ass_activate_extension() {
$extension = new Group_Activity_Subscription;
add_action( “wp”, array( &$extension, “_register” ), 2 );
}
add_action( ‘init’, ‘ass_activate_extension’ );`

That appears to have fixed things on my end, let me know if it helps. For the record I copied that off of a previous version of the plugin which I had installed. I’ve already emailed @boonebgorges about this so we’ll see what he makes of this.

@menelik Thanks a million for looking into this.

You’re right that your solution will probably work. But the reason why it’s necessary is because of a small typo. The `add_action()` line that you suggest is actually in the plugin file, near the top, but it’s only fired conditionally based on a version check. But I was doing the version check slightly wrong, which made it fail. Oops

In any case, it should be fixed in 2.9.1. Thanks again for your vigilant testing!