Making WordPress.org

Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#5180 closed defect (bug) (fixed)

Design issue in support article sidebar unordered list

Reported by: makewebbetter's profile makewebbetter Owned by:
Milestone: Priority: normal
Component: HelpHub (wordpress.org/documentation) Keywords:
Cc:

Description

I was reading an article so I seen this issue in Topics sidebar where all topics hyperlink were added.
Here is the screenshot - https://www.dropbox.com/s/hs99ssw9w0iiq61/issue-in-article.png
And here is the page URL where i saw the issue - https://wordpress.org/support/article/optimization/

Change History (5)

#1 @dufresnesteven
5 years ago

  • Component changed from General to Handbooks
  • Keywords needs-design removed

@makewebbetter Thanks for reporting the issue!

The <li> appears to have lept out of the <ul>!

#2 @coffee2code
5 years ago

  • Component changed from Handbooks to HelpHub
  • Resolution set to fixed
  • Status changed from new to closed

This ended up being a content problem with the article in question, which is now fixed.

FYI: I switched the component for this to HelpHub since it pertains to one its articles, which are a custom post type with a handbook-like table of contents, though none of it utilizes the handbook plugin.

Details: The "Hosting" heading (anh3), below the first content heading "Performance factors" (an h2) had a manually assigned HTML anchor of "hosting" set. The regex for finding in-content headings essentially looks strictly for bare heading tags without accounting for attributes. So Hosting's manual attribute kept it from being detected, which threw off the inferred hierarchy of headings. Removing the HTML anchor fixed the issue. (The headings all get auto-assigned an anchor via the ToC code anyhow, so the manual assignment wasn't necessary.)

#3 @coffee2code
5 years ago

  • Milestone Improved Search deleted

#4 @dufresnesteven
5 years ago

@coffee2code Great. Thanks for the learn up!

#5 @makewebbetter
5 years ago

@coffee2code great issue solved.

Note: See TracTickets for help on using tickets.