BuddyPress.org

That happened on my site too – but I thought this was related to a Fatal Error I had with a key plugin. So maybe the two issues were separate….hmmm…..

yeah, the main Blog and the user-Blogs diappeared……at least the Blog-Listing at the Blogs-directory (using WPMU).
@andy @jjj could you please check

I can confirm that blogs are missing after upgrading to BP 1.2.4 on a WPMU 2.9.2 install.

Why dont you make your own directory?

Might I suggest tag BP plugins as “buddypress-extend” or “bp-extension” plus “buddypress” just to make the distinction that that the plugin is bp-dependent as opposed to just being bp-friendly.

After the upgrade I can not see blog?

Upgraded from BP 1.2.3 to 1.2.4 (automotic upgrade) – my blogs directory is empty – “Sorry no blogs found) – Main menu blogs item.

Using WPMu 2.9.2 & default BP Theme. (I’ve removed all BP Related plugins & BP is only active plugin. Also deactivated/reactivated theme)

@arxpoetica et al –

I just created the private BP group Semantic Web and Open Stack Integration to focus our discussions. As it is a private group, you must request membership. I felt it was better to create a private group so that we could ensure the conversations are maintained at the proper level.

since there is attention on the extend section – i noticed the “last updated” is off by 15 hours. on one i just updated: “Last Update: 15 hours ago”

@jeffsayre — i trust and get your concern w/ openid. That said, it’s hard to stop a moving train. I just don’t want to completely disregard all the motion going on elsewhere. So call me the healthy skeptic in the room — that should be a good thing, right? It just means that as we move forward you’ll have someone voicing alternate points of view. But I’m still on board to make *something* happen. (Btw, Chris link works for me. Maybe the site was just having a bad day :p ).

Have we set up an actual group for this? I think that might be a good place to start.

Is there anybody who will fix it for $$$?

I have the same problem and I am still looking for somebody to fix it… even for cash..

It is, that was posted after it. There’s nothing stopping you creating tickets with a 1.0 milestone (other than angry admins!)

is BP 1.2.4 already released ?
…… as there is still one ticket open in TRAC:

https://trac.buddypress.org/ticket/2398

@DJPaul

That is a good point. However, since BP.org is currently pulling in all plugins that include the “buddypress” tag, there is not much we can do. If we had a BP.org plugin and theme moderator, that would be different!

@JeffSayre, maybe that can be handled somehow by BP? Add a hook that will deactivate all the BP plugins and then ask to reactivate them manually by admin?

Also, I suggest changing the subject of the topic, since it’s not relevant and people can get confused (I felt like that after reading it)

Thanks.

One could argue that plugins that provide a new widget could be tagged buddypress as they don’t break BuddyPress, per se. Jeff, I don’t think asking people to use a different tag for BuddyPress compatibility will work, people won’t change what they know.

The page will turn into junk unless there is some degree of oversight applied to the plugins listed.

You must always deactivate any BuddyPress-specific plugins before upgrading or reinstalling BuddyPress. That is why your first attempt failed. Moving your plugins outside of the /plugins directory basically accomplished that for you.

https://codex.buddypress.org/getting-started/upgrading-from-10x/

From that Codex article:

“…it’s a good idea to disable other BuddyPress plugins first of all”

Since BP 1.2, all BP-dependent plugins should have code that will prevent them from firing if BP is not activated. However, some plugin devs have not added that coding to their plugin so you can have issues.

@dancole

It depends on your definition of “near future”. Since all authentication is handled by WordPress, not BuddyPress, this project is truly a WordPress-specific feature. We are forming a group to work on this issue and also discuss the possibilities of implementing Semantic Web and / or Open Stack protocols in BuddyPress.

But, this will not be a core WP feature–at least not in the near term. I imagine that we will let the WP 3.0 series work out any new issues once that series is released. So, sometime around the WP 3.1 or 3.2 public release might be a reasonable target for releasing a WebID plugin for WP.

Do you have any specific interest and / or experience with WebIDs?

The real issue is that any plugin in the WP Plugin Repo that is tagged “buddypress” is automatically listed in BP.org’s Extend Section. So, any plugin dev that uses that tag will have their work listed.

We could request that plugin devs use the tag “buddypress-compatible”, instead of “buddypress”, when tagging plugins that are not dependent on BP but can run under BP. This way, only those plugins that are truly BuddyPress specific (dependent) will be listed in the BP.org Extend Section. Of course, it would be up to each plugin dev to honor that request.

I’ll have to go back and rename some of my plugins, if this happens. There’s got to be a better way. Maybe sortabllity by rating or popularity as determined by bp.org users, which would filter out the irrelevant stuff.

Hey Mike, somewhere around the end of this video (http://m.podshow.com/media/25237/episodes/228148/dcmtvipod-228148-04-26-2010.mp4) you said that an events component is being developed which is going to be fabulous. Were you talking about bp-events?