Forum Discussion

RogueScholar's avatar
RogueScholar
Occasional Contributor
1 hour ago

Download link broken for Firefox extension - Nightly Channel

So I'm busy setting up a new personal workstation, and being the middle-aged power user that I am, I've settled in comfortably with the Nightly releases of the various elements of 1Password software that I use. Sadly I was thwarted just now regarding downloading the Nightly release of the Firefox extension, as what I'm certain would be considered the "official" link to download the package leads to an HTTP 404 "File Not Found" error page. That struck me as highly out-of-character for 1P.

Steps to reproduce

  1. Begin at the "Browser extension" link in the Downloads section of the footer on all public-facing pages on 1Password.com. Canonical URL: https://1password.com/downloads/browser-extension
  2. Scroll to just above the footer on this one and click the "Join the Beta" button that links to the article on the support site with all of the details unsuitable for "normies." Canonical URL: 

    https://support.1password.com/betas/?windows#install-a-beta-release-of-the-1password-browser-extension

  3. Click on the link for "Firefox (nightly)," which a reasonable personal would expect to trigger a file transfer of the .xpi package containing the extension. Canonical URL: 

    https://c.1password.com/dist/1P/b5x/firefox/nightly/latest.xpi

  4. See a 404 error and wonder just how good the drugs are up in Canada, specifically the neighborhoods around the 1Password office, imagining they must be pretty spectacular. Then daydream about living a life that provides opportunities to enjoy them and also not get fired for oversights that lead to onboarding failures and a small (but still non-zero) amount of diminished regard for company/product. 😇

Alright, so that last one was thrown in just to needle you guys, because I know you can take it. This is a bit surprising though, even for a support page, to have a first-party download link for onboarding just not resolve at all. The filename is static, after all, so a pipeline failure to update the link target to a new build name wouldn't seem to be at issue. *shrugs*

I would've felt guilty if I just walked away without letting you know that things were awry, having been on the receiving end of one or two of those kinds of butt-chewing sessions by "the boss" earlier in my career and they're no fun, so that's why this thread exists. Also enclosed are my sincere hopes that by the time you're back in the office to read this, that the impulse to want to hold onto the carpet to keep from floating away has subsided. *snickers knowingly while simultaneously bringing his hand up to the side of his face in the universally recognized "call me" gesture* 😃

No RepliesBe the first to reply