[@johnjamesjacoby Keymaster 16 years, 9 months ago]

If you want the theme that is on testbp.org, that’s the included bp-default theme with BuddyPress 1.2.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

Since you’re using the old BuddyPress 1.1.3 themes, you will either need to use the BuddyPress Backwards Compatibility plugin, or update your theme to use bp-classic instead.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

The answer is not to use the bp-default theme anymore.

Switch to bp-classic or your own theme, and you’ll be back to normal.

The purpose of BP out of the box, is to provide you with everything you need to make a social network, including the theme to do it. If you haven’t been making your theme a child of bp-sn-parent, or you made your own custom theme, then you’re on your own as a developer to fill the gaps in your custom theme.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

Make a ticket in the trac with your suggestions? Your contributions could make it into the core. There are a few places where queries could probably be reduced.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

The backpat plugin is only going to support the 1.1 branch of code, and not the dual theme massive integration headache that came before it.

To have the activity stream update when you post a topic or post a reply, bbPress would need a special plugin to be made, and/or bbPress would need to be “deeply” integrated with WordPress/BuddyPress to have those functions natively available.

The other thing you could do is look into previous versions of BuddyPress that included that kind of support. In BP 1.0 it was assumed that if you wanted forums, that you were using the voo-doo magic method of integrating things.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

No. That tab is only for incoming friendship requests that need your attention to accept or reject.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

@katendarcy

This plugin doesn’t perform logic searches within fields, but it does allow you to search for criteria in any xprofile field and any combination of them (except checkboxes at the moment.)

@michaelesenwasser, not yet that I know of.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

@mlemberg

If what you want to do is translate and/or localize the text of each component, there are a few posts regarding how to do that already.

Can you point me to where things aren’t localized? There were a few places in 1.1 that have been patched in 1.1.3, and 1.2 should be pretty solid in this regard.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

@arturo

Make a note of multi-language on http://bpdevel.wordpress.com/ and we can talk about it during this coming weeks’ dev chat. It’s something I’d like to see also, even if it’s just something as simple as selecting your language in the settings screen. I’ve had a much more complex version of this running locally for a while now, so I’ll probably simplify it and patch it for Andy to look at soon.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

@davidlewis

Funny you say that, because I’ve had two totally unrelated client sites that said the exact opposite. They were confused about the private message setup, and when they saw the persons name prepoulated as a link, they clicked that link to that person every time, went to their profile again, assumed private messages didn’t work, and complained. Strange how the world works eh?

Because Twitter has owned the @reply idea, if ours doesn’t work similar, it probably won’t work at all. Same with hashtags. All a hashtag is, is a tag to search through streams by. It’s like tagging activity, which can be done via a plugin now that there’s activity meta.

Right now the only place and the only time the @name works, is when you’re updating your status to directly mention specific users. That kind of makes it a technology that won’t get used too often. There is also only 1 place to automatically populate that users @name in the update box, and that’s when you’re viewing their profile already. Twitter makes the activity stream the central source for all things activity, including @ing people back and forth. Maybe if user names in the activity_content were all given a specific class we could use some jQuery to turn that class into a link that auto-populates the update box instead of making it a link to their profile? That would help fully endorse the @name idea in multiple places, rather than just 1.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

@mikepratt

I think you bring up some good points about how @’ing someone, where it appears, and how you’re told someone @’ed you can start to be a run around. It’s possible that it could start to be a lot of back and forth, and if you’re not familiar with the concept of what it means or how it works, then there could be more of a learning curve than just typing in a box and hitting send.

Personally, I think sending a public message to someone and having it also updating your current status could be confusing, especially since writing a new blog post, or commenting on an activity stream item don’t update your current status. And if your new status contains an @reply, the link under your username in your profile gets stripped. Twitter has also partly trained me now that clicking on someones @name doesn’t bring me to their profile, it just sets up a reply to that person right away. I also think @replies should work in activity stream comments, instead of just the status update.

The username thing is hard to get around. The problem comes from peoples display names being editable and dynamic. You could, if you were really concerned about the display of things, filter the output of the activity stream item and use a little PHP creativity to replace the username with the display name. I’ve done this already to get rid of the · on a client site, because their activity stream links are setup differently and the ·s don’t make sense where they are.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

The usage of @ may have been a twitter hack, but it came from using it as a way to acknowledge or direct a comment at a user when a threaded option wasn’t available. We use it even here in these very forums quite often, because we can’t directly reply to one another.

