WordPress.org

Make WordPress Core

Opened 2 years ago

Closed 5 months ago

#47235 closed defect (bug) (fixed)

i18n: "Back to..." vs. "Return to..."

Reported by: ramiy Owned by: SergeyBiryukov
Milestone: 5.6 Priority: low
Severity: minor Version:
Component: Administration Keywords: has-patch commit
Focuses: administration Cc:

Description

In WordPress dashboard some pages have links at the bottom of the screen linking back other screen pages.

The wording is inconsistent, in some cases the we use "Back to..." in other cases we use "Return to..."

Check those links:

Note: some of those strings has "←" char prefix, other use "←" char, but most don't use any prefix.

We need to set a standard.

Attachments (6)

47235.patch (979 bytes) - added by ramiy 2 years ago.
47235.2.patch (796 bytes) - added by ramiy 2 years ago.
47235.3.diff (1.8 KB) - added by audrasjb 15 months ago.
Refreshed and unified patch.
47235.4.diff (20.4 KB) - added by kharisblank 15 months ago.
Replace "Return to" and "Back to" with "Go to"
47235.5.diff (21.5 KB) - added by garrett-eclipse 7 months ago.
Refreshed patch
47235.6.diff (20.2 KB) - added by garrett-eclipse 7 months ago.
Refresh to remove unintended qunit string changes

Download all attachments as: .zip

Change History (23)

#1 @ramiy
2 years ago

Also, some screen use "Go to..." see here.

@ramiy
2 years ago

#2 @ramiy
2 years ago

  • Keywords has-patch added

The first patch merges similar translation strings. Replacing "Go to..." with "Return to..." strings.

@ramiy
2 years ago

This ticket was mentioned in Slack in #core-i18n by ramiy. View the logs.


16 months ago

#4 @SergeyBiryukov
16 months ago

  • Milestone changed from Awaiting Review to 5.4

@audrasjb
15 months ago

Refreshed and unified patch.

#5 follow-up: @garrett-eclipse
15 months ago

Hi @audrasjb thanks for the refresh, reviewing I see you've updated the 'Go to the Themes/Plugins screen' strings in the paused_themes/plugins_notice functions. To my understanding these notices will take over their respective screens before you even get to view the Themes/Plugins screens so the term 'Return' could be incorrect/misleading as you weren't previously on those pages. To me 'Go to the' is more valid for both the cases where they were on the screen before hand and some where they were coming to the screen for the first time but instead got this notice.

I hope that makes sense, and I could be wrong. If the only way those notices appear are if you start on the Themes/Plugins screen first then I guess the change is valid in that case.

#6 in reply to: ↑ 5 @ramiy
15 months ago

Replying to garrett-eclipse:

Hi @audrasjb thanks for the refresh, reviewing I see you've updated the 'Go to the Themes/Plugins screen' strings in the paused_themes/plugins_notice functions. To my understanding these notices will take over their respective screens before you even get to view the Themes/Plugins screens so the term 'Return' could be incorrect/misleading as you weren't previously on those pages. To me 'Go to the' is more valid for both the cases where they were on the screen before hand and some where they were coming to the screen for the first time but instead got this notice.

I hope that makes sense, and I could be wrong. If the only way those notices appear are if you start on the Themes/Plugins screen first then I guess the change is valid in that case.

I agree.

@kharisblank
15 months ago

Replace "Return to" and "Back to" with "Go to"

#7 @valentinbora
14 months ago

  • Keywords dev-feedback added
  • Priority changed from normal to low
  • Severity changed from normal to minor

#8 @valentinbora
14 months ago

  • Keywords needs-refresh added

@kharisblank thanks for the patch update.

It looks like for the most part, it applies cleanly, with one exception in src/wp-admin/includes/class-plugin-installer-skin.php

I've tested it (non-exhaustively) for a Plugin update and it does the job.

Please refresh the patch for the ticket to move forward.

#9 @audrasjb
14 months ago

  • Milestone changed from 5.4 to Future Release

Hi,

With 5.4 Beta 3 approaching and the Beta period reserved for bugs introduced during the cycle, this is being moved to Future Release. If any maintainer or committer feels this should be included or wishes to assume ownership during a specific cycle, feel free to update the milestone accordingly.

@garrett-eclipse
7 months ago

Refreshed patch

#10 @garrett-eclipse
7 months ago

  • Keywords needs-testing added; needs-refresh removed
  • Milestone changed from Future Release to 5.6

Hello, I've refreshed the patch in 47235.5.diff to address the parts that didn't apply cleanly as well as to add the newer 'Return to top' string found in privacy-tools.php to the mix.

@valentinbora @ramiy @SergeyBiryukov please do a final review/test and we'll see if this can make 5.6.

#11 @audrasjb
7 months ago

Thank you @garrett-eclipse, you rock! The patch looks good to me.

#12 @audrasjb
7 months ago

  • Keywords commit added; dev-feedback needs-testing removed

Adding commit workflow keyword

#13 @ramiy
7 months ago

@garrett-eclipse your patch has unrelated string fixes for API qunit tests.

@garrett-eclipse
7 months ago

Refresh to remove unintended qunit string changes

#14 @garrett-eclipse
7 months ago

Good catch thanks @ramiy I noticed that on a different patch and fixed in #50805 which is now in trunk so shouldn't see that come up again. Refreshed to remove them in 47235.6.diff.

#15 @audrasjb
5 months ago

  • Keywords commit removed

I tested the patch and good news: it still applies cleanly against trunk.
That looks ready to go in my opinion. Marking for commit.

#16 @audrasjb
5 months ago

  • Keywords commit added

#17 @SergeyBiryukov
5 months ago

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

In 49539:

Text Changes: Unify various "Back to..." vs. "Return to..." vs. "Go to..." strings.

Standardize on "Go to..." as a more appropriate option for most cases.

Props garrett-eclipse, kharisblank, audrasjb, ramiy, valentinbora.
Fixes #47235.

Note: See TracTickets for help on using tickets.