[@johnjamesjacoby Keymaster 16 years, 5 months ago]

Upgrading to 1.2.4.1 should fix this issue.

[@johnjamesjacoby Keymaster 16 years, 5 months ago]

The $current_site check was put into 1.2.4 when it was meant for 1.3.

It’s been reverted for 1.2.4.1.

[@johnjamesjacoby Keymaster 16 years, 5 months ago]

Fact is that not every website needs to be a social network, same as not every site needs to be a blog network.

BuddyPress, much like WordPress, shines when you don’t even know you’re using it, and it’s up to good themes to make that happen; something BuddyPress lacks when compared to WordPress.

There are limitless setups that you could dream up with mutlisite WordPress and BuddyPress, but none of them matter if the theme can’t pull that functionality out to be front and center. Multiple blogs, sites, networks, domains, communities, groups, etc… I think it’s safest to mirror the development of your community similarly to how one prepares a server; react to the size and don’t over-prepare. If you have 10 users, you probably won’t need W3 Total Cache and a CDN. Once you have 10,000 active users, you may want to consider beefing things up. Same with BuddyPress; once you have a ton of users, turn on groups and forums, or add something new and exciting.

Community features should match community size. If you turn on too many features with not enough users, your website looks like a ghost town, and no one will join. If you don’t have enough features, people will get bored and leave. BuddyPress does its best to let you find that balance pretty quickly, and helps you shape your online community how you see fit.

It’s like SimCity, but without the natural disasters.

[@johnjamesjacoby Keymaster 16 years, 5 months ago]

bp_user_link hasn’t been deprecated, but it’s on the chopping block.

I think we’ll need to sweep through the functions for 1.3 and strongly define what the _member_/_loggedin_/_displayed_/_user_ function names are inferring. In the past (and currently) some of these were used rather inconsistently. I cleaned some of this up in the branch last night for 1.2.4, but there’s plenty more to do.

[@johnjamesjacoby Keymaster 16 years, 5 months ago]

@grosbouff For the purpose of your plugin, bp_profile_group_has_fields gets in the way. The purpose of bp_profile_group_has_fields in the default theme, is that it will skip over any group of fields that have no values filled in when inside the profile loop.

I think what you want to use is bp_field_has_data().

I also don’t think that this is a bug. All of those functions are doing exactly what is expected.

Can you explain in more detail what you need these functions to do?

[@johnjamesjacoby Keymaster 16 years, 5 months ago]

Part of the problem might be running BuddyPress in a subdirectory. We use some tricky URI parsing to dynamically trap and trigger the pages that don’t actually exist. To do this, we count the slashes and put the slugs in the “correct” positions, which in your case are one level off.

You could .htaccess your way out of this by redirecting, but your best bet is to install it at the root of your site.

For those only having the trouble with /register and /activate, make sure you have member registration turned on. Since it’s off by default on single site WordPress, that has gotten me a few times.

[@johnjamesjacoby Keymaster 16 years, 5 months ago]

You’ll also need to make sure you have Arabic installed for WordPress, and if using multi-site, Arabic must be set as the site language in site wide settings.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

I like the colors and logo. Looks cool and it incorporates BuddyPress really well.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

Avatar uploads will be fixed In the next point release, due out very very soon.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

Yes it is. You will want to wrap your code in HTML code tags.

You’ll want to omit opening or closing PHP for the time being though, looks like the filter is a little too strong.

echo $foo;

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

@techguy The philosophy for wide-spread adoption is to not create any additional tables, and use meta whenever possible. This way you can rely on the internal functions of WordPress and BuddyPress to get and set that data, and you don’t have an upset site admin that needs to figure out where to put that table, how to cache it, how to serve it across multiple servers, etc…

I also think it depends on the scope that you need to achieve. The Groups API works really well for just about anything that you would want to plug into the groups component, but at the same time there can also be a need for totally 100% custom jobs where even the built in functionality doesn’t work for your application, in which case a totally custom theme might be in order.

All in all, I usually start with a custom plugin, that relies on the Groups API and group meta, and only use wp_sitemeta/wp_options if it’s a blanket default setting for all groups that can be changed by the site administrator.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

All over it.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

Old member pages are 404ing.

