Skip to content

Conversation

@vidushigupta0607
Copy link

@vidushigupta0607 vidushigupta0607 commented Jun 30, 2025

Problem
Several external links within WordPress admin setting pages—specifically General, Discussion, and Permalink—currently open in the same window. This behavior can negatively impact the user experience in the following ways:

Users may lose unsaved changes if they click an external link without first saving their settings.

Users may assume the link opens in a new tab (as is the case with links in the Edit Profile page or the Help tab), and unintentionally navigate away from the page.

Inconsistencies in link behavior across admin pages create confusion and a fragmented user experience.

Root Cause
Some documentation/help links in the admin settings screens do not include target="_blank". This leads to an inconsistent user interface where users cannot predict link behavior.

Solution
Update external documentation/help links in affected settings pages to:

  • Include target="_blank" so they open in a new tab.

This aligns their behavior with other similar links in the admin UI, prevents data loss from navigation, and improves overall consistency and UX.

Trac ticket: https://core.trac.wordpress.org/ticket/23432

@github-actions
Copy link

github-actions bot commented Jun 30, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props vidugupta.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link

Hi @vidushigupta0607! 👋

Thank you for your contribution to WordPress! 💖

It looks like this is your first pull request to wordpress-develop. Here are a few things to be aware of that may help you out!

No one monitors this repository for new pull requests. Pull requests must be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description.

Pull requests are never merged on GitHub. The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making.

More information about how GitHub pull requests can be used to contribute to WordPress can be found in the Core Handbook.

Please include automated tests. Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the Automated Testing page in the handbook.

If you have not had a chance, please review the Contribute with Code page in the WordPress Core Handbook.

The Developer Hub also documents the various coding standards that are followed:

Thank you,
The WordPress Project

@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@vidushigupta0607
Copy link
Author

The account has been linked now!

@vidushigupta0607 vidushigupta0607 force-pushed the track-23432-open-links-in-new-tab branch from 30bf468 to 9190dcf Compare June 30, 2025 06:09
printf(
/* translators: %s: Documentation URL. */
__( 'Enter the same address here unless you <a href="%s">want your site home page to be different from your WordPress installation directory</a>.' ),
__( 'Enter the same address here unless you <a href="%s" target=_blank>want your site home page to be different from your WordPress installation directory</a>.' ),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
__( 'Enter the same address here unless you <a href="%s" target=_blank>want your site home page to be different from your WordPress installation directory</a>.' ),
__( 'Enter the same address here unless you <a href="%s" target="_blank">want your site home page to be different from your WordPress installation directory</a>.' ),

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants