[wp-trac] [WordPress Trac] #45537: Allow block editor to be used on the posts page using filters

[WordPress Trac]

#45537: Allow block editor to be used on the posts page using filters
-----------------------------+-----------------------------
 Reporter:  cameronjonesweb  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Future Release
Component:  Editor           |     Version:  5.0
 Severity:  minor            |  Resolution:
 Keywords:  has-patch        |     Focuses:
-----------------------------+-----------------------------

Comment (by grantmkin):

 > Is there any reason why we can't use Gutenberg on the posts page by
 default? Can we make a patch to do that instead?

 @youknowriad Trying to understand the context around this I found
 https://core.trac.wordpress.org/ticket/17470. The content editing UI is
 hidden on the empty `page_for_posts` page in an effort reduce user
 confusion, since themes typically don't display the post_content of that
 page.

 Is there a good way to disable post_content editing when loading Gutenberg
 for that page? If not, that seems like a reason to continue disabling
 Gutenberg by default, but adopt the change proposed in this ticket to
 allow filtering (at least for now).

 With the filtering enabled, in the near term I imagine the Gutenberg
 plugin would enable the block editor on the posts page for block based
 themes and load the appropriate template for editing, which would solve
 the problem of edits for that page not being shown by the theme 🎉.

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