Forum Replies Created
Here’s a really helpful guide to translating using poedit: http://urbangiraffe.com/articles/translating-wordpress-themes-and-plugins/
Count me in for some sort of get together. I’ll hold off on offering to buy a round until I know how many people are going to show up though – beer is expensive in NYC!
I’m sorry for the extremely unhelpful comment, but: I laughed out loud when I saw this topic’s title. “IE broke my CSS” would make a great t-shirt, or a band name.
tcesco, I recently ported over a version of the more general bbPress attachments plugin by _ck_: http://wordpress.org/extend/plugins/forum-attachments-for-buddypress/. The downside is that I haven’t yet gotten inline images to work, which means that people can upload and download images but they don’t appear as images in the posts (just downloadable file links). Thus it might not work for your purpose, but it’s worth a look.
Check out bp-core/bp-core-adminbar.php. The items in the admin bar are hooked to bp_adminbar_menus, and are ordered by the priority argument. So, for instance, if you want to put a button between the Blogs and Notifications menus, I’d write the button into a function called bp_adminbar_my_button, then use the hook
add_action( 'bp_adminbar_menus', 'bp_adminbar_my_button', 7 );.
Getting MediaWiki running together with WP/BP has two main parts: 1) sharing user login info and 2) theming them to look alike. http://dev.commons.gc.cuny.edu/2009/05/21/new-mediawiki-extension-wpmusinglesignon/ gives a method for (1). As for (2), you’re looking at lots of elbow grease
Very cool, Flynn. Thanks so much for sharing.
Hi snagfly. I’m the author of that plugin. It sounds like the problem is that you activated the bbPress trigger plugin inside of WordPress. As is stated in the readme files, this part of the plugin is only needed if you are running a separate installation of bbPress with BuddyPress 1.0.
If you are running BuddyPress 1.1+, you can safely delete the file bb-group-forum-subscription.php, keeping and activating only bp-group-forum-subscription.php.
Hi welshpixie – is there a chance you’re using More Privacy Options for WP? You might want to see the following http://buddypress.org/forums/topic/more-privacy-options-private-blogs-and-activity-streams
JJJ – I really like your modular way of thinking about how the forums could work with other parts of BP. It’s just hard to envision how, say, forums could be attached to an event, given the current dependence of forums on groups. Ideally (at least from this viewpoint) forums would be more of an independent, top-level component of BP, in the same way that a wire is (and in the same way that a wire can be placed on profiles, group pages, and so on).
@wordpressfan I think you might be right for some kinds of communities, but as the groups functionality of BP becomes richer (as it does with, for example, Andy’s new External Group Blogs plugin), the groups/forums distinction won’t seem so arbitrary. Forums then become just one of the ways that group members (ie people who share a common interest or purpose) can collaborate and communicate. But you’re right that right now there is little difference between a group and a forum, at least functionally speaking.
Excellent, Mike. Not only am I not offended, but I would love to see the improvements that you make to the email notification itself. It was (funnily enough!) one of the last things I did when I put together the plugin, so I didn’t feel like putting a lot of time into it. If you come up with something more flexible and/or better for a wider audience, I would love to have it, and with your permission patch the plugin.
Another idea is to have all non-group-specific forums belong to a sort of invisible, public group that everyone on the site is a member of. That way, anyone could post to the forum, and its topics would show up in the forum directory as you’d expect.
The trick would be to get that group not to appear on group directories, both public and individual, since the group would be nothing more than a shell for public forums and thus wouldn’t have any other content worth listing on people’s group and activity pages. It’d be easy enough to add a piece of metadata to each group that determined whether it should be listed in directories (independently of the public/private/hidden distinction). The problem is that groups are listed in lots of different places in BP, and you’d have to hijack each one of them in order to filter for this metadata. Such a plugin would be a pain to build and to maintain, I expect, as group lists are posted in more and different places throughout BP.
I’m glad you got it figured out. The reason I didn’t do this in the first place, though, is that BBDB_USER and those other global variables refer (if I’m not mistaken) to the bbPress db credentials, not the BP credentials that are necessary. If you’ve got the two installed in the same database, it’s not an issue and the globals will work. But I’m running bbPress and BP in separate DBs. $bb->user_bbdb_user and the like store the WP db info that the admin enters in the bbPress admin > WP integration settings.
So I guess all this is to say that I’m glad you got your situation figured out (I think I already said that ) but the very same solution might not work for all installations.
@Mike – Yes, I noticed the other day that Brent had posted the plugin, and I thought it was hilarious that we had come out with the plugins at almost the exact same time. Please feel free to pick apart my code, as I’m planning to do with your code in the near future, so that we can communicate about the best way to merge, or at least not unnecessarily duplicate work. I’ve got some ideas for making the plugin better in the future (daily digests in place of individual emails would be a big improvement but is probably pretty difficult) and we should definitely help each other!
Here’s what I think is going on. When you create a new topic, bbPress has to go to the BP tables to find out who’s in the topic’s group and then subscribe them to the new topic. It looks like I wrote the code with the assumption that your BP db is accessible by the same mysql user as your bbPress db. I guess that’s probably not the case in some situations. That could be the problem.
On the other hand, the fact that your error says “using password: NO” suggests that no password is being sent at all, i.e. that $bb->user_bbdb_password is coming up blank. I’m not sure what that’s about.
In either case, a quick workaround is to hardcode your bp mysql db username/pw into the plugin. In
$con = mysql_connect(“localhost”,$bb->user_bbdb_user,$bb->user_bbdb_password);
replace $bb->user_bbdb_user with the user and …password with the pw.
Hope that works.
I really need bbattachments for my BP community, and I’ve already started work on porting it over to BuddyPress. There are a few hurdles to overcome, but I don’t think it will take too much longer. I’ll post more when I’ve got something for others to test.
Tore, you can feel free to send me that $100 anytime
@r-a-y – Two great ideas. Next time I push out an update I will implement both. Maybe an admin option with checkboxes for where you want the subscribed/not-subscribed messages to appear (on the group home page or on the group forum index page or both). I might get to this next week – earlier if I find bugs and need to update anyway
Wow, I’m fast. New version of Group Forum Subscription that works with BP 1.1: http://wordpress.org/extend/plugins/group-forum-subscription-for-buddypress/installation/
Wow, Westpointer, we had the same idea at the same time. http://buddypress.org/forums/topic/group-forum-subscription
My version allows a bit more user control (opting out of specific discussions or entire groups) by using bbPress’s native Favorites function. I wonder if there’s some way you and I can combine forces
Hi cozzie. I’m not sure whether you’re still interested in a solution to this, but I just wrote a plugin that lets you select what you want the Groups and Members widgets’ default views to be. You can get it here http://dev.commons.gc.cuny.edu/2009/09/07/new-buddypress-plugin-enhanced-buddypress-widgets/
Hi Modemlooper – not sure whether you’re still interested in this, but I was looking to make a similar change (I wanted recently active members to show by default). I wrote a plugin to make it happen: http://dev.commons.gc.cuny.edu/2009/09/07/new-buddypress-plugin-enhanced-buddypress-widgets/. Hope it helps.
You’ve got to replace the whole line. (Or just back out !(int) at the beginning of the if statement and replace it with 1 >, which amounts to the same thing.) Let me know how it works.
@Flynn – Glad you got the single sign-on working! The visual integration really just came from an excessive amount of CSS elbow grease. I’m a bit embarrassed to say that our solution for sitewide navigation isn’t as elegant as yours – the WP nav is hardcoded into the MediaWiki template. We were in a rush to get the thing together (and frustrated with the less-than-ideal theming structure of MW!) and it never occurred to us. I’ll definitely look into using includes to make this work.
As for the activity plugin – it’s hard to know from just the blank screen just what’s wrong. If you’re getting the problem even without saving pages, then it’s unlikely that it’s a problem with the code (since it is only hooked when a wiki page save is complete). A couple possibilities:
- You might want to take a look to make sure that there is a close ?> in the MW extension. I had to leave it out of the MW documentation page because of the way the MW knowledgebase renders PHP (I guess?). If MW isn’t detecting an end to the extension, it could cause a panic.
- Where did you place the require_once line in your LocalSettings.php? My system was finicky; I only got the plugin to activate correctly when I made it the second to last require_once in the config file (just before the WP redirection extension code). So you might try playing around with the location of this file.
- Make sure as well that the line in LocalSettings.php is pointing to the right location – [MW-directory]/extensions/buddypress-activity/buddypress-activity.php, or whatever alternative location you’ve chosen on your system.
Hope that helps at least a little!
@Hempsworth – It’s funny that you mention the class=timesince – I must have spent three hours trying to get that to work one way or the other. The problem is that the timesince span tags are added in the individual BP components (groups, blogs, wire, etc). To get wiki functions to work the same way I would have to abandon the quick-n-dirty activity hack that I employed and actually build entire wiki BP classes. Maybe one day! In the meantime, you might try this even quicker-n-dirtier hack that I mention in the Usage section of the extension page. The preg_replace code I give there goes in BuddyPress core, around line 226 and 230 (ish) of [wp-install-directory]/wp-content/plugins/buddypress/bp-activity/bp-activity-templatetags.php. This hack will only apply to new wiki activity – not the stuff that you’ve already posted – so make sure to make a new wiki edit to test.
Glad the filter is useful to you!
I think the answer to your question is yes, John Smith’s profile would come up in that kind of scenario. The links that are created in BP profiles are merely full-text searches on all BP profiles (this is the link behavior out of the box, and my filters do not change this). Even if the name “Smith” in John’s profile doesn’t link to http://your-buddypress-url/members/?s=Smith, that search URL will still be live and accessible from the regular BP search box.
I haven’t looked into the details, but it should be possible to build a plugin that limits search in different ways. You might, for instance, search all profile fields except those that have been tagged as non-searchable (last name, for example). Another strategy: you might only return a hit on (for example) “Smith” if the result appears between anchor tags; in this way, non-linked profile fields would automatically be excluded. The first kind of solution is probably the better one, and I imagine it will be quite easy once field-specific profile search comes along in BP 1.3 http://buddypress.org/about/roadmap/