Disappearing posts/pages (in quickedit mode)

[catahac]

Steps to reproduce:

1. Quickedit a post.
2. Click save and instanly click quick-edit on another post.

When the ajax-request completes the first quick-edited post will disappear from the posts table. This is only a display bug.

[hakre]

Just experienced the same. Can confirm this for 3.0 trunk. It's a bug in the frontend JS logic. Defect by Design.

[lsparks]

This is still an issue as of 3.1, any updates as to when this might get addressed?

[sivel]

Please do not change the version on tickets. The version is used to track when a bug was introduced/identified.

[lsparks]

Sorry, I didn't know that. Thanks for the info.

Please do not change the version on tickets. The version is used to track when a bug was introduced/identified.

[chriscct7]

This still occurs also its really hard to trigger.
To reproduce:

• Edit something on the quick view of a post (but do not click save)
• Move cursor over the quick edit of another post.
• Hit enter (which triggers the JS to submit the quick edit) and instantly after you do that click on the quick edit button on the second post your cursor was already on.

Incredibly hard to do unless you're really trying to do this, but still reproducible nonetheless

[kevdotbadger]

I think the problem is caused the removal and appending of the new row returned by the AJAX request, although I'm not 100% sure (it might have something to do with either the ID getting messed up, or which rows are being removed, or the revert() happening at the beginning of the edit, or something else!?)

Anyway, the old code was

$(inlineEditPost.what+id).remove(); // Remove the original (now hidden) post row
$('#edit-'+id).before(r).remove(); // before the editor row, add the new HTML returned by the save AJAX request, then remove the edit row
$(inlineEditPost.what+id).hide().fadeIn(); // with the new returned and added to the DOM, hide it then fade in.

My solution was to use the original row, and not remove it at all. Simply inject the needed HTML back into it. This solves bug.

$('#edit-'+id).remove(); // Remove the edit row
$(inlineEditPost.what+id).empty().append($(r).html()).fadeIn(); // Inject the needed HTML the original post row and fade in

The r returned by the AJAX call contains the whole row as HTML, I'm not sure if this returned HTML is used elsewhere, so i left that alone. The $(r).html() simply gets the child elements which we need to inject back into the original row.

[kevdotbadger]

Same diff, but without the min version.

[kevdotbadger]

I'm also unsure how the core team handles minified versions, do they minify everyone prior to release? Anyone 12769.without-min-version.diff is the same diff but without me touching the .min version.

[afercia]

Some things have changed in the Quick Edit form in the last months: buttons are now buttons, JavaScript events, etc. Couldn't reproduce anymore, but maybe I'm missing something. @chriscct7 would you mind to double check and try to reproduce when you get a chance? :)

[afercia]

Nevermind, was finally able to reproduce. Very unlikely to happen though, unless you're doing it intentionally :) What I'd do:

• on Quick Edit link click
• return if a previous AJAX request has not completed

Investigating also #25696 which maybe requires a similar solution.

[afercia]

See #25696 for a proposed solution. Note: this happens also on Categories, Tags, and Comments.

[jorbin]

No changes in the last 8 weeks, so I'm bumping from 4.5.

@afercia If you think you have a fix, feel free to re-milestone.

[oglekler]

I managed to reproduce an issue by setting network speed to slow in Developer Tools > Network. Patch from #25696 needs to be tested for solving both issues with disappearance of rows in the admin after some action.