WordPress.org

Make WordPress Core

Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#20598 closed defect (bug) (fixed)

WP.org menu is different when on Codex page(s)

Reported by: DrewAPicture Owned by:
Milestone: WordPress.org Priority: normal
Severity: minor Version:
Component: WordPress.org site Keywords:
Focuses: Cc:

Description

Jumping into and out of the Docs tab on WP.org today, it occurred to me the main tabs menu when on Codex pages is the (old?) design where Themes and Plugins were sub-menus of Extend.

To reproduce: Visit WP.org, note the main menu is 11 items across. Navigate to Docs, it's now down to 9 across with 2 sub-menus.

Attachments (2)

20598.logged-out.png (32.4 KB) - added by SergeyBiryukov 3 years ago.
20598.logged-in.png (33.3 KB) - added by SergeyBiryukov 3 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 follow-up: @helenyhou3 years ago

I'm seeing the new menu and such in the Codex, although the Home item is highlighted instead of Docs.

comment:2 in reply to: ↑ 1 @DrewAPicture3 years ago

Replying to helenyhou:

I'm seeing the new menu and such in the Codex, although the Home item is highlighted instead of Docs.

Once I logged in to the Codex, I got this too. The problem I described before was as a logged-out user. Seems like both scenarios are wonky.

comment:3 @SergeyBiryukov3 years ago

  • Milestone changed from Awaiting Review to WordPress.org

the main tabs menu when on Codex pages is the (old?) design where Themes and Plugins were sub-menus of Extend.

I see the same when logged out. (20598.logged-out.png). When logged in, all 11 items are displayed in the same old layout, which breaks it (20598.logged-in.png).

When I change wp4.css?10 in the page source to wp4.css?20 (as on Home page) with Firebug, everything looks OK.

I once had a similar issue with WP.org header menu in all sections, not just in Codex (could reproduce on several systems and even on some browsershots.org screenshots):
https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2012-01-13&sort=asc#m353192
https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2012-01-13&sort=asc#m353242

After discussing that with Otto, it seemed to be some kind of an upstream proxy issue, which sorted itself out in a month or so (during that month I used Proxomitron to alter the link to wp4.css locally).

comment:4 @nacin3 years ago

We've requested a deploy which should fix this.

comment:5 @nacin3 years ago

  • Resolution set to fixed
  • Status changed from new to closed

Should be fixed. Please re-open if it is not resolved.

comment:6 @SergeyBiryukov3 years ago

Looks fixed indeed.

Note: See TracTickets for help on using tickets.