Deprecated code, the wire, and the status update components are totally removed from the BuddyPress 1.2 core and will be available in a separate BuddyPress Backwards Compatibility plugin. If you desire to use those components, or are using a custom theme that uses old function names or loops, you will be required to install and activate this additional plugin to continue to use your old code.

This was done for three reasons:

1. Reduce the amount of legacy code in the core that is just hanging around not being used

2. Not give new comers 2 (or more) ways to do the same one thing

3. Influence plugin and theme developers to upgrade their code to be compatible with BuddyPress 1.2 sooner rather than later

More detailed instructions and details will come as the 1.2 launch comes closer, but this is the best way to make sure everyone is happy.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

You’re best to deactivate BuddyPress and any plugins that depend on it before upgrading.

2.9.1 should be the last time you will need to do that though.

[@johnjamesjacoby Keymaster 16 years, 9 months ago]

1. BP trunk already supports 2.9.1, and 1.2 will as well.

2. BP trunk works very well on WordPress 2.9.1 (not MU)

3. Don’t expect WP3.0 until at least June, if not later. The WordPress dev cycle is aiming for new versions every six months.

r-a-y’s been paying attention.

I would recommend staying away from the trunk version of WordPress (single) at the moment. The WPMU trunk currently contains the most up to date WPMU 2.9.1 version, it just hasn’t been officially released yet.

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

Either you fixed it, or you’re missing something…

Not all blogs are 404’ed… http://bloggingwire.com/yourfitness/about

Looks like just the club link isn’t working, but does the /club blog actually exist?

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

https://wordpress.org/extend/plugins/bp-member-filter/

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

@Mike Pratt

I think from a development perspective, it was easier to avoid the WP profile entirely, since it’s far too limited in what you can do with it. Like you can’t (in the DB) easily tell the WP profile screen which dynamic field type to use for each dynamic field. Since BuddyPress took the direction of being entirely theme based, it made sense to make a whole new profile with a more direct apprach to setting the fields and getting/updating the data.

For 1.3 there will be a more powerful xprofile system that makes for smarter fields.

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

If you install a fresh copy of bbPress in a forum on your server called “forums” then it will override the slug in most installations. At that point you would need to theme your bbPress installation to look like the rest of your website.

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

The first way is for users that may have been registered before BuddyPress was installed. They can still login, post comments, and use the forums, but if they never edited their profile and set their display name(fullname), BuddyPress won’t find them.

The second is if a user edits their profile from the WordPress side (firstname, lastname, nickname) without changing their BuddyPress display name. At that point the two will be out of sync.

It’s possible to hook into the save profile action of WordPress and change the BuddyPress display name when the user changes their WordPress nickname, but some sites may want a combo of the firstname/lastname while others may want to use the nickname, and others still may not really even care or use either. From that perspective it makes sense to not have BuddyPress try to interfere too deeply with syncing profile fields that might not have a direct 1 to 1 relationship with each other.

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

We need more information than this to help you.

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

No but it’s a request that comes up every so often. It wouldn’t be too hard to create this, but I’m not sure anyone has put anything together like this yet.

A lot of this comes down to the theme and how you style the certain abilities of BuddyPress within that theme. You can also use the parent/child abilities to block different aspects of the blogs/sections of your site, which is typically what I’ve done in the past.

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

@Dan Butcher

There are two ways users can back themselves into this corner and they come from how their accounts were setup in the first place and what they do with them afterwards.

Try this BP to WP Profile Sync plugin I just wrote up for you, and let me know how it goes?

@peterverkooijen

I know this is something that you’re passionate about, and xprofile will get a good makeover in 1.3, but this IS the best way to handle names for all audiences, at least until someone can come up with a solution that somehow makes more sense. I also know that you’re trying to be helpful, but this isn’t the topic to have this debate in.

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

@michaeleisenwasser

You will need to scan a directory for strings and compile a list of them. This is already done for you with the included .pot file. Open that file and start translating, then save it as buddypress-es_US.po.

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

Plugins shouldn’t need to change very much between 1.1 and 1.2 versions. What’s changing mostly is the theme, and the removal of status updates and the wire component.

Easiest way to get the BP version is to use the BP_VERSION constant, but again, chances are you won’t need to do that.

[@johnjamesjacoby Keymaster 16 years, 10 months ago]

Code should be free under the GPL, but support has value. Unfortunately it’s difficult to charge people for your time through a website, which is why developers tend to charge for code or put up a paywall.

Someone make a BuddyPress site where your paypal is part of registration, and every time someone in the developer group marks a forum topic as resolved, it invoices paypal for $1 from the topic starter.

That, would be the best way to make money as a dev without freelancing or consulting, in my opinion.