BuddyPress.org

These are the supported languages:

http://alexgorbatchev.com/wiki/SyntaxHighlighter:Brushes

The issue was initially presented as a well-defined problem:

BuddyPress developers need a common place to share code snippets

Now, the conversation has transformed into a bigger-picture discussion. That is always good in my mind.

Burt and Andy bring up valuable points. As Burt points out, we are on the verge of something interesting. We have an opportunity to use the social-networking tools of BuddyPress to create something unique and wonderful in the developer community. Andy offers very specific, compelling reasons on why and how we should indeed use those tools.

So, I propose that we need to reframe the originally-stated issue like this:

What is the best way for BuddyPress developers to leverage the power of BuddyPress to create a vibrant, useful developer resource?

@Stefk, try Burtadsit’s solution.

Private members and groups sections should be a core feature of Buddypress imho.

I’ll reply to the name issue here also. The group names and descriptions can be arbitrarily long and can trash the theme layout in bbpress. These are two different software packages Elody and I chose to be as minimally invasive as possible. I left the forum name and description up to the bbpress/wpmu admin’s discretion.

I didn’t think that a site admin would be too happy to have the theme broken by a long group name.

I included a way out also. The name and description of the group are pulled over to bbpress and are available as template tags for you to use.

oci_group_name()

oci_group_description()

It would make sense to have a searchable blog for such code snippet creations. The restrictions on proper searching in bbPress makes it difficult to find things. I get better results searching google to find things I know exist in these forums. That is where a blog would be way better

Trent

From the forums installation-readme.txt:

11. Enable user switching in bbPress by copying the following line of code into your bbPress

bb-config.php file:

$bb->bb_xmlrpc_allow_user_switching = true;

Needs to be in your bb-config.php

A helpful topic here: https://buddypress.org/forums/topic.php?id=471

I too am in favor of the “another blog on this site” option.

Having thought about it more – my vote would be another blog on this site.

For a few reasons:

1. People can use the same login, and therefore comment without being spammed or moderated.

2. We can promote regular BuddyPress community members to \”snippit creator\” status.

3. We can track all the snippets in activity streams.

4. We get nice buddypress.org permalinks for every snippet.

5. RSS.

Mascix, this is really a WPMU question. I suggest searching the WPMU forums and if you can’t find the answer, then start a new thread there.

DJPaul-

Just a couple quick thoughts specific to BuddyPress:

1. Has x number of friends. Triggered at each admin-set interval such as 25, 50, 100.

2. Has joined x number of groups.

3. Has started x number of groups.

4. Has contributed x number of group wires

Each of these are basically milestones that could be set in the backend. As each milestone (achievement) is reached, a new icon could be displayed in the user’s profile.

Nothing fancy. Just quick ideas.

Having problems uploading an avatar? Do they turn black? Do they not show up at all? Does the cropping tool malfunction?

https://buddypress.org/forums/topic.php?id=302#post-1212

https://buddypress.org/forums/topic.php?id=1960#post-10404

Some good advice on how to change blogs.dir directory permissions: https://buddypress.org/forums/topic.php?id=1153

Here is a rule of thumb. You do not want to try uploading too big or too small of an avatar file. By default, BuddyPress sets the small avatar at 50 by 50 and the large avatar at 150 by 150. So, if your source image is smaller than 150 on at least one of its dimensions, you could have issues with creating the large avatar. If it is smaller than 50 on at least one of its dimensions, you could have issues with creating the small and large avatar.

Finally, if you are still having issues after following the linked advice, you may have a WPMU plugin conflict–especially if you are using any plugins for image manipulation or display. Here is a list of plugins that can cause conflicts that users have reported to date:

1. NextGen Gallery
2. WP-cycle
3. lightbox
4. Dynamic Content Gallery

To figure out if you have plugin issues, follow the standard WPMU protocol for determining plugin conflicts.

Oh. bin.buddypress.org of course.

EDIT: I said that with just a knee jerk reaction. Kind of a ‘not invented here’ thing. Now that I’ve had time to think why, I realize it’s because we do need to control it. In case nobody has noticed, we’re have the opportunity to *not* follow the rules for technical support and software development. The nature of buddypress, it’s social nature, gives us the opportunity to invent something truly different and useful.

Don’t ask me yet what that is yet but signs of it are beginning to appear.

Complaints about the bp.org group forums not being live yet. They aren’t just complaints. They seem to be us, struggling to accomplish something in a certain manner and knowing that the tools are dangling before us.

We’re discussing code collaboration, commenting, sharing solutions to user problems and questions. Solving things in front of people. How best to accomplish that with code paste bins.

Suggestions and approval of a ‘technical blog’ that will show people, by example, how to do things.

It’s like we’re all suffering some vague malaise and we sense where to find the remedy.

I agree. A technical blog is different than a codex page is different than a code snippet. I like the idea of using whichever makes the most sense. I also think a dev group forum would be very useful.

However, I believe we are specifically talking here about where to host a code snippet library.

I didn’t know we were being graded. Is there a curve? Seriously though. I see value to each approach. We’ll probably wind up using a combination of some if not all.

Burt, there is no all of the above on this test

Thanks Lance. Nice job.

I don’t like idea of permanently using outside paste bins right off the bat for the reasons you outlined. We’re already using them from time to time for temporary things. It’s just that, transient and temporary. I do like the idea of stuffing code on one for sharing and collaborating. Forums and blogs seem to hate code. A paste bin has lovely things like line numbers and syntax hilighting. Isn’t there a code editor built into wp itself? The regular one. I’ve never seen it since I’ve only worked with wpmu where it’s insanity to hand over the source code to a theme to all blog admins and give them a ‘save’ button.

I think the Codex pages should be sources of documentation and education not guides to implementation. That little tutorial I wrote today outlining how to mod the admin bar would be better suited as a blog post on that tech blog you mentioned.

I completely agree about the new FAQ sticky forum post. It only really solves my frustration at having to hunt the damn things down all the time.

A bp group forum like the one that exists would be an asset once Andy fires up the actual group forums. One problem/solution one thread.

So, it looks like I’m voting for all of the above.

Lance, thanks for doing this!

I prefer option three (3), the self-hosted code snippet library. I agree with your assessment of the benefits of controlling our own snippet repo. Also, I think that we should use pastebin.com since, like WordPress, it is licensed under GPL.

i noticed that when a user signs out and the “log out” is showing nothing happens when they click it…. you have to refresh teh page and have the “logout of facebook” showing for taht to work… i think its the same issue if they attempt to logout using the usual buddypress logouts