Contributor Role unable to 'Save Draft' posts

[stylemo]

After updating to 3.8.2, the Contributor role can't 'Save Draft' anymore.

Logged in as 'contributor', when I try to save the posts as draft, all the fields become blank and the post is lost and not saved at all. This only happened when the site auto-updated to 3.8.2.

Probably a related issue of #27734

[nacin]

Hi stylemo, are you referring to the "Quick Draft" box on the dashboard? That's a known issue covered in #27734.

I cannot reproduce any issues with a contributor pressing "Save Draft" while editing post (as in, on post.php?action=edit). I also imagine if we had broken this we would have received more than one bug report about it in five days. Could you describe what exactly is going on? Any JS console errors? PHP errors logged? Any plugins?

[stylemo]

Hi nacin. No, I'm not referring to the "Quick Draft" box but I am referring to the main editor page when composing a post as a 'contributor' role. 'Save Draft' button when submitted clears the title field but not the other fields (custom meta fields isn't cleared). And when I check the Draft posts section, the posts isn't there so it's not saved at all.

Sorry, I wish I could give you more debug info but the best I could describe the problem and I hope that helps.

I could confirm that 'Save Draft' posts recently work on 3.8.1 and lower versions.

[nacin]

stylemo, I still cannot reproduce, I'm sorry. Do you have any plugins installed? Are you able to reproduce this without any plugins activated on a 3.8.2 install?

[SergeyBiryukov]

Confirmed.

1. Log in as a contributor and go to Add New Post screen.
2. Enter just the post title and click "Save Draft".
3. The title becomes blank again, and the post is not listed on the Posts screen.

Does not happen in 3.8.1 or trunk, only in 3.8.2.

[dd32]

Enter just the post title and click "Save Draft".

There's an important step here that's somewhat not obvious, which is why I couldn't repro this earlier, you can't let it set the slug, you have to go directly from Title -> Save Draft with no stopping inbetween.

[SergeyBiryukov]

Appears to be triggered by [27976]. [28073] fixed edit_post(), but not _wp_translate_postdata().

In trunk, we have (since [27405]):

if ( ! isset( $post_data['post_status'] ) ) { 
	$post_data['post_status'] = 'auto-draft' === $previous_status ? 'draft' : $previous_status; 
}

In 3.8 and 3.7 branches, it's:

if ( ! isset($post_data['post_status']) ) {
	$post_data['post_status'] = $previous_status;

27795.patch​ (for 3.8 branch) fixes this for me.

[dd32]

27795.diff​ is a patch I was working on that makes use of the existing auto-draft -> draft conversion which takes place inside edit_post() (line 206-208), this also avoids an unset index notice in that same block ($post_data['post_status'] is unset on 206 in this case). I've added extra context to the patch to see that logic.

SergeyBiryukov's patch does exactly the same thing really, it just happens in a different function,

[nacin]

I can reproduce this bug on 3.8.2, but I can't reproduce this bug on the current 3.8 branch. This appears to be fixed for me by [28073].

I will also note that any auto-draft lost this way is recovered by [28075]. Nice.

[nacin]

As in: I don't find a patch to be necessary here. But wondering what I'm missing.

[ocean90]

I could reproduce the steps by SergeyBiryukov, but only before [28073], not after (current branch).

[kirasong]

I am also not able to reproduce post [28073] in the 3.8 branch. Is a further patch is necessary for other reasons?

[nacin]

Closing as a duplicate of #27734.

[dd32]

Replying to nacin:

I can reproduce this bug on 3.8.2, but I can't reproduce this bug on the current 3.8 branch. This appears to be fixed for me by [28073].

I will also note that any auto-draft lost this way is recovered by [28075]. Nice.

Confirmed again. I was mistakenly on the 3.8.2 tag instead of the 3.8 branch.

[SergeyBiryukov]

Replying to nacin:

I can reproduce this bug on 3.8.2, but I can't reproduce this bug on the current 3.8 branch. This appears to be fixed for me by [28073].

Yes, I was testing 3.8.2, not the branch. Sorry for the confusion.