Activity commenting: Forum post and blog comment activity permalinks

[r-a-y]

I wrote about this issue in the bp.org forum thread about the new activity commenting feature, but thought I'd post it here as well.

---

The new activity commenting feature creates a permalink or thread for each item, however activity permalinks should probably be disabled for forum posts and blog comments due to content duplication.

If a comment is made on a forum activity item, perhaps add it as a forum reply instead?

Likewise if a comment is made on a blog post, perhaps add it as an actual blog comment. This might be a little tricky...

If we decide to keep blog activity permalinks, a possible workaround could be to add a WP function called "Community Reactions", which could be added to a WP theme's comments.php. This is where activity comments could be listed. Kind of like a trackback or something. Just a thought.

[r-a-y]

The basic problem is fixed now.

As a future enhancement, there are users on testbp.org who are fans of AJAX inline commenting for blog comments and forum posts.

I understand this is more complicated to achieve though.

[paulhastings0]

I would say that there's still enough interest in integrating forum posts, blog posts, blog comments, activity streams, etc. to warrant re-opening the ticket and examining it.

(Read a few of the last posts on the 1st page.)

[boonebgorges]

I think this is plugin territory. The hooks and filters are there to make this into a plugin. It would be a pretty straightforward exercise for someone who knew what they were doing.

IMHO BP's threaded activity stream (which is much more complex and elegant than WP comments or bbPress forum topics) is one of its real strengths. Putting this kind of content diverter into BP core, even as a non-default option, means adding a bunch of infrastructure to something that is in a way not as nice as the BP-native option.

As r-a-y said, this issue is largely fixed with the ability to turn off activity replies for certain kinds of activity items.

I'm going to remark as fixed, though I'm happy to have more discussion about the issue.