You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was just wondering how would one check that it's working as expected without deploying.
If I build the doc locally, I get the following error,
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at file:///..../docs/_build/html/_static/data/versionwarning-data.json. (Reason: CORS request not http)
If I build it locally, served via python -m http.server I get,
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://readthedocs.org/api/v2/version/?project__slug=&active=true. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing)
but that's not really sufficient to determine what would be the latest version linked, and the banner is not shown since there is already a banner injected by RTD.
Eventually I could test it by deploying the docs as latest, but I would also like to check that for older versions the redirected version is stable not latest and it seems that that's not possible, without actually releasing 2 versions, unless I'm missing something?
Maybe increasing the verbosity of console logging would already help.
The text was updated successfully, but these errors were encountered:
Thanks for this package!
I was just wondering how would one check that it's working as expected without deploying.
python -m http.server
I get,Eventually I could test it by deploying the docs as latest, but I would also like to check that for older versions the redirected version is
stable
notlatest
and it seems that that's not possible, without actually releasing 2 versions, unless I'm missing something?Maybe increasing the verbosity of console logging would already help.
The text was updated successfully, but these errors were encountered: