In continuation of this, I ran into a fatal error on the buddypress settings page in the admin area.
Fatal error: Call to undefined function bp_core_get_buddypress_themes() in /customers/xevodesign.nl/xevodesign.nl/httpd.www/talkmore/wp-content/plugins/buddypress/bp-core/bp-core-admin.php on line 105
Edit: Nevermind, using “define ( ‘BP_IGNORE_DEPRECATED’, true );” in your wp-config isn’t allowed apparently..
Hehe, das toevallig, ben ook pas net klaar met het vertalen van buddypress naar Nederlands, het ziet er naar uit dat niet alles is vertaald bij je site?
hi
It is working.may be it was a temporary problem.Try again,hopefully it should work for you too.
So, what will we look for when trying to find the code for the dozens of widgets?
Welcome back!
Eager to test, and help out where needed,
-n
That was on big pile of bills! 
Welcome back.
Quoting Gpo1: “@M, Please can you extend your twitter plugin with a page for user’s followers tweets & avatar? ”
@Gpo1: I probably could, but the plugin is not meant to entirely replace Twitter, it’s meant to offer a reasonable amount of interactivity with Twitter.
Funny how bills can take a person away from writing free code 
Sorry for the delays…
Basic chat works. Group chat is more complicated if one wants to really support anything other than a tiny community without driving a database server into the group with loads of queries per second. So we’re working on that and having some success. I guess a few of you had a chance to demo that aspect while I was online testing it
No ETA on a release date…
Funny how bills can take a person away from writing free code
Sorry for the delays…
I think you’re over-thinking this a little bit.
bp-default assumes that it is the “home” template, and nothing more. It assumes that user blogs will use other templates that you either create yourself, supply to them, or that they can install via the Appearance item in the site admin.
The only way to trick this into working is by putting…
define( 'BP_ENABLE_MULTIBLOG', true )
…either in wp-config.php or /wp-content/plugins/bp-custom.php. This still probably isn’t really what you’re trying to do, but it will get you where you want to be without modifying the core templates. If you’re using a custom template, then it’s as easy as modifying the header.php to always link back to the root blog components and pages that you want it to.
BTW, although my first post mentioned that I must have made a change that caused the links to “break,” it was a new site so I was *assuming* that the links must have worked originally and so I thought I must have made a change to themes (or something else) that caused the problem.
However, since I subsequently saw the same behavior with a completely fresh install (starting with no database and an empty public_http directory, I’m now thinking that those particular BuddyPress links were probably never working.
At that point I really think this sounds like some kind of conflicting JavaScript issue. This cropper is solid because it’s the same library used by WordPress 2.9’s image cropping feature, and I think it’s even the same one that Gravatar uses ( which fits the roadmap ability of being able to import a gravatar via the BuddyPress interface. )
Check if any other plugins are adding conflicting JavaScript, and see if there are any errors occurring in your site.
Update. By comparing my site’s BuddyPress-generated tabbed links “Blog”, “Members”, “Groups”, “Forums”, and “Blogs” to those for other sites, I was able to pin-down specifically what was wrong—but don’t know the fix.
My main blog structure was such that the main blog was at:
http://mysite.com
…and a member blog would be at:
http://mystite.com/memberblog
All the aforementioned BuddyPress-generated tabbed links “Blog”, “Members”, “Groups”, “Forums”, and “Blogs” were failing because the links specifically for the memberblog because “/memberblog” was being added to each of those links (if I removed the “/memberblog” part of the links then the links would go to the right place).
I tried everything I could think of to solve the problem (code reinstalls, database deleting and reinstallation, removing all plug-ins, etc), and *nothing* fixed the problem.
Interestingly, when I finally tried reinstalling using the http://memberblog.mysite.com site structure, those various memberblog Buddypress tabbed linked worked just fine.
Is it possible that BuddyPress has a bug specifically for that mysite.com/memberblog structure?
I’m going to stick with the memberblog.mysite.com structure because I don’t have currently have the coding experience to get into addressing the issue, and I’m happy enough with the subdomain approach in any case. I just wanted to let folks know that there might be a problem… or perhaps somehow it is something particular to my setup—although everything else worked just fine.
Just tagged version 0.1.3
* Fixed bug where Comments was not showing up in link list nav bar
* Many l10n fixes, big props to Chouf1
* Added support to control voting behavior with config constants and filters
* Added Spanish translations, props to laloma
* Improved Fotoglif support due to changes to their API
The first time you upgraded BP from 1.0.3 to 1.1.2, did you manually upgrade or use the automatic upgrade feature of WordPress?
What I would recommend is trying this:
- Make a backup copy of your DB if you have any data worth saving
- Make a backup copy of your bb-config.php file-assuming that you had forums integrated before
- Deactivate all non-BP plugins
- Deactivate BP
- Delete the old BP files located in the /buddypress/ directory
- Temporarily remove all plugins from /plugins/–copy them to a temp folder outside your install
- Manually upload a fresh copy of BP 1.1.2 and move the contents of /buddypress/bp-themes/ into their proper place
- Remove your /wp-content/bp-themes/ directory–assuming that you have moved it back into place since your last post
- Reactivate BP
- If no error, choose and activate the new default BP theme
Does BuddyPress version 1.1.2 now work? If so, add back your other plugins and activate them.
you can give me that link, i’m ready to release a dozen of widgets and plugins in the next days, and would be ok to support that one as well… i’ll check the code before release and apply credits for the work done.
@casualgamesfrance
Thanks for your help! Your code works for all the tags given, but not for the images 
The correct code for inserting a picture is put in the database (without escape character for the quote). But when I look into the fora I can’t see a picture, because In the code of that page, there’s put an escape character before the quote’s.
I removed the add_filter( ‘bp_get_the_topic_post_content’, ‘wp_filter_kses’, 1 ); in /wp-content/plugins/buddypress/forums/bp-forums-filters.php and this solved the problem!!
The next step is to remove this filter in your custom.php file so I can leave buddypress as it is.
Thanks a lot!!
5283373Inactive
My Buddypress community (4500 members!) is asking for images for month now.
I patched BP with a filter to allow HTML tags in forums, and they use image hosting services, but with a lot of pain!
Native images capability in BP would make BP the best platform ever!
I figured out the problem, it was not with buddypress but had to do with another jQuery item I had in the header.php. I figured it out and we’re good to go.
Thanks for all your help guys, I really appreciate it!!!
I actually have (unofficially and without asking) updated this plugin for my personal site only and it works as far as I tested it. I don’t mind making that available, but have no interest to offer any tech support whatsoever, neither to adopt this plugin.
I am merely saying that if anyone is looking to mess with this plugin in BP 1.1.X to let me know and I can send you a link. I don’t see any reason for leg work to update this plugin should be done twice, but don’t expect support in any form.
It is a shame that Burt has dropped of the radar recently as he did an incredible job with this plugin. In fact I would assume with the quality of his plugin that Andy could easily take his work and make it into core. Otherwise I hope he will come back soon.
Agreed, the lack of images in the activity stream, wire and forums is driving me bonkers as well.
As far as I can tell, there is only a handful of capable developers here. Themers more so, but the availability of people that code this are very limited. Unfortunately these requests seem to fall on deaf ears.
In that sense BuddyPress is not even close to being a real contender amongst other social open source packages. I hate to say it, but it is true.
On the flipside, BP is young and a lot could happen in year. Somehow though this feature has never been able to be made a priority. Which is a shame, since with thousands of users generating pages full of text is just plain boring.
I love BuddyPress, but definitely feel your pain.
Thanks for all your guys help, I appreciate the fast responses to my post. If you find a fix please let me know!
Manoj – I understand what you are saying, but I need a fix so users do not have to do this. If every user that experiences this problem has to do this, then that will cause the site not to be user friendly and it would not be a real fix. There has to be a hack for the js. I appreciate the advice though, thank you!
Haven’t tested it myself, but something like this usually is easier on the brain…
<a href="<?php echo loggedin_user->domain . $bp->friends->slug . '/remove-friend/' . $potential_friend_id, 'friends_remove_friend' ) ?>" title="<?php _e('Cancel Friendship', 'buddypress') ?>" id="friend-<?php echo $potential_friend_id ?>" rel="remove" class="confirm remove"><?php _e('Disconnect', 'buddypress') ?></a>
It’s also possible that because this specific link has ajax attached to it, that it’s returning false before the additional JS message can fire on the click. In that case we’ll need to try a different route.
I re-read that page, but I don’t see anything that addressed my issue. I’ve disabled all other plugins (even though they didn’t have buddypress dependencies and I’m just trying to re-activate the plugin.
Looks to me like IE8 thinks jQuery library didn’t get included. Either that or it’s having a hard time seeing that “j” is jQuery. I’ll try to take a look at this soon.
