Opened 10 years ago
Closed 10 years ago
#5907 closed defect (bug) (fixed)
"Load Newest" issue
Reported by: | namrons | Owned by: | boonebgorges |
---|---|---|---|
Milestone: | 2.2 | Priority: | normal |
Severity: | normal | Version: | 2.0.3 |
Component: | Activity | Keywords: | has-patch |
Cc: |
Description
When new content is detected a “Load Newest” button appears but if the user who posted the update deletes the update a few seconds afterwards, the update still loads to other users activity streams even though it was deleted previously, and they are still able to comment on it without an error being reported. In this instance would it not be appropriate to have an error appear such as “Sorry, that update was deleted by the poster” or something to that affect?
https://buddypress.org/support/topic/heartbeat-api-and-the-load-newest-function/
Attachments (3)
Change History (12)
#1
@
10 years ago
- Component changed from Core to Activity
- Milestone changed from Awaiting Review to 2.2
#2
@
10 years ago
- Keywords has-patch added
Added 5907.unittest.patch to test the issue and 5907.patch to solve it.
Before recording a comment we are actually getting the parent activity. But we only check for its visibility, defaulting to null if empty. So i think we just need to bail if the parent activity has an empty date_recorded field.
#3
follow-up:
↓ 4
@
10 years ago
- Keywords commit added
This looks like a good minimal fix. Let's get it committed.
It might be worth another ticket, but perhaps we could also look at improvements for the AJAX here, which would give a more specific error message in the case that the parent message has been deleted.
#4
in reply to:
↑ 3
@
10 years ago
Replying to boonebgorges:
It might be worth another ticket, but perhaps we could also look at improvements for the AJAX here, which would give a more specific error message in the case that the parent message has been deleted.
I agree, i will leave the ticket opened after commit is done and will try to suggest a patch to handle this case in the ajax function.
#6
@
10 years ago
I'm not sure i'm the best at this (write good english), but here's my suggestion: 5907.message.patch ;)
Hi namrons,
Thanks for your feedback, this is not related to the heartbeat feature i think, as if you create an update in one browser and display it in another one, delete it from the first browser and comment it from the second one, you have the same issue.
Working on it.