[Bug] Empty blog drafts cannot be deleted

[pokrakam]

Was trying to clean up my blog drafts:

But when I try to delete any of them I get this:

Obviously it's easy enough to work around and thus not a high priority, but a silly message nevertheless.

[jerryjanda]

What's odd here is...I'm not sure how you were able to save these as drafts in the first place. These drafts don't have primary tags, and if you don't have the proper number of characters in the title and body copy, you shouldn't be able to save.

Can you explain the steps taken to get these saved into drafts?

--Jerry

[JL23]

Does not seem to be an exception, there are at least 106 like this: https://blogs.sap.com/wp-admin/edit.php?post_status=draft&post_type=postℴby=titleℴ=asc&paged=1

[JL23]

I just produced one.

I started the page to create a blog, entered some words and removed them again. Had not at all entered a title. Just kept staying in that page for a while. Draft was saved automatically:

then I left the page.

Now there is a draft to see in the overview of blog drafts

and deletion will trigger the message as reported above

[pokrakam]

As it so happens I documented the steps in precise detail at the time I created those very drafts.

See: [Bug] Blogging with an iPad jumps all over the place

(Still unresolved...)

[agentry_src]

One must add at least the minimum words. I usually use something like "Content to prepare for deletion"

One must also have a title and a selected primary tag. Doesn't much matter what either one is as long as they meet the requirements.

Then you can delete the blog.

As far as creating empty blogs, when you are editing one blog, you can also create a new one from the side menu. I suspect there is an autosave function that does not care one way or the other about the validity of the content. Once you have created it, without any other content or input, you then have to go through meeting the minimum blog requirements before you can delete it.

IT should probably review this and move the minimum requirements to the creation function instead of the deletion function.

Regards, Mike Appleby

[pokrakam]

Yes, I did say it's very easy to work around. But a bug is a bug, the error is silly and should be corrected.

I note it still hasn't been fixed. I could be sad, but maybe I should just be happy that they're dealing with higher priority things.