Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix footer links #3149

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix footer links #3149

wants to merge 1 commit into from

Conversation

ChrisBAshton
Copy link
Contributor

These footer links have been broken since version 37.1.1 of govuk_publishing_components, which automatically converts all footer links to absolute URLs, using Plek.new.website_root: alphagov/govuk_publishing_components#3699

That corresponds to https://www.gov.uk on Production, but needs to be https://content-publisher.publishing.service.gov.uk.

No other publishing app passes custom links to the footer like Content Publisher does, so this appears to be the only app affected. With that in mind, the simplest fix is to specify the correct absolute URL rather than deferring to the component (as opposed to, say, changing the value of Plek.new.website_root, which may have unintended side-effects).

Tested in a Rails console on Production:

"#{Plek.external_url_for('content-publisher')}#{app.guidance_path}"
=> "https://content-publisher.publishing.service.gov.uk/documents/publishing-guidance"

⚠️ This repo is Continuously Deployed: make sure you follow the guidance ⚠️

Follow these steps if you are doing a Rails upgrade.

These footer links have been broken since version 37.1.1 of
govuk_publishing_components, which automatically converts all
footer links to absolute URLs, using `Plek.new.website_root`:
alphagov/govuk_publishing_components#3699

That corresponds to `https://www.gov.uk` on Production, but needs
to be `https://content-publisher.publishing.service.gov.uk`.

No other publishing app passes custom links to the footer like
Content Publisher does, so this appears to be the only app affected.
With that in mind, the simplest fix is to specify the correct
absolute URL rather than deferring to the component (as opposed to,
say, changing the value of `Plek.new.website_root`, which may have
unintended side-effects).

Tested in a Rails console on Production:

```
"#{Plek.external_url_for('content-publisher')}#{app.guidance_path}"
=> "https://content-publisher.publishing.service.gov.uk/documents/publishing-guidance"
```
@ChrisBAshton ChrisBAshton requested a review from AshGDS May 29, 2024 08:27
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.

None yet

1 participant