Opened 11 years ago
Closed 3 weeks ago
#33743 closed defect (bug) (fixed)
Theme location x Menu location
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 7.0 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Menus | Keywords: | has-patch commit |
| Focuses: | ui-copy | Cc: |
Description
We are using "Theme Location" and "Theme locations" in admin menu page (and also many help text sentences).
But Customizer uses "Menu locations" and "Menu Locations".
I am not sure what is better, but it should be same.
Attachments (5)
Change History (17)
#2
@
11 years ago
I found 75 instances of menu location(s), menu-location(s) in the codebase (documentation, css, js, code).
vs
22 instances of theme location(s), theme-location(s).
Does it still make sense to pick "Theme locations", and in cases like this one do we leave the code alone and only update the documentation?
#4
@
3 years ago
- Milestone set to Future Release
Another string: the Menus admin page uses "Display location" when editing a menu, which has confused translators (#58629).
#5
@
3 years ago
- Focuses ui-copy added
- Keywords has-patch needs-copy-review added; needs-patch removed
I think the help text could be better than what the patch has, but it's a start.
#6
@
4 months ago
Is this ticket still valid? What is the "help text [that] could be better] @sabernhardt ?
@
4 months ago
Manage Locations tab, with new text (from patch) underlined, both in the Overview help text and in the table header
#8
@
4 months ago
I agree with your text changes, @sabernhardt -- it's definitely more clear to say "theme menu." And I do remember that being an issue for me when I started using native themes instead of Beaver Builder.
#9
@
4 months ago
- Milestone changed from Future Release to 7.0
I'll mark this for consideration in 7.0 then. I might create a pull request, with the same changes, if that could make it easier to review than the .diff.
#11
@
3 weeks ago
- Keywords commit added; needs-copy-review removed
I think this makes a lot of sense. Keeping the language we use to talk about user interfaces consistent is always helpful. I think "Menu Locations" is generally clearer, as it is the object being placed being used as the subject.
In my opinion, this is commit-ready.
We're already pretty standardized on "theme locations" in documentation, and as you said, the help tabs, so I'd go with "Theme Locations".