Skip to content
This repository has been archived by the owner on Apr 13, 2022. It is now read-only.

(Some) documentation website is broken #17111

Closed
heidemn-faro opened this issue Feb 5, 2021 · 2 comments
Closed

(Some) documentation website is broken #17111

heidemn-faro opened this issue Feb 5, 2021 · 2 comments
Assignees

Comments

@heidemn-faro
Copy link

heidemn-faro commented Feb 5, 2021

https://docs.angularjs.org/guide/directive

Runtime nodejs6 is no longer available. Please redeploy your function to a newer version.

EDIT: Okay sorry, this seems to be an outdated doc website URL.
New URL: https://code.angularjs.org/1.6.10/docs/guide/directive

However, your own company's search engine directed me there ;-)
Maybe improve your SEO?

image

@heidemn-faro heidemn-faro changed the title (!) Documentation website is broken (Some) documentation website is broken Feb 5, 2021
@rasmuslp
Copy link

rasmuslp commented Feb 5, 2021

To me, it looks like anything other than the front-page of https://angularjs.org is broken. Please fix. Docs shouldn't be hard to find on the official page.

@gkalpak gkalpak self-assigned this Feb 5, 2021
gkalpak added a commit to gkalpak/angular.js that referenced this issue Feb 5, 2021
Previously, we only deploy to Firebase hosting for the
`docs-angularjs-org` Firebase project. This meant that the eployed
functions used an old version of Node.js and started failing once
support was dropped for that version. See angular#17111 for details.

This commit fixes this by ensuring that we deploy to all enabled
Firebase services (currently functions and hosting).

Fixes angular#17111
Fixes angular/angularjs.org#251
@gkalpak
Copy link
Member

gkalpak commented Feb 5, 2021

Thx for reporting this @heidemn-faro et al.

https://docs.angularjs.org/guide/directive is actually the right URL (not an outdated one).

The issue should have been fixed now.
I am also working on PR to prevent the error in future deployments. (UPDATE: #17114)

gkalpak added a commit to gkalpak/angular.js that referenced this issue Feb 5, 2021
Previously, we only deployed to Firebase hosting for the
`docs-angularjs-org` Firebase project. This meant that the deployed
functions used an old version of Node.js and started failing once
support was dropped for that version. See angular#17111 for details.

This commit fixes this by ensuring that we deploy to all enabled
Firebase services (currently functions and hosting).

Fixes angular#17111
Fixes angular/angularjs.org#251
gkalpak added a commit to gkalpak/angular.js that referenced this issue Feb 6, 2021
Previously, we only deployed to Firebase hosting for the
`docs-angularjs-org` Firebase project. This meant that the deployed
functions used an old version of Node.js and started failing once
support was dropped for that version. See angular#17111 for details.

This commit fixes this by ensuring that we deploy to all enabled
Firebase services (currently functions and hosting).

Fixes angular#17111
Fixes angular/angularjs.org#251
@gkalpak gkalpak closed this as completed in c7d68fa Feb 6, 2021
gkalpak added a commit that referenced this issue Feb 6, 2021
Previously, we only deployed to Firebase hosting for the
`docs-angularjs-org` Firebase project. This meant that the deployed
functions used an old version of Node.js and started failing once
support was dropped for that version. See #17111 for details.

This commit fixes this by ensuring that we deploy to all enabled
Firebase services (currently functions and hosting).

Fixes #17111
Fixes angular/angularjs.org#251
AnkushLambdatest pushed a commit to AnkushLambdatest/angular.js that referenced this issue Jun 29, 2022
Previously, we only deployed to Firebase hosting for the
`docs-angularjs-org` Firebase project. This meant that the deployed
functions used an old version of Node.js and started failing once
support was dropped for that version. See angular#17111 for details.

This commit fixes this by ensuring that we deploy to all enabled
Firebase services (currently functions and hosting).

Fixes angular#17111
Fixes angular/angularjs.org#251
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants