WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #41316, comment 172


Ignore:
Timestamp:
07/26/2018 05:39:34 AM (3 years ago)
Author:
pento
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #41316, comment 172

    initial v1  
    2222> I'm a bit concerned that, as far as I can tell, there isn't a way for WordPress.org to remotely toggle this metabox.
    2323
    24 That's correct, it isn't possible to remotely toggle it, I don't believe that adding such a flag wouldn't really give us any practical benefit. The flag would have to be provided by the w.org update API, which sites check every 12 hours. If there were some dire emergency, we would be able to push out a 4.9.9 release with the meta box hidden, and because of the lag time in sites checking the API, it would have approximately the same rate of uptake as an API flag would. (We would presumably drop the update check TTL as soon as we decided to push out 4.9.9, so all sites would be updated in 12 hours from that point, the only practical difference would be the earliest set of sites to check the API would hide the meta box a little later.)
     24That's correct, it isn't possible to remotely toggle it, I don't believe that adding such a flag would give us any practical benefit. The flag would have to be provided by the w.org update API, which sites check every 12 hours. If there were some dire emergency, we would be able to push out a 4.9.9 release with the meta box hidden, and because of the lag time in sites checking the API, it would have approximately the same rate of uptake as an API flag would. (We would presumably drop the update check TTL as soon as we decided to push out 4.9.9, so all sites would be updated in 12 hours from that point, the only practical difference would be the earliest set of sites to check the API would hide the meta box a little later.)
    2525
    2626While the option exists to push out a rapid 4.9.9 release, I would be extremely reticent to use it. I expect that there will be sites that Gutenberg doesn't really work for, yet, but the proper response to that is not to panic and shutdown the callout, it's to ensure that the site user can easily keep using Classic, so we can focus on fixing the problem in Gutenberg. There are several levels of opting in to Gutenberg here: install the plugin, activate the plugin, and then for every post that you edit, choose the "Edit" button instead of the "Classic Editor" button. People can very easily back out of using Gutenberg at any time.