[wp-trac] [WordPress Trac] #43888: Move Gutenberg editor to customize.php and leave / keep old editor

WordPress Trac noreply at wordpress.org
Sat Apr 28 10:05:30 UTC 2018


#43888: Move Gutenberg editor to customize.php and leave / keep old editor
-------------------------+----------------------
 Reporter:  alexvorn2    |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Editor       |     Version:
 Severity:  normal       |  Resolution:  invalid
 Keywords:               |     Focuses:
-------------------------+----------------------
Changes (by pento):

 * keywords:  2nd-opinion =>
 * status:  assigned => closed
 * version:  trunk =>
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 Thanks for the feedback, @alexvorn2!

 If you prefer the old editor, check out the [https://wordpress.org/plugins
 /classic-editor/ classic editor plugin], which will be the offical tool
 for restoring the old editor, if you need it.

 I absolutely agree that Gutenberg fits well into site customisation, check
 out [https://choycedesign.com/2018/03/06/customizing-the-future/ this
 talk] by @melchoyce about the next phase of the Gutenberg project.

 It's also worth remembering that WordPress 5.0 won't be released until
 it's ready: that means the block editor is a great experience, there are
 solid paths for upgrading your existing code to work with it, as well as
 reliable fallbacks to the classic editor when needed.

 I'm closing this issue as Core Trac isn't really the place to have this
 discussion, but I encourage you to test your existing code and sites with
 the Gutenberg plugin, and report any bugs you run into over on the
 [https://github.com/WordPress/gutenberg/issues Gutenberg issue tracker].

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


More information about the wp-trac mailing list