Closed TroyCMSSupport closed 1 month ago
@omahane @ian-sears @jilladams - This is ready for URL Redirect - Facility name has already changed
The destination URL 404s: https://www.va.gov/north-florida-health-care/locations/jacksonville-north-va-clinic/
The Drupal node for that URL doesn't exist: https://prod.cms.va.gov/north-florida-health-care/locations/jacksonville-north-va-clinic/
The live page for Jacksonville North VA clinic is: https://www.va.gov/north-florida-health-care/locations/jacksonville-southpoint-va-clinic/ with North in the H1
The URL alias is set to /north-florida-health-care/locations/jacksonville-southpoint-va-clinic in the Drupal node: https://prod.cms.va.gov/node/1581/edit
Do we need to actually update the URL alias, before publishing a devops redirect?
The redirect has been deployed.
@omahane noting, when I click the old URL https://www.va.gov/north-florida-health-care/locations/jacksonville-southpoint-va-clinic/, I get a 404 not a redirect. True on the Tulare one too. I do see the deploy today contained your commits, and went out 4 hours ago - should definitely be working by now.
It's working now. This is a timing issue one way or another. Either the redirect goes first and deploys a URL that doesn't exist or we save the content and the release goes out with a URL that doesn't exist. We typically do the former.
Thank you @omahane @jilladams @ian-sears - I have confirmed the redirect, VA.gov locator, and Locations section of the main facility - all point to the correct / published page.
I had to reopen this because we have a canonical URL request out there: https://dsva.slack.com/archives/C02BTJTDFTN/p1721669125978809?thread_ts=1721421342.650609&cid=C02BTJTDFTN
CSV has been deployed, per Slack: https://dsva.slack.com/archives/C02BTJTDFTN/p1721421342650609
Confirmed rename is in place
Implementation date
When does this request need to be live: ASAP
Instructions for URL redirect
(Note: This issue will be used from initial request through implementation to ensure all individuals working on this are notified of status updates. Please do not create multiple issues to track different steps.)
ansible/deployment/config/revproxy-vagov/vars/redirects.yml
URL Redirect
Use one of the following:
1. Canonical URL change or
Note: Canonical URL changes do not block the completion of the parent ticket. Once the URL redirect above has been deployed, the value to the Veteran is delivered. This ticket should be kept open until the URL change is verified, except in the case of a removal (as described below).
Instructions for canonical URL change
URL change example (update with actual ID and URL)