Making WordPress.org

Opened 15 months ago

Closed 3 months ago

#6740 closed defect (bug) (reported-upstream)

Update to /documentation/ didn't redirect PHP and Site-Health Pages

Reported by: estelaris's profile estelaris Owned by:
Milestone: Priority: high
Component: HelpHub (wordpress.org/documentation) Keywords:
Cc:

Description

The link to the pages for PHP and Site-Health in the previous ?support/ site (now /documentation/) need to be updated/redirect?

Pages: https://wordpress.org/support/update-php/ and https://wordpress.org/support/site-health/

More info: https://meta.trac.wordpress.org/ticket/4004
https://make.wordpress.org/core/2019/01/14/php-site-health-mechanisms-in-5-1/
https://github.com/WordPress/wporg-documentation-2022/issues/48

That is all the information I found about these pages.

Change History (7)

This ticket was mentioned in Slack in #docs by estelaris. View the logs.


15 months ago

#2 @dd32
15 months ago

  • Keywords changes-requested removed

These pages are "special" as they're translated and available in every locale, eg https://de.wordpress.org/support/update-php/ (Even if the locale doesn't have a /support/ site, and the content is translated via GlotPress, not through the /support/ site admin)

It should be updated so as to be presented via /documentation/ but due to the hard-coded page content for translations, it's not as simple as copying the content over.

Last edited 15 months ago by dd32 (previous) (diff)

#3 @ryelle
15 months ago

The content can be moved over to a pattern in documentation, but those translations won't actually be used since the Rosetta sites use the wporg-support theme. This would cause the content to be duplicated between the two themes, at least until the redesign is rolled out to Rosetta.

Would that work if the redirect only applied to the non-rosetta site?

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


15 months ago

#5 follow-up: @dd32
15 months ago

Would that work if the redirect only applied to the non-rosetta site?

Yep!

Are strings for the Documentation theme even being imported into GitHub anywhere yet? If not, there'll be no immediate duplicate strings to worry about.

The translations can be exported/imported between the projects when the time comes to enable it.

#6 in reply to: ↑ 5 @estelaris
13 months ago

Replying to dd32:

Are strings for the Documentation theme even being imported into GitHub anywhere yet? If not, there'll be no immediate duplicate strings to worry about.

There are no plans yet to move documentation strings into GH, so if redirects are only applied for non-Rosetta site, can we close this ticket?

#7 @estelaris
3 months ago

  • Resolution set to reported-upstream
  • Status changed from assigned to closed

moving this to the GH documentation issue tracker to follow up
[Issue 1446]https://github.com/WordPress/Documentation-Issue-Tracker/issues/1446

Note: See TracTickets for help on using tickets.