Make WordPress Core

#59534 closed defect (bug) (reported-upstream)

Query Loop block: Page next to current one (mid_size control) is not visible

Reported by: nataliat2004's profile nataliat2004 Owned by:
Milestone: Priority: normal
Severity: normal Version: 6.4
Component: General Keywords:
Focuses: Cc:

Description

  1. Install and activate WP 6.4 - Beta2 (Theme Twenty Twenty-Four)
  2. Add Query Loop block and ensure that Query Page Numbers block is displayed
  3. Check block settings

Actual result: 'Page next to current one' (mid_size control) is not visible https://monosnap.com/file/IBycGB5epadw3MtIekCERQTwweY4pa
Expected result: 'Page next to current one' should be visible.
Related to https://github.com/WordPress/gutenberg/pull/51216.

Attachments (1)

Monosnap File 2023-10-04 13-33-33.png (356.1 KB) - added by nataliat2004 21 months ago.

Download all attachments as: .zip

Change History (5)

This ticket was mentioned in Slack in #core-test by hardikgohil. View the logs.


21 months ago

#2 @hellofromTonya
21 months ago

  • Keywords reporter-feedback added

Hello @nataliat2004,

Welcome to WordPress Core's Trac :) Thank you for reporting this issue.

Sorry for the delay in responding to your ticket.

Can you please report this issue upstream in the Gutenberg repository? [https://github.com/WordPress/gutenberg/issues/new/choose Use this link to open a new issue report.

Once reported, please comment here in this Trac ticket with a link to the issue. Why? To bind / wire the two report together.

Once a new issue is opened (or found), then this Trac ticket can be closed as reported-upstream.

Why report in Gutenberg?
The editor's tools and UI are developed, fixed, and maintained in Gutenberg. Gutenberg releases these through publishing npm packages, which Core then consumes / uses.

How do the changes get into Core?
Once fixed and the npm packages released, then Core's package.json is updated, bringing in the latest packages.

#4 @hellofromTonya
20 months ago

  • Keywords reporter-feedback removed
  • Milestone Awaiting Review deleted
  • Resolution set to reported-upstream
  • Status changed from new to closed

Thank you @nataliat2004 for reporting it upstream and commenting back here to wire the two reports together. I'm closing this ticket.

Note: See TracTickets for help on using tickets.