What's wrong with the index DOC? content disappear


#1

I thought this is a official doc, but where is the index page content?
other page just fine,just the index-content disappear,like this:

UPDATE
I open the chrome console and I found this:

angular.js:11706 Error: [$parse:lexerr] Lexer Error: Unexpected next character  at columns 0-0 [@] in expression [@blog.title].

http://errors.angularjs.org/1.3.20/$parse/lexerr?p0=Unexpected%20next%20character%20&p1=s%200-0%20[%40]&p2=%40blog.title
at eval (angular.js:63)
at Lexer.throwError (angular.js:11968)
at Lexer.lex (angular.js:11927)
at Parser.parse (angular.js:12088)
at $parse (angular.js:12807)
at $interpolate (angular.js:10159)
at addTextInterpolateDirective (angular.js:8065)
at collectDirectives (angular.js:7248)
at compileNodes (angular.js:7058)
at compileNodes (angular.js:7074)


Online documentation does not load
#2

The root cause of the problem is the same thing as The Themes Doc Site All Pages Not Showing. Here’s a screenshot from just now of the Index Context page in the docs:


#3

The docs are hosted by readme.io, we don’t have control over it if there are bugs on the page. You’d need to at least provide us with your browser details, or otherwise send the report straight to them :slightly_smiling_face:


#4

I was just going to post about it, it’s not loading on any of my devices.

@Hannah it’s not loading on any device, iPhone, safari on both os, firefox, chrome.

It seems to be a request blocking it or something, because after a couple milliseconds it shows up

Does anyone have any other source to read it that is not downloading another theme? I’m trying to design the loop at the index page to show the posts


#5

The workaround is to press the browser stop button as soon as the content has loaded, before the scripts have loaded. Beyond that there’s nothing we can directly do - Readme.io is a centralised platform and they’re aware of the issue


#6

bro that trick doesn’t work for me, in the meantime, if someone has the same issue, I guess the other solution is to look at the original casper template :confused:


#7

The issue should be resolved now.