Angular.js: Docs seem to be broken

Created on 23 Aug 2017  Â·  10Comments  Â·  Source: angular/angular.js

Most helpful comment

I think it's a caching problem (again)

There are two instances and one of them seems to be broken.

All 10 comments

Wow, I've been refreshing it for 5 mins. fixed 10 secs after opening the issue :joy:

I think it's a caching problem (again)

There are two instances and one of them seems to be broken.

I am getting this error in the console https://code.angularjs.org/snapshot/docs/error/$injector/modulerr?p0=docsApp&p1=Error:%20%5B$injector:modulerr%5D%20http:%2F%2Ferrors.angularjs.org%2F1.6.5%2F$injector%2Fmodulerr%3Fp0%3Ddeployment%26p1%3DError%253A%2520%255B%2524injector%253Anomod%255D%2520http%253A%252F%252Ferrors.angularjs.org%252F1.6.5%252F%2524injector%252Fnomod%253Fp0%253Ddeployment%250A%2520%2520%2520%2520at%2520https%253A%252F%252Fajax.googleapis.com%252Fajax%252Flibs%252Fangularjs%252F1.6.5%252Fangular.min.js%253A7%253A76%250A%2520%2520%2520%2520at%2520https%253A%252F%252Fajax.googleapis.com%252Fajax%252Flibs%252Fangularjs%252F1.6.5%252Fangular.min.js%253A26%253A408%250A%2520%2520%2520%2520at%2520b%2520(https%253A%252F%252Fajax.googleapis.com%252Fajax%252Flibs%252Fangularjs%252F1.6.5%252Fangular.min.js%253A25%253A439)%250A%2520%2520%2520%2520at%2520https%253A%252F%252Fajax.googleapis.com%252Fajax%252Flibs%252Fangularjs%252F1.6.5%252Fangular.min.js%253A26%253A182%250A%2520%2520%2520%2520at%2520https%253A%252F%252Fajax.googleapis.com%252Fajax%252Flibs%252Fangularjs%252F1.6.5%252Fangular.min.js%253A42%253A290%250A%2520%2520%2520%2520at%2520p%2520(https%253A%252F%252Fajax.googleapis.com%252Fajax%252Flibs%252Fangularjs%252F1.6.5%252Fangular.min.js%253A8%253A7)%250A%2520%2520%2520%2520at%2520g%2520(https%253A%252F%252Fajax.googleapis.com%252Fajax%252Flibs%252Fangularjs%252F1.6.5%252Fangular.min.js%253A42%253A138)%250A%2520%2520%2520%2520at%2520https%253A%252F%252Fajax.googleapis.com%252Fajax%252Flibs%252Fangularjs%252F1.6.5%252Fangular.min.js%253A42%253A322%250A%2520%2520%2520%2520at%2520p%2520(https%253A%252F%252Fajax.googleapis.com%252Fajax%252Flibs%252Fangularjs%252F1.6.5%252Fangular.min.js%253A8%253A7)%250A%2520%2520%2520%2520at%2520g%2520(https%253A%252F%252Fajax.googleapis.com%252Fajax%252Flibs%252Fangularjs%252F1.6.5%252Fangular.min.js%253A42%253A138)%0A%20%20%20%20at%20https:%2F%2Fajax.googleapis.com%2Fajax%2Flibs%2Fangularjs%2F1.6.5%2Fangular.min.js:7:76%0A%20%20%20%20at%20https:%2F%2Fajax.googleapis.com%2Fajax%2Flibs%2Fangularjs%2F1.6.5%2Fangular.min.js:43:70%0A%20%20%20%20at%20p%20(https:%2F%2Fajax.googleapis.com%2Fajax%2Flibs%2Fangularjs%2F1.6.5%2Fangular.min.js:8:7)%0A%20%20%20%20at%20g%20(https:%2F%2Fajax.googleapis.com%2Fajax%2Flibs%2Fangularjs%2F1.6.5%2Fangular.min.js:42:138)%0A%20%20%20%20at%20https:%2F%2Fajax.googleapis.com%2Fajax%2Flibs%2Fangularjs%2F1.6.5%2Fangular.min.js:42:322%0A%20%20%20%20at%20p%20(https:%2F%2Fajax.googleapis.com%2Fajax%2Flibs%2Fangularjs%2F1.6.5%2Fangular.min.js:8:7)%0A%20%20%20%20at%20g%20(https:%2F%2Fajax.googleapis.com%2Fajax%2Flibs%2Fangularjs%2F1.6.5%2Fangular.min.js:42:138)%0A%20%20%20%20at%20gb%20(https:%2F%2Fajax.googleapis.com%2Fajax%2Flibs%2Fangularjs%2F1.6.5%2Fangular.min.js:46:251)%0A%20%20%20%20at%20c%20(https:%2F%2Fajax.googleapis.com%2Fajax%2Flibs%2Fangularjs%2F1.6.5%2Fangular.min.js:22:19)%0A%20%20%20%20at%20Uc%20(https:%2F%2Fajax.googleapis.com%2Fajax%2Flibs%2Fangularjs%2F1.6.5%2Fangular.min.js:22:332