https://buddypress.org/members/johnjamesjacoby/

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

When trying to upload a group avatar: “There was an error handling that image, please try again.”

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

On forums root, every other group is assigning all tr’s as “alt” resulting in it showing up as all white instead of grey / white.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

I predict this topic has many replies in very little time, most of which will probably be of the thankful variety.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

I’ll ask politely that this topic not turn into another debate please.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

I’m conflicted.

1. I’m happy there are multiple solutions for Ning users to import their data into BuddyPress.
2. I wish that everyone’s efforts were on making this a near-perfect option in the core package.

I firmly support Boone’s option because it aligns with my personal beliefs, but I appreciate that there is another option for people with beliefs that are different than mine.

Putting code behind the paywall just makes it hard for me to celebrate its success as much as I feel like I want to.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

Fixed in branch. Expect a point release soon to address this and a few other sign-up issues.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

Thanks for keeping on top of this everyone.

[@johnjamesjacoby Keymaster 16 years, 6 months ago]

I think that if the low level core API of BuddyPress is strong and extensible, then ‘what BuddyPress is’ will mean different things to different people, depending on why they use it.

In a land before time, BuddyPress was actually intended to be several separate plugins, but having different components with different version numbers and dealing with the dependencies would have been a nightmare.

Now though, watching plugins merge and adapt, it doesn’t seem that unlikely.

Imagine if when you DL BuddyPress, you’re just DLing BuddyPress core, and the install routine lets you pick which additional components you might want for your social network, and it puts them in the BuddyPress directory. Not everyone needs friends, but maybe they want to follow each other. Different plugins for almost the same thing. Users should be walked through the component picking process to be able to shape their social network in a matter of minutes.

I believe the component API should be built for rapid deployment of new components. It should take care of the things we currently spend hours trying to dance around. I.E. component registration, template inclusion, URL rewriting, GET/POSTing, and it needs to give each new component its own API at the same time, so that we can easily communicate between these components and make them talk to each other in a universal way.

Then BuddyPress will become less of a “friends/activity/groups/profiles/pm” plugin, and more of a “sum of its parts” plugin.

So, the API would need to be fairly self aware, and include setters/getters/checkers for just about every routine there is for them to possibly do.

We had a ticket open about 4 months ago with a transitional API that I started for a general BP_Component class. It wasn’t much, but maybe a start?

[@johnjamesjacoby Keymaster 16 years, 7 months ago]

The visibility of the Admin nav-item is a side effect of “Site Wide: true” but it isn’t the correct way to fix this.

The “Site Wide” meta value doesn’t have anything to do with users, roles, or capabilities. It’s only there to tell WordPress that plugin can act as the umbrella that covers all blogs/sites in a network.

The offending plugins are simply just not using the correct methods to add their navigation to the Admin area.

WordPress has many wrappers to help make this easy for plugin authors:

add_management_page

add_options_page

add_theme_page

add_users_page

add_dashboard_page

add_posts_page

add_media_page

add_links_page

add_pages_page

add_comments_page

All of the above functions are passed an $access_level variable, that can be set to a “current_user_can” value to limit its access.

I’d drop a message to the authors of the plugins that are showing their settings to unauthorized users. That isn’t just inconvenient/embarrassing/confusing, it’s a security risk.

[@johnjamesjacoby Keymaster 16 years, 7 months ago]

With less than a day left now,there’s probably little value in putting the blog post up.

But, you can refer to these links for ideas.

http://spreadsheets.google.com/ccc?key=0AtgQiOrXrZ0ZdE5rUnRzTXB0VWtqTUtvVkp1Rk9lYXc&hl=en

https://buddypress.org/about/roadmap/

Some things I’m excited to see:

An events component that doesn’t *require* bp-groups

Privacy that uses WordPress roles and capabilities

REST API

Inappropriate content flagging

User attachments

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

I like this thread, so I’m going to check back on it in 3 hours. If you haven’t cleaned it up yourselves, I’ll do it for you.

And… if I wasn’t posting this from the Apple store, I’d probably have locked it. Haha!

[@johnjamesjacoby Keymaster 16 years, 8 months ago]

I like it. Will be very popular when it’s finished.

Good job.