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
If a posts page has been added as a static page (see instructions/screenshot below) the respective menu item should include required menu classnames like current-menu-item.
Step-by-step reproduction instructions
Open Settings > Reading and select "Your homepage displays a static page"
Select a "Homepage" (e.g. Home) and a "Posts page" (e.g. News)
Install a FSE Theme (e.g. TwentyTwentyTwo)
Edit site and add a new navigation with the custom links "Home" and "News"
Open the frontend and access "News".
The menu item class is missing current-menu-item (Home works as expected!)
Screenshots, screen recording, code snippet
News: Missing "current-menu-item" class
Home: Ok
Environment info
WordPress 5.8.2 (+ Gutenberg 12.2.0) OR WordPress 5.9 (RC 1)
TwentyTwentyTwo Theme
Chrome/Firefox (latest versions)
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered:
them-es
changed the title
Full Site Editing Navigation: Menu item for "Posts page" is missing required class if added as static page
FSE Navigation block: Menu item for "Posts page" is missing required class if added as static page
Dec 30, 2021
Description
If a posts page has been added as a static page (see instructions/screenshot below) the respective menu item should include required menu classnames like
current-menu-item
.Step-by-step reproduction instructions
Settings > Reading
and select "Your homepage displays a static page"current-menu-item
(Home works as expected!)Screenshots, screen recording, code snippet
News: Missing "current-menu-item" class
Home: Ok
Environment info
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes
The text was updated successfully, but these errors were encountered: