BuddyPress.org

Dbascent94-

Are you still having issues? A week ago you posted this:

I tried using the default themes and the same problem persists. I could really use a pointer on where to even begin looking for a fix for this

But you failed to tell us which version of BuddyPress you are running. Two weeks prior, you stated that:

I downgraded to RC1. I am going to wait for 1.0 and then try again.

Does your problem exist when using the public release version 1.0?

We don’t have sufficient information to beginning helping either of you. Please read this and post accordingly: https://buddypress.org/forums/topic.php?id=2674

Log into WPMU backend as site admin. Go to Appearances > Plugins. The version of all your plugins, including BuddyPress, is displayed there.

Here’s the versioning info you should see with regards to the BuddyPress plugin:

For BP public release version 1.0 –> 1.0

For BP RC2 –> 1.0-RC2

For BP RC1 –> each individual BP component will show up as it’s own plugin.

As of r1303, which is where RC2 started I believe, BuddyPress was turned into one, big plugin suite.

in the bp-core.php if i’m not wrong, at the top of the file the version is displayed another way is wp-admin ->site admin -> buddypress, look at the bottom of the page, it should be displayed

If you’re still having this issue, you need to remove as many variables as possible. Since you are using a custom theme and a number of 3rd-party plugins, this is where you should focus your efforts.

Before starting this process, make a backup of your MySQL DB just in case. Also, it is advisable that you back up all your custom themes and 3rd-party plugin files just in case you make some major mistake.

Now, switch to the standard themes that come with BuddyPress. Try creating a group again. If the problem appears to be resolved, switch back to your custom themes and try creating a group again. If the problem returns, contact the theme designer.

Next, assuming the problem still exists with the standard BuddyPress themes, you should deactivate your 3rd-party plugins one at a time. Deactivate just one, try creating a group again. If the problem still exists, then deactivate another 3rd-party plugin. Keep doing this until either the problem goes away, or all 3rd-party plugins are deactivated. You can also go about this the other way: deactivate all plugins except BP and then reactivate one at a time, checking to see if the issue occurs again with each new reactivation.

If you find that the problem goes away after a particular 3rd-party plugin is deactivated, then you may have found the culprit. Contact the developer of that plugin and ask for advice.

Please report the results back in this thread.

@Scotm, Am interested in that also integrating P2 theme with this twitter plugin.

& tweet from wire!

This is actually a WPMU question, but I think you should find an answer here: https://buddypress.org/forums/topic.php?id=2042

I installed 1.0 from the download link.

Changed the slugs: BP_GROUPS_SLUG, BP_MEMBERS_SLUG, BP_FRIENDS_SLUG, BP_WIRE_SLUG

Applied wire_patch_three.patch

Works for me. I logged in to your site and noticed that this line wasn’t changed which is the problem:

Line 368, in bp-wire/bp-wire-templatetags.php

return apply_filters( 'bp_get_wire_delete_link',

'<a href="' . wp_nonce_url( site_url( $bp->groups->slug . '/' . $uri . '/' .

$bp->wire->slug . '/delete/' . $wire_posts_template->wire_post->id ),

'bp_wire_delete_link' ) . '">[' . __('Delete', 'buddypress') . ']</a>' );

Your install still says ‘wire’ in the delete url instead of ‘pinnwand’. Looks like the patch wasn’t fully installed? This is on: http://sven-lehnert.de/

Change line 368 to be $bp->wire->slug instead of $bp->{$bp->current_component}->slug and it’ll work. See the difference in the two lines here: https://trac.buddypress.org/attachment/ticket/723/wire_patch_three.patch

i like the caching mechanism inclusion, better will be if it will be cached with the built in system wp_cache_set & family

Shakera-

If I understand your issue, you are having problems localizing BuddyPress into Cyrillic.

Please check this BuddyPress codex page first as there is a translation of BP for Bulgarian.

If you are making your own translation, then you should read the Translating WordPress codex page.

Kunal17,

