Skip to content

Fix title in redirection page#22470

Merged
vraja-pro merged 8 commits intorelease/25.7from
2455-257---trivial---page-name-in-the-browser-tab-is-not-proper-for-redirects-page
Aug 1, 2025
Merged

Fix title in redirection page#22470
vraja-pro merged 8 commits intorelease/25.7from
2455-257---trivial---page-name-in-the-browser-tab-is-not-proper-for-redirects-page

Conversation

@leonidasmi
Copy link
Copy Markdown
Contributor

@leonidasmi leonidasmi commented Jul 31, 2025

Context

Summary

This PR can be summarized in the following changelog entry:

  • Fixes an unreleased bug where the title of the redirections page would be incorrectly showing double the word Redirects.

Relevant technical choices:

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

  • With Premium disabled, go to Yoast->Redirects
  • Confirm that the title in the tab is the expected one, Redirects - Yoast SEO < <SITE TITLE> - WordPress, which the same format with all Yoast pages:
image
  • Regression: Go to the settings page and confirm that the title in the tab remains the same with what it was before this PR/RC.
    • Test with a couple of subsettings page, to make sure the title gets updated accordingly.
  • Activate Premium and go to Yoast->Redirects
  • Visit all 3 subpages there and confirm that the title in the tab gets the proper value:
    • Redirects - Yoast SEO < <SITE TITLE> - WordPress for the redirects subpage
    • Regex redirects < Redirects - Yoast SEO < <SITE TITLE> - WordPress for the regex redirects subpage
    • Redirect Method < Redirects - Yoast SEO < <SITE TITLE> - WordPress for the redirect method subpage

Relevant test scenarios

  • Changes should be tested with the browser console open
  • Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
  • Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
  • Changes should be tested on different browsers
  • Changes should be tested on multisite

Test instructions for QA when the code is in the RC

  • QA should use the same steps as above.

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

  • Like said above, regression test the title in the settings subpages.

UI changes

  • This PR changes the UI in the plugin. I have added the 'UI change' label to this PR.

Other environments

  • This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.

Documentation

  • I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

  • I have tested this code to the best of my abilities.
  • During testing, I had activated all plugins that Yoast SEO provides integrations for.
  • I have added unit tests to verify the code works as intended.
  • If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
  • I have written this PR in accordance with my team's definition of done.
  • I have checked that the base branch is correctly set.

Innovation

  • No innovation project is applicable for this PR.
  • This PR falls under an innovation project. I have attached the innovation label.
  • I have added my hours to the WBSO document.

Fixes #

@leonidasmi leonidasmi added the changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog label Jul 31, 2025
@leonidasmi leonidasmi added this to the 25.7 milestone Jul 31, 2025
@coveralls
Copy link
Copy Markdown

coveralls commented Jul 31, 2025

Pull Request Test Coverage Report for Build 4d76121a776689a34144ff7fd9ea71b2b52317c8

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

Details

  • 7 of 18 (38.89%) changed or added relevant lines in 5 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall first build on 2455-257---trivial---page-name-in-the-browser-tab-is-not-proper-for-redirects-page at 30.628%

Changes Missing Coverage Covered Lines Changed/Added Lines %
packages/js/src/redirects/components/route-layout.js 0 1 0.0%
packages/js/src/settings/components/route-layout.js 0 1 0.0%
packages/js/src/initializers/settings-store.js 0 3 0.0%
packages/js/src/shared-admin/store/document-title.js 6 12 50.0%
Totals Coverage Status
Change from base Build 24f6f53158f649005d90b2e54ecc87f7173e903a: 30.6%
Covered Lines: 4892
Relevant Lines: 14868

💛 - Coveralls

@leonidasmi leonidasmi marked this pull request as ready for review August 1, 2025 08:30
@leonidasmi leonidasmi force-pushed the 2455-257---trivial---page-name-in-the-browser-tab-is-not-proper-for-redirects-page branch from dd3547f to d3ffd01 Compare August 1, 2025 08:37
Copy link
Copy Markdown
Contributor

@vraja-pro vraja-pro left a comment

Choose a reason for hiding this comment

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

CR and AC ✅

@vraja-pro vraja-pro merged commit 4eddde3 into release/25.7 Aug 1, 2025
18 checks passed
@vraja-pro vraja-pro deleted the 2455-257---trivial---page-name-in-the-browser-tab-is-not-proper-for-redirects-page branch August 1, 2025 14:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

changelog: non-user-facing Needs to be included in the 'Non-userfacing' category in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants