BuddyPress.org

I am seeing a small error in Safari 4. Looks like you need to add a clear or perhaps just some shifting around in the loop. I am getting steps down the page with content. Looks great in Firefox 3.5 though.

You can see a screenshot here.

It seems that you are more than likely using an older theme, one that is not compatible with the version of BP that you’re running.

Please answer these questions so that we can better understand your setup:

https://buddypress.org/forums/topic/when-asking-for-support

i was just about editing my post to say I have been posting too fast.

forgot to move the /links in the theme directory. now it works perfectly.

indeed a very useful plugin and perfect integration job

what bowe said above is realy the truth : not every plugin for BP is so well developped

thanks

i just installed it fine on my wpmu 2.8.6 + BP 1.1.3

but can’t get it to work

there is no page at http://myexample.com/members/admin/links/create/step/link-details

could it be that the plugin doesn’t support the 1.1.3 release ?

in any case I will follow what seems to be a very nice plugin

RC1 Unstable… I really want this on my production site. Though I’m hesitant to install because of the ‘unstable’ bit.

I think many people have no idea how extremely full featured and well programmed this plugin is.. I’m just starting to grasp the amount of possibilities this plugin can mean for almost any buddypress site.

I would go as far that this plugin is the best 3rd party plugin I’ve seen so far and that it only looks to become better and better. Expect a post about this plugin on BP-Tricks.com sooner then later!

Great work Marshall!

Can anyone that’s having this problem back-up your buddypress directory, and try a clean zip file download and FTP upload of buddypress 1.1.3?

I have a feeling the auto-updater didn’t get a chance to finish up what it was trying to do, and it’s dying before it copies all the files correctly.

… it isn’t feasible since the queries it would take to pull that off would be astronomical.

If the data can be written to a table to begin with, and the structure of the written data makes sense, then in theory a query can be designed to accomplish the same outcome without having to write it to a table.

But in practice, since WP uses a sharded DB and not a normalized DB schema, this could be an issue.

… but I think the talking back and forth between the components isn’t really the job of the core to do

Okay, I think I just saw a ghost. That was a scary comment, jjj!

Whereas I agree that it may not be the responsibility of the core to ensure that non-core components successfully talk back and forth with each other or with other core components, it is absolutely the responsibility of the core to ensure that each core component effectively and properly communicates with one another when activated. Every component we have discussed here is a core component.

What you basically just said is the right hand does not need to know what the left hand is doing. In actuality, your right hand may not always need to know what your left hand is doing, but sometimes it is an absolute necessity. The brain takes care of this for us, of course.

BuddyPress’ core needs to take care of monitoring, negotiating, and policing the actions of its core components. As users and developers, we are entirely dependent on the core development team to make sure that happens.

And if I could reply to only Jeff right now, I would say T_PAAMAYIM_NEKUDOTAYIM!

But since I can’t I just forked this conversation in a totally new direction! How’s that for activity.

I think Jeff is right, but it isn’t feasible since the queries it would take to pull that off would be astronomical. The reason this is an activity cache table is because it is where activity is stored in an easier to gather fashion. Maybe cache is the wrong word, but it’s doing what it says by being an easier way to combine other queries into one easy to get, light on its feet query of site wide activity.

The only other solution would be to branch activity comments off into a separate table, but that would require a query for each group of comments, instead of just grabbing all of what’s relevant and dumping it out.

Back to the original topic I suppose, but I think the talking back and forth between the components isn’t really the job of the core to do. The activity stream is a functional component of BuddyPress, and BuddyPress can exist without blogs, comments, and forums. In that scenario activity commenting doesn’t matter because there’s nothing to sync with. If someone needs to sync that data, they can make a plugin to do it, just like someone made a plugin to sync bbPress replies to blog posts and vice versa.

That’s a cool message. Google suggest it means “missing double dots” aka ::.

Are you trying to call a static class function from a dynamic variable thingy? e.g.

$myvar = ‘something’;

$myvar::explode_world();

I looked up T_PAAMAYIM_NEKUDOTAYIM briefly yesterday; it’s something to do with the double-colons.

I commented out line 195 for now:

return $this_group::save();

Probably because the spammers don’t recognize it as BuddyPress yet, don’t expect that to last long.

How about we put all of the components that allow activity to hit the stream(s) into an array. Say…

$bp->activity->actions

Then, that array (which already exists) can be altered by a potential administration panel (or future permissions later.) BuddyPress plugins can register themselves as having activity with bp_activity_set_action( ) to which there should be a bp_activity_remove_action() that would add or remove activity abilities to the array such as $bp->activity->actions->comments_enabled

The array will have everything set to true by default. Constants in bp-custom.php or a plugin that makes an admin panel can then set those values to true or false…

bp_activity_get_action()

As long as there’s proper actions in place, plugin authors can sneak in there and append data to comments/forums/posts, whatever, provided everything is available at run time, which it usually is.

Long story short, add another $arg to set if commenting is allowed or not.

Even better…

This would also be a great reason/time to implement an activitymeta table, as it would allow this type of thing to not be core, but plugin territory if someone needs it. Or, that kind of on/off switch could just be in sitemeta and a plugin could block comments on specific activity actions from within the action.bp_blogs_activity_commenting = false

There’s actually a ton of ways this could be done pretty easily.

I think a great way to solve this problem would be to have a way for the activity stream item itself to know which post it is pertaining to, and pull that stream and display it on the post either in lieu or or addition to comments. Then people could comment on the activity stream from within the blog post too. Imagine a blog post that said “Comment on this blog post, and see what people are saying about it.” They’re the same but different, and if templated correctly now you have comments about the text of my blog post, and comments about the fact that I posted it.

Same for forum topics and posts. Maybe you use topic/post activity as a way to say “This post is dumb and I think you’re stupid” without ever mucking up the actual forum topic of discussion itself. So you branch out new activity not just with new branches, but whole new ways to discuss that specific activity without interrupting that activity.

Take this forum post. If it had a link to say “Comment on this forum post” and it slid open a post box from within the forum for someone to give me feedback and say “This post is really too long and boring” then from within the forum view you can see each forum post has 3, 4, 20 activity comments on them.

That, is the future of how to integrate the activity stream fully into a website.

…in my opinion(s).

I think Andy touched on that in another thread. I’ll let him respond but I’m guessing the answer… for now anyway… is probably not.

A QUESTION CONCERNING THE WIRE

This is about the 1.2 theme update, so I’ll post it here to save a fresh topic… Will we be seeing a textarea at the top of a users activity stream allowing friends to post comments, as we had with the wire?

I see that activity/wire/status have been merged, so I was anticipating this – but cannot see it on testbp.org yet?

We do that now of course too… but our selection of elements is limited.

You could fake this offcourse, make a wp theme that looks exactly like your buddypress theme.

No, this hasn’t been tried yet, because there is no need and it’s still in it’s baby shoes.

Limitations would be no cross-browser support.

No oppurtunities, unless offcourse IE suddenly desides to fully support HTML5.

HTML5 is made to make markup more easy and more readable, therefore your actually use tags that fits it’s content. For example <header> for the header.

Depending on your audience you don’t necessarily have a choice about IE6. It’s not about you. LOL. I dislike it as much as anyone, but sometimes requirements are requirements. And personally… I’ve never had much problem supporting it. Even with some really far out designs. There are only a few big gottchas and you know that going in and code around it. Simple.

That said… I have no problem whatsoever with Andy not supporting IE6 in the new theme. That’s his choice and it’s a reasonable one. If you really need to use the new theme and you really need it to work on IE6… well… I guess it’s time to start hacking together a conditional ie6 bug fix stylesheet