[wp-trac] [WordPress Trac] #62422: Can't edit pages after update to 6.7 and also later after downgrade

WordPress Trac noreply at wordpress.org
Fri Nov 22 18:33:50 UTC 2024


#62422: Can't edit pages after update to 6.7 and also later after downgrade
-------------------------------+-----------------------
 Reporter:  levskipg           |       Owner:  (none)
     Type:  defect (bug)       |      Status:  reopened
 Priority:  normal             |   Milestone:  6.7.2
Component:  Editor             |     Version:  6.7
 Severity:  critical           |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+-----------------------

Comment (by robertstaddon):

 Replying to [comment:19 seanlanglands]:
 > The contents of react-dom.min.js change between 6.6 and 6.7 (here's the
 history):
 > https://github.com/WordPress/WordPress/commits/master/wp-
 includes/js/dist/vendor/react-dom.min.js
 >
 > But the script version does not:
 >
 > 6.6: https://github.com/WordPress/wordpress-
 develop/blob/ee5bd5553f96264359a029768e1525dbc623ed63/src/wp-includes
 /script-loader.php#L112
 >
 > 6.7: https://github.com/WordPress/wordpress-
 develop/blob/94a798b54b4be308cfafb2db09bbed9c3ea9ff34/src/wp-includes
 /script-loader.php#L110
 >
 > I believe the above value is used for the `?ver=` parameter when
 enqueuing. Since evidence points to a caching issue, changing the version
 ''should'' have prevented these issues and forced servers/clients to grab
 an updated 6.7 script version. Perhaps naming the version "18.3.1-umd" or
 something to that effect.

 @seanlanglands has absolutely nailed the cause of the problem here!
 Brilliant work.

 Over the past week I have had multiple clients on multiple servers with
 multiple browsers on a wide variety of themes and plugins all experiencing
 this exact same JavaScript error in their console after being upgraded
 from WordPress 6.6 to 6.7. In every situation clearing the CloudFlare
 cache and having the client do a Shift + refresh to clear their local
 browser cache resolved the issue.

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


More information about the wp-trac mailing list