somebody must have updated the docs website and broken something. this issue has occurred before.
Previous issues:
https://github.com/angular/angular.js/issues/12960
https://github.com/angular/angular.js/issues/12963

Yep unfortunately. I also cant access the docs

Can you check if clearing the browser cache helps (not just F5, completely clear all cache data)? I had some intermittent failure loads, but now everything seems good.

Have this problem in Chrome but it opens in MS Edge.
I get a bunch of warnings in my console in Chrome before the above @georgeawg mentioned Error

docs.angularjs.org/:63 A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ajax.googleapis.com/ajax/libs/angularjs/1.6.5/angular.min.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
addTag @ docs.angularjs.org/:63
docs.angularjs.org/:63 A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ajax.googleapis.com/ajax/libs/angularjs/1.6.5/angular-resource.min.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
addTag @ docs.angularjs.org/:63
docs.angularjs.org/:63 A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ajax.googleapis.com/ajax/libs/angularjs/1.6.5/angular-route.min.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
addTag @ docs.angularjs.org/:63
docs.angularjs.org/:63 A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ajax.googleapis.com/ajax/libs/angularjs/1.6.5/angular-cookies.min.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
addTag @ docs.angularjs.org/:63
docs.angularjs.org/:63 A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ajax.googleapis.com/ajax/libs/angularjs/1.6.5/angular-sanitize.min.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
addTag @ docs.angularjs.org/:63
docs.angularjs.org/:63 A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ajax.googleapis.com/ajax/libs/angularjs/1.6.5/angular-touch.min.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
addTag @ docs.angularjs.org/:63
docs.angularjs.org/:63 A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ajax.googleapis.com/ajax/libs/angularjs/1.6.5/angular-animate.min.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
addTag @ docs.angularjs.org/:63

Hi @mottykohn , these logs are unrelated to the broken docs some people are experiencing.
In Chrome, you can try to clear the cached site data completely. I think it's a cache issue.

It worked! thanks

On Thu, Aug 24, 2017 at 3:49 PM, Martin Staffa notifications@github.com
wrote:

Hi @mottykohn https://github.com/mottykohn , these logs are unrelated
to the broken docs some people are experiencing.
In Chrome, you can try to clear the cached site data completely. I think
it's a cache issue.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular.js/issues/16194#issuecomment-324737913,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARIl6GuOiwCZ4umt_5tI0Kzq9RHB27Enks5sbdPlgaJpZM4O_35M
.

--
Mordechai Kohn

I'm pretty confident that this was a caching issue, which will be resolved once we switch to Firebase.

Was this page helpful?
0 / 5 - 0 ratings