Project

General

Profile

Actions

Support #11509

closed

deleted Page causing a Menu problem?

Added by Marilyn Weber almost 5 years ago. Updated about 1 year ago.

Status:
Abandoned
Priority name:
Normal
Assignee:
-
Category name:
-
Target version:
Start date:
2019-06-02
Due date:
% Done:

0%

Estimated time:
Deployment actions:

Description

Matt Conlin, the admin of https://jtds.commons.gc.cuny.edu, noticed that the word "current" mysteriously appears next to one of the three menu items at the top of the screen ( "Introducing JTDS"). I think I can see why - it looks like "Introducing JTDS" was given as a Page title twice. If you look at Appearance, then Menus, and select View All under Pages, it's listed once with a submenu of "Sections of the Journal") then again further down.

But when I look at the Pages, I can't find the original "Introducing JTDS" to remove it. See screenshots.

Can you see it and make it visible to me? Or do I have the wrong end of the stick entirely? Thanks!


Files

again as menu item.JPG (32.8 KB) again as menu item.JPG Marilyn Weber, 2019-06-02 08:28 PM
top menu item.JPG (93 KB) top menu item.JPG Marilyn Weber, 2019-06-02 08:28 PM
pages.JPG (122 KB) pages.JPG Marilyn Weber, 2019-06-02 08:31 PM
Actions #1

Updated by Boone Gorges almost 5 years ago

  • Status changed from New to Reporter Feedback
  • Target version set to Not tracked

This is a bug, but you've misdiagnosed the cause - it's related to deleted pages or duplicate page titles.

The issue is the WP Accessibility plugin, which is adding the "(current)" text to the nav item. It's doing it using the screen-reader-text selector, which is used by WP to hide content from anyone not using a screen reader. The problem is that the plugin doesn't actually provide the styles necessary to hide the content.

It appears that this behavior will change in the next update to WP Accessibility, which will be part of our Jun 11 release. https://github.com/joedolson/wp-accessibility/commit/4e5a69fbd8a6f11db7b0c31fa416f0ab110ea9ab

In the meantime, if the user would prefer not to wait, the following in the Dashboard's custom CSS area should fix the problem:

.screen-reader-text {
  border: 0;
  clip: rect(1px, 1px, 1px, 1px);
  clip-path: inset(50%);
  height: 1px;
  margin: -1px;
  overflow: hidden;
  padding: 0;
  position: absolute !important;
  width: 1px;
  word-wrap: normal !important;
}
Actions #2

Updated by Marilyn Weber almost 5 years ago

Thank you!

Actions #3

Updated by Boone Gorges about 1 year ago

  • Status changed from Reporter Feedback to Abandoned
Actions

Also available in: Atom PDF