Skip to:

Opened 5 years ago

Closed 4 years ago

#3226 closed defect (bug) (fixed)

Cannot view/edit draft topic reply in backend

Reported by: antipole's profile antipole Owned by:
Milestone: 2.6 Priority: normal
Severity: normal Version: 2.5.14
Component: General Keywords:


With admin access, I spent some time preparing a topic reply in the back end, where it is easier to position media and you can preview it. I then saved a draft to return to later.

Alas, I could not access the draft reply. It is not included in the list of All replies but there was a draft included in the count of drafts in the line above the Bulk actions selection box. Clicking on the Drafts count should have listed the drafts. It gives me a 404 error. The URL attempted is:

I also tried filtering the list of replies by date as the draft was the only reply made in November. This also gave a 404.

I conclude that any attempt to access the draft reply gives a 404.

I managed to retrieve my text by accessing the database in cPanel. So it was there!

WP 4.9.8; BuddyPress 3.2.0; bbPress 2.5.14

Attachments (1)

Screen Shot 2019-11-09 at 12.40.06 PM.png (122.3 KB) - added by johnjamesjacoby 4 years ago.
Improved support in 2.6/trunk

Download all attachments as: .zip

Change History (3)

#1 @johnjamesjacoby
4 years ago

In 6931:

Topics/Replies: improved support for replies without topics.

This commit removes an assumptive call to bbp_get_topic() and avoids a debug notice when a reply is orphaned.

See #3226.

4 years ago

Improved support in 2.6/trunk

#2 @johnjamesjacoby
4 years ago

  • Milestone changed from Awaiting Review to 2.6
  • Resolution set to fixed
  • Status changed from new to closed

In bbPress 2.6, the ability to save a reply as a "Draft" is replaced with it being "Pending" instead.

However, if you have replies that actually are already Draft status, they will also now be made visible, so they'll come back to you when you upgrade.

The above screenshot shows one that I've hard-coded to draft status to show this off.

Marking as resolved. Thanks @antipole!

Note: See TracTickets for help on using tickets.