[wp-trac] [WordPress Trac] #37889: "Add post" overwriting a previous post in 4.6

[WordPress Trac]

#37889: "Add post" overwriting a previous post in 4.6
--------------------------+------------------------------
 Reporter:  tgelles       |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  General       |     Version:  4.6
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  administration
--------------------------+------------------------------

Comment (by tgelles):

 1) If I tried to "take back" my posts, the page would refresh with the
 same prompt as before: "This content is currently locked. If you take
 over, X will be blocked from continuing to edit."

 2) I am creating posts as the same user. My steps were:

 Add New Post --> Fill out title, content, etc, publish or draft
 Click "add new post" and the page would refresh,
 Begin typing, but the generated permalink of the most recently created
 post.

 Similarly, If I were to go back to the main Posts admin page, I'd have to
 refresh my browser to see the new post.

 I made some major tweaks to my htacess file, removing the[6G Firewall 2016
 sections https://perishablepress.com/6g/], plus this legacy material:


 {{{
 # BEGIN GZIP
 <ifmodule mod_deflate.c>
 AddOutputFilterByType DEFLATE text/text text/html text/plain text/xml
 text/css application/x-javascript application/javascript image/svg+xml
 application/octet-stream
 </ifmodule>
 # END GZIP
 }}}


 and


 {{{
 # Browser Caching: http://code.google.com/speed/page-
 speed/docs/caching.html#LeverageBrowserCaching
 #
 # Set the cache-control max-age
 # 1 year
 Header set Cache-Control "max-age=14400, public, must-revalidate"
 <FilesMatch
 "\.(ico|pdf|flv|jpg|jpeg|png|gif|js|css|swf|svg|woff|ttf|eot|otf)$">
 Header set Cache-Control "max-age=31622400, public"
 </FilesMatch>
 # 2 DAYS
 <FilesMatch "\.(xml|txt)$">
 Header set Cache-Control "max-age=172800, public, must-revalidate"
 </FilesMatch>
 # 4 HOURS
 <FilesMatch "\.(html|htm)$">
 Header set Cache-Control "max-age=14400, must-revalidate"
 </FilesMatch>
 # Remove ETags
 FileETag None
 }}}

 And, for now, it seems to have done the trick...? Somehow?

 The url: wp-admin/post-new.php?post_type=people&wp-post-new-reload=true is
 now appearing whereas before I believe the '&wp-post-new-reload=true ' was
 not included in the URL.

 I am continuing to monitor everything, but I'm wondering if those edits
 could be a culprit?

--
Ticket URL: <https://core.trac.wordpress.org/ticket/37889#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform