canonical / canonical/ubuntu.com

Four redirects and one page image point at 404s

Open
#16,670 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
324
Forks
303
Avg merge
2d 21h
Merged PRs (30d)
52

Description

Ran a link checker I wrote over the repo and read every hit by hand. Five are still live problems, and four of them sit in redirects.yaml, so visitors hit them rather than editors

where target status
redirects.yaml:20LoCo/? http://loco.ubuntu.com/ 404
redirects.yaml:444developer/core/get-started/orange-pi-zero/? http://www.orangepi.org/downloadresources/ 404
redirects.yaml:540download/iot/orange-pi-zero/? same 404
redirects.yaml:628enterprise-canonical-kubernetes/? https://assets.ubuntu.com/v1/Enterprise-Canonical-Kubernetes.pdf 404
templates/internet-of-things/digital-signage.html:36 https://assets.ubuntu.com/v1/2c3ad93c-smart-displays-2.png 404

https://ubuntu.com/LoCo returns 404 today, so this is user facing rather than theoretical. The loco.ubuntu.com host itself redirects to https://ubuntu.com/community/docs/locos, which is also 404, so the destination is gone on both sides

So I have not opened a PR because each of these needs your intent rather than a mechanical fix. I cannot tell where LoCo or the Orange Pi Zero pages should point now, and I do not know which image digital-signage was meant to show. Tell me where you want them to go and I will send the change

Lower priority, mentioned for completeness: templates/shared/contextual_footers/_iot_for_developers.html links to http://developer.ubuntu.com/en/snappy/, which is dead, but that template is not included anywhere in the repo, so it may want deleting rather than fixing

All checked with curl following redirects and a browser user agent. Dead links inside the versioned charmed-k8s docs were left alone on purpose, since old doc versions are usually frozen

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the five entries listed in redirects.yaml and templates/internet-of-things/digital-signage.html, then review the reported curl results and the unused contextual footer template. Confirm the intended replacement destinations with a maintainer before editing. Done means the selected redirects and image URL resolve successfully, while any decision about the unused footer is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, yaml
Domain
web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.