Bug - theming assets links broken (404)

[nfee006]

Describe the bug

Multiple theming elements referenced in the static-header-footer are unavailable (404) as of approximately 16h EST on 10/03/2021.
Files affected:

• https://wet-boew.github.io/themes-dist/GCWeb/assets/favicon.ico
• https://wet-boew.github.io/themes-dist/GCWeb/css/theme.min.css
• https://wet-boew.github.io/themes-dist/GCWeb/js/theme.min.js
• https://wet-boew.github.io/themes-dist/GCWeb/wet-boew/js/i18n/.min.js
• https://wet-boew.github.io/themes-dist/GCWeb/assets/sig-blk-en.svg
• https://wet-boew.github.io/themes-dist/GCWeb/assets/wmms-blk.svg

To Reproduce

Steps to reproduce the behavior:

1. Go to https://github.com/wet-boew/GCWeb/blob/db8f99ce9d1f8f58a58771269fa18d0b5c995a8a/site/pages/gcweb-theme/static-header-footer/bootstrap-3.html
2. Locate the links for the files mentioned above.
3. Notice the 404 status message when you navigate to them.

Alternatively,

1. Access a site that makes use of the Bootstraps 3 header/footer. I am not aware of any ones that are widely available though.

Example

The site in question is only available on my agency's intranet. As such, I cannot provide a useable link.

Current behavior

Theming elements are not accessible. The most notable issue is that, without the CSS, the theme menu is unstyled and takes up most of the page.

Expected behavior

The expected behaviour would be that the theming elements load (unless there has been a major update that I am not aware of?).

Screenshots and/or logs

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10, Ubuntu 16.04
• Browser: Chrome, IE, Firefox
• Version:

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser: [e.g. stock browser, safari]
• Version: [e.g. 22]

Additional context

I am not a web developer and am very open to other solutions if they exist. I do have the GCWeb theme downloaded locally but it's not clear if that's the best solution.

[RobJohnston]

Linking for posterity: wet-boew/wet-boew#9060

[anthonyfok]

We have some live Internet examples showing the breakage due to GCWeb theme assets links now 404 (though we will be fixing our websites with local assets later today):

• https://opendrr.github.io/
  • (web archive: http://web.archive.org/web/20210311232647/https://opendrr.github.io/)
• https://opendrr.github.io/data/en/
  • (web archive: http://web.archive.org/web/20210311233820/https://opendrr.github.io/data/en/)

Please keep backward compatibility in mind, preferably as the topmost priority,
whenever you change things,
like how popular dependencies like jQuery and Bootstrap
keep all of their new and old versions on CDN for posterity so as not to break websites.

Another thing I would highly suggest is to have end users host the GCWeb assets on their own servers
instead of relying on https://wet-boew.github.io/themes-dist/GCWeb/, which, in this case, becomes a single point of failure.
Maybe this is already being implemented in your new restructuring, but if not, please consider this and other ways to make GCWeb more resilient and immune to such 404 breakage.

Many thanks!

Related issue: wet-boew/gcweb-jekyll#21

[anthonyfok]

In retrospect, perhaps the root issue lies with assumptions made in gcweb-jekyll?
See wet-boew/gcweb-jekyll#23

[duboisp]

I confirm this broken link was introduced when we have made recent changes to our continuous deployment script from travis-ci to github action, in the preparation of the GCWeb release v9.2.0.

An immediate and permanent solution will be to add the missing folder name "GCWeb" for the base URL. Example:

• https://wet-boew.github.io/themes-dist/GCWeb/GCWeb/css/theme.min.css
• https://wet-boew.github.io/themes-dist/GCWeb/GCWeb/js/theme.min.js

Those URL / files locations are not in scope of our Public API according to : https://wet-boew.github.io/wet-boew-documentation/decision/3.html

I will fix the broken link into the source file: /site/pages/gcweb-theme/static-header-footer/bootstrap-3.html along with the PR: #1784

You are free to submit a PR that will re-introduce those folder into the GCWeb "dist" by updating the continuous deployment script here: https://github.com/wet-boew/GCWeb/blob/master/.github/workflows/cd.yml