Is there anything else in your “bp-custom” file? Also make sure there are no spaces before and after the opening and closing <?php> tags.

Could you post the entire contents of the “bp-custom” file to http://buddypress.pastebin.com/ so we can look at it?

sounds awesome! will this be integrated into the buddpress status updates that will be incorporated soon?

The core Buddypress files do not live in /mu-plugins/ anymore. They should be in /plugins/ instead. If the location of BuddyPress is hardcoded into the Toksta chat plugin, then that is the problem.

Contact the Toksta chat developers and ask them to update their plugin to the proper path–and not via a hardcoded path.

I’m excited about this, its almost exactly what i was looking for…

I would however really like to see tweet by wire integration (perhaps a small check box that says tweet this)

Without knowing the details, it would be nice if you could somehow ‘pull’ the post form into a custom home theme in BP. This way users could seamlessly cross-post to Twitter from the home page using one form. I’m using P2 theme as my home theme so the need is obvious, but perhaps this could be possible somehow.

Regardless, very happy to hear this is coming soon.

Evvscuba–

Here are a few thoughts:

1. Do a test with your users by switching to the standard BuddyPress themes. If the problem goes away, then it’s most likely a theme issue.
2. Make sure that your users are uploading avatar files with sufficient dimensions. At a minimum, each dimension needs to be at least 150 pixels.
3. Upgrade your version of GD. It is a little outdated. There may have been some browser-related bug fixes since your version (note: I’m just suggesting that possibility; I have not verified this though). The current, stable version is 2.0.35
4. Finally, contact Sgrunt, the desinger of Facebuddy, and ask for his advice. He may be aware of an issue with IE 6 & 7. If he is not aware of your partciluar issue, he most likley will appreciate you keeping him in the loop–wether or not this particular issue has anything to do with his custom theme. Share with him the results of the above steps.

RC means release candidates and it’s a programming term for referring to specific pre-release versions of software. Buddypress has had 2 so far – RC1 and RC2.

On a similar vein, most programmers use something known as a revision control repository throughout development, primarily for easy access to previous versions (“commits” in this context) of software. One of the advantages of this is that it saves duplicating a folder on your computer each time you make progress. Each commit will have a version or release number. Imagine having 1303 folders on your hard drive with only slight differences between them.

As far as we are concerned here, RC1, RC2 and rXXXX (where X are numbers) refer to a particular snapshot or version. Now Buddypress has had it’s version 1.0 release, every live website ought to be running version 1.0.

Rules of thumb: any BP-specific plugins ought to run on v1.0. Any theme that says RC1, though, probably WON’T run on v1.0. There is probably a lot of tutorials etc that refer to a specific release number (like r1303 in your example). That’s just the nature of ongoing development – documentation is prone to getting out of date easily.

If you’re trying to follow some specific instructions and get stuck, just post here and we’ll help.

Very interesting video and article Burt. Thanks.

My problem during last installation with bbpress alpha 6 and buddypress 1 was that all users in bbpress were set to ‘inactive’ and only bbress admin could post on bbpress via buddypress group forum – so it’s another thing to check out if you run into problems with integration…

@Timschmi

As stated above, a blog is typically more personal… written by one person. A Wiki is the opposite. The whole point of a Wiki is group collaboration… group being the key word. So within an organization, you may have a Management group, an IT group, a Training group… etc… and they would all have their own documentation to manage and collaborate on. So to me… Wiki’s within a group just make sense. Right now, the only thing you can share within a BuddyPress group is chat on the wire. But within an organization (for instance)… groups have much greater needs that that.

In case you couldn’t tell… I’m hoping to use BP someday as an Intranet… which to me means social networking + collaboration and document sharing. BP 1.0 has the social networking aspect nailed right now. It’s VERY nice. So sweet. I just hope it takes off and developers start getting on board to extend it.

p.s. I like the Elgg approach of having Wiki’s and Files within groups but also allowing you to browse *ALL* Wikis and Files on the site… so you don’t have to get to them from the group.