Make WordPress Core

Context Navigation

Changes between Version 1 and Version 2 of Ticket #30052, comment 6

Timestamp:: 11/23/2014 07:47:23 PM (12 years ago)
Author:: bobbingwide

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #30052, comment 6

-              v1
+              v2
 It may be a bit early in the day to confirm that I have the same problem but I am getting the same unexpected result. The Crunching... never ends.
+I was getting the same unexpected result. The Crunching... never ended.
 Notes:
 The filename changes to the new post ID ( 29144 in the latest instance )
 When I view the media page everything looks OK.
 Also the Crunching... is on the right hand side.
 In working environments the crunching is not so far to the right.
 Post ID of > 1000 is not an issue in the working environments.
+* The filename changed to the new post ID ( 29144 in the latest instance )
+* When I viewed the media page everything looks OK.
+* Also the Crunching... is on the far right hand side.
+* In working environments the crunching is not so far to the right.
+* Post ID of > 1000 is not an issue in the working environments.
 When I deactivated ALL my plugins the Crunching did complete.
+* And I can now confirm that the problem was caused by my own tracing plugin...
+* which was outputting some HTML comments during 'shutdown' processing.
+* So the response was no longer a single integer.
+* I have reproduced the problem in different environments with post ID < 1000
+* The placement of the Crunching on RHS is a red herring.
+Unfortunately my code checks for DOING_AJAX, but since $_REQUEST['action'] is NOT set then wp-admin/async-upload.php doesn't set it. Is it safe to test $_REQUEST['short']?
+The question one might ask is "should there be some way
+of communicating to routines that hook into 'shutdown' that the response has been sent and you mustn't do anything to mess it up?"
+Could the client end be a little less sensitive?