Build: Post-Processing of Custom 404 Page Makes Bundled Resource URLs Relative

[seandstewart]

Describe the bug

The post-processing of custom 404 pages results in the links to static resources being stripped of their leading /, resulting in a broken page.

You can see it live here: https://python-typical.org/usage/foo

As illustrated in this community post:

Note that the resources are all relative: <link rel="stylesheet" href="assets/stylesheets/application.adb8469c.css">,

Whereas when I build locally, the resources are absolute: <link rel="stylesheet" href="/assets/stylesheets/application.adb8469c.css">

Configuration

• You can see a relevant TOML here: https://github.com/seandstewart/typical/blob/master/netlify.toml
• I ran the build(s) through the UI.

Deploy logs

https://app.netlify.com/sites/typical-python/deploys/5f42d511848e3d5cea1f31ef

Note: I’m referencing one site in this issue, but this appears to be affecting all of my sites, currently. Additionally, I’ve interacted with other users experiencing this same issue.

Referencing issue: https://github.com/squidfunk/mkdocs-material/issues/1878

[ehmicky]

Hi @seandstewart,

Thanks for reaching out!
This repository is not directly involved in post-processing. However, I have transferred the bug description to the team working on this feature, so we can keep this issue to track the progress of solving this problem.

[seandstewart]

Thanks for the triage, @ehmicky!

[seandstewart]

@ehmicky sorry to bother, but has there been any progress made on this particular issue? Is there a separate issue tracker I can follow so I'm not bugging the wrong team?

[ehmicky]

Hi @seandstewart,

Thanks for following up. Unfortunately not. We'll keep you updated as soon as this is fixed!