build-your-own-radar
build-your-own-radar copied to clipboard
Origin is not allowed by Access-Control-Allow-Origin.
Hi, I have massive problems with the instance running at https://radar.thoughtworks.com. Does anybody have the same problems? No matter if I use a google sheet or provide a CSV file on my own web server, every time this error appears in the java script console: [Error] Origin https://radar.thoughtworks.com is not allowed by Access-Control-Allow-Origin. [Error] Failed to load resource: Origin https://radar.thoughtworks.com is not allowed by Access-Control-Allow-Origin. (radar.csv, line 0) [Error] Fetch API cannot load [...]/radar.csv. Origin https://radar.thoughtworks.com is not allowed by Access-Control-Allow-Origin.
Hi @mschmid, Thanks for letting us know. We are currently working on this will update soon once done.
Hi @mschmid
Can you tell us, how you are using the google sheets option?
When we tried to create a new Google sheet and use it, it seemed to work perfectly. So can you help us out with the following information
- What URL are you entering in the text box?
- Before creating the radar, did you publish the Google sheet using the 'Publish to the web' option?
Thanks, Naji/Saran
Thank both of you for the fast answer. The given example works, if I paste the URL https://docs.google.com/spreadsheets/d/1waDG0_W3-yNiAaUfxcZhTKvl7AUCgXwQw8mdPjCz86U/edit#gid=0 on the website https://radar.thoughtworks.com the radar appears. If however I copy the example sheet within google docs to be able to modify it and publish it: https://docs.google.com/spreadsheets/d/1CBKf8sCxbxg9RHJNFXd7o_au-9jzG96wi_QdFFbEqkk/edit#gid=0 the following message appears:
Oops! We can’t find the Google Sheet you’ve entered. Can you check the URL? Please check FAQs for possible solutions.
Hi @mohamednajiullah & @SARAN-thala, any news on that? Can you reproduce the error?
Hi @mschmid
I also tried your scenario, this is my copy example sheet within google docs to be able to modify it and published it https://docs.google.com/spreadsheets/d/184npbFgA4dd5e28Inhm38KMk8HvcEEfpdTdiopkEyBc/edit#gid=0. If I paste this URL in https://radar.thoughtworks.com, the radar renders perfectly.
I would suggest to you, try with a new instance. This doc might help you.
@mschmid your sheet is not "Published to the web".
![screen shot 2017-11-06 at 9 04 09 pm](https://user-images.githubusercontent.com/6568319/32448863-19ba44b4-c336-11e7-8767-4fbda0a5f59c.png)
Please refer Publish section of the doc @SARAN-thala mentioned.
FYI https://spreadsheets.google.com/feeds/worksheets returns 403
when the sheet is not "Published to the web".
It will be better if we handle this scenario gracefully by showing an appropriate message to users and direct them to this doc.
@arunvelsriram Thank you vey much for the link with the spreadsheets - subdomain. This made the error visible. I published the document to the web, but I used another dialog (see screenshot) than the one that is described in the documentation.
With the publishing via the right dialog it works
I was not aware that google has to different ways to publish a document into the public.
Thank you very much, now I am able to use this tool also!
Thank you @arunvelsriram . Considering this issue is resolved, I'll close this thread.
Reopening this issue. We'll resolve this once we've gracefully handled this error.
With the publishing via the right dialog it works
Hi @mschmid
~~I have the same issue you had...~~ ~~A question to your solution~~: ~~How did you reach the~~ ~~right dialog~~~~?~~ 😕
Solved! Thank you @mschmid! I'm using German language and I thought the menu point to choose is Datei.Freigeben... but it's not. Datei.Im Web veröffentlichen... matches to "Publish to the web..." and that's what you have to use according https://www.thoughtworks.com/radar/how-to-byor! :blush:
Reopening this issue. We'll resolve this once we've gracefully handled this error.
Is this still on the, ahum, radar?
@mohamednajiullah is this resolved? If not, I can try to make a PR.
Workaround: enable it with https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf/related?hl=en . A way simpler solution would be #231 .
Closing as stale. Please reopen if it's not resolved.