Project

General

Profile

Actions

Bug #1316

closed

Buddy Press Docs - comments going to email, but not to the Doc

Added by scott voth about 13 years ago. Updated about 13 years ago.

Status:
Resolved
Priority name:
Normal
Assignee:
Category name:
BuddyPress (misc)
Target version:
Start date:
2011-11-02
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

Hi - I noticed this when I received a comment via email from Brian - the comment did not get posted to the actual Doc he was commenting on, but went out via email. Group was our CAC team - http://commons.gc.cuny.edu/groups/cac-community-team-project-planning/

Here is the comment:

Brian Michael Foote commented on the doc Help System Standardization: at 9:01 pm, October 29, 2011
Hey all, I wanted to mention that I posted a couple of screencaps of Help pages from Etsy, Flickr, and Tumblr just to show how other folks do help. I know I could have just linked to them but…well…I didn’t. The new Codex looks great Scott! This may not be remotely helpful but personally when I look at Help and Support compared to the Codex it feels as though H&S is guided support and the Codex is almost like a manual for the Commons. I realize that isn’t entirely the case but I like how H&S has lead in questions like “How can I create a…” whereas the Codex is more itemized in its description. I’m wondering if it’d be at all helpful to package these two sections that way to members even if the information overlaps significantly. The reason for doing so would be to shape H&S into a place where people could go to learn how to do something whereas the Codex would be more about, er, less hand-holding maybe, or less Com munity Facilitator involvment over the community at large? As a blog H&S could have more of the videos we’ve talked about creating similar to the WP101 videos. We could possibly do member support through the comments on those posts as well so that we could just reference those if the same questions came up, or better, people would find them searching through the site. I’d love to know how you conceptualize the differences between the two. I see that the H&S blog is the main landing page but it’s so robust that I’m having a hard time seeing what keeps them totally distinct. Looking forward to working on this more in the meeting!

But I can't find the comment in the doc. http://commons.gc.cuny.edu/groups/cac-community-team-project-planning/docs/help-system-standardization


Related issues

Has duplicate CUNY Academic Commons - Bug #1321: BP Doc Comment Doesn't Show Up on Doc (but does appear in group stream)DuplicateBoone Gorges2011-11-03

Actions
Actions #1

Updated by scott voth about 13 years ago

Hi - I also noticed that Sarah commented on this doc - and I got an email - but it didn't get recorded in the doc.

Actions #2

Updated by Boone Gorges about 13 years ago

  • Status changed from New to Assigned
  • Assignee set to Boone Gorges
  • Target version set to 1.2.5
Actions #3

Updated by Boone Gorges about 13 years ago

I've done a bit of poking, and it looks like the "To view or reply..." links at the bottom of the emails, and some of the links in the activity stream, are going to the incorrect Docs. That is, the comments are appearing in the places where they're intended to appear, but you're getting the wrong links. Looking into it.

Actions #4

Updated by Boone Gorges about 13 years ago

OK, I've narrowed it down a bit more. It appears to have something to do with parent and child Doc hierarchy. More specifically, parent Docs appear to be showing the comments of their youngest child.

I can't tell at a glance whether this bug is the fault of BuddyPress Docs or of WordPress itself - the technique I use for pulling up child docs is a technique that I've found to be buggy in WP before. I'll do some more exploration. Opened a BP Docs ticket here if anyone cares: https://github.com/boonebgorges/buddypress-docs/issues/149

For the moment, I have disabled the display of the "Children" display underneath a Doc content. Comments are now appearing where they ought to appear.

Actions #6

Updated by Boone Gorges about 13 years ago

  • Status changed from Assigned to Resolved
Actions

Also available in: Atom PDF