Make WordPress Core

Opened 2 years ago

Last modified 16 months ago

#45537 new defect (bug)

Allow block editor to be used on the posts page using filters

Reported by: cameronjonesweb Owned by:
Milestone: Future Release Priority: normal
Severity: minor Version: 5.0
Component: Editor Keywords: has-patch
Focuses: Cc:


Currently it doesn't seem possible to use filters to make the block editor on the posts page unless the page already has content. This is a regression from the Gutenberg plugin where this was possible. Considering it is and was possible to edit the posts page using the classic editor using filters, it makes sense that we can enable the block editor to be used on the posts page.

Attachments (1)

45537.diff (720 bytes) - added by cameronjonesweb 2 years ago.

Download all attachments as: .zip

Change History (9)

#1 @swissspidy
2 years ago

The patch looks reasonable, but what‘s the use case for being able to edit the posts page?

#2 @cameronjonesweb
2 years ago

Treating the posts page like an archive. We have get_the_archive_description for post types and taxonomy terms, content on the posts page serves a similar purpose. I use it on my site and I've had to do it on a number of client sites too

But like I said, it's already possible, it just can't use the block editor.

#3 @hannahmalcolm
2 years ago

This is something that every content marketer I've run into wants as well. They want to add content to the top of the "Blog" page.

I've had requests for social media feeds and all sorts of things, so it's not just "simple" text content. Being able to use the block editor for this page gives a consistent user experience and allows for some of the more dynamic and complex blocks to be added.

#4 @swissspidy
2 years ago

  • Milestone changed from Awaiting Review to Future Release

This becomes more relevant when there's gonna be a "Posts Page" block at some point. Moving to Future Release.

#5 @swissspidy
22 months ago

#47198 was marked as a duplicate.

#6 @Fantasy1125
22 months ago

@swissspidy In our agency we have a lot of these use cases as well. Archive pages need to have a certain amount of content to rank good in Google to improve the SEO. Almost all of our clients need this kind of functionality. We would really appreciate that this patch would be merged.

#7 @gchtr
22 months ago

I can only agree with @hannahmalcolm and @Fantasy1125.

We recently added our own archive block that can be used on any page that acts as a post type archive. This way, our clients can add blocks before and after the archive output. It works for all custom post types, but without this patch, we can’t make it work for the posts page without first adding some dummy text to make the switch to the Block Editor. We would love to see this patch being merged soon.

#8 @ArnaudBan
16 months ago

My use case :

I use a filter on 'editor.PostFeaturedImage' to add more option related to the featured image. It works nice but not on the posts page because it doesn't use the block editor like all the other pages of the site.

Note: See TracTickets for help on using tickets.