Offline post writing could lead to overwriting the previous post

[vloo]

Using Chrome 34 on Linux Mint 16.

1. Open two "Add new post" tabs;
2. Publish a post in the first tab -> it gets id=X
3. Go offline;
4. Write something new in the second tab that you opened;
5. Go back online;
6. Publish the new post from the second tab;

Result:

The post from the second tab gets id=X and the previous post becomes a revision of the new one. Slug of the new post is in effect when you got /%post_name%/ permalink structure and opening a link to the first post will lead to 404.

P.S. Could be somewhat related to #24447 and it's older twin-brother - #9604.

[SergeyBiryukov]

Related: #28288

[adamsilverstein]

vloo -

thanks for the bug report!

i wasn’t able to immediately reproduce the bug... Can you reproduce this every time?

can you clarify in step 3 when you say 'go offline' are you disconnecting your internet connection? how long did you wait before going back online? also, can you verify that you are using the latest version of WordPress and also try disabling all plugins and testing again? Finally, if you are know how or are adventuresome, can you try applying the patch in #28288 to see if that resolves the issue?

thanks.

[vloo]

I must admit both sites that I tested the issue were live environments with some plugins in action, but both 3.9.1. I'll test it on a clean install now just to clarify that it's WordPress, not a plugin (sorry for not thinking of this earlier!).

Step 3 is disconnecting from the Internet. Prior to that I don't have any text or even title input in the second tab. I stay offline for a couple of minutes, not a long period.

If I manage to reproduce it again, I'll apply the patch too.

[adamsilverstein]

OK, thanks.

I think the bug is WordPress and possibly related to autosaves, if we can nail down a way to consistently reproduce we may be able to figure it out. Also, if the other ticket patch gets accepted i think this will solve your problem. it may not be a plugin issue, i only ask because it is good to rule out this possible issue.

[vloo]

Can't be reproduced any more. I guess it was fixed at some point or the original report I did was under the influence of some plugin.