You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When inserting a "Latest posts" block in a post, it displays also the "host" post if it's recent enough:
This doesn't seem particularly useful. While the classic Recent Posts widget is typically used in a sidebar and thus it's correct it displays all the recent posts, the Latest Posts block (aside: why it has a different name: Recent vs. Latest?) is used in the post content and should exclude the "host" post when this is in the recent ones.
Additionally, when inserting the Latest Posts block in Gutenberg:
create a new post
don't save the post yet
insert a Latest Posts block
the "host" post is not included (because it's still a draft):
save
refresh the page
now the host posts is listed
This mix of different behaviors can be confusing for users and should probably be improved a bit.
The text was updated successfully, but these errors were encountered:
If we were to add this feature, we should consider the fact that this block could be used in a page or a site builder later (the same block) and there's no host post.
I think the way forward here is to support some or all of the REST API's query parameters and automatically include ?exclude=ID for the current post ID.
When inserting a "Latest posts" block in a post, it displays also the "host" post if it's recent enough:
This doesn't seem particularly useful. While the classic Recent Posts widget is typically used in a sidebar and thus it's correct it displays all the recent posts, the Latest Posts block (aside: why it has a different name: Recent vs. Latest?) is used in the post content and should exclude the "host" post when this is in the recent ones.
Additionally, when inserting the Latest Posts block in Gutenberg:
This mix of different behaviors can be confusing for users and should probably be improved a bit.
The text was updated successfully, but these errors were encountered: