Are there steps other than clicking the "Run tool" button to follow?
-
-
Replying to @really_bz @Novack_ and
If I try to put in a public spreadsheet URL, I get 'TypeError: can't access property "style", document.getElementById(...) is null'
1 reply 0 retweets 0 likes -
-
Thank you for checking. You can ignore the dom issues. But once you provide the spreadsheet id, try some operation like creating a table. Results were like the picture. Not sure how fast changes are introduced on nightly, this was 13 days ago.pic.twitter.com/GqgY8aAFjv
2 replies 0 retweets 0 likes -
If I use the 2020-03-09 nightly, load https://novack.itch.io/google-sheets-for-unity … and put in https://docs.google.com/spreadsheets/d/1Fq3OuAvrxfFZgFz9awFTdaXxIfq1ZDOwGrIU0dKYvVk/edit#gid=0 … for the sheet url, then when I click "Create Character Table/Worksheet" I do not get a CORS error. Same thing with a 2020-02-27 nightly.... What am I missing?
1 reply 0 retweets 0 likes -
What do you get? It just works? That would be good. The bad news is that the CORS rejection issue has now propagated to Firefox stable, Im on Win64, FF v74, and getting the CORS rejection.
2 replies 0 retweets 0 likes -
Replying to @Novack_ @really_bz and
I stand corrected. The error on FF 74 stable was due to your spreadhseet not having public write permissions. False alarm, sorry about that one.
1 reply 1 retweet 0 likes -
I added public write permissions now; wasn't clear that was needed. No change in behavior on nightly as far as I can see... Which makes me suspect I am not taking the same steps as you are, of course.
1 reply 0 retweets 0 likes -
The instructions of whats needed are described on the tool itself, I assumed anyone actually using the tool would read those short lines on the app form, made more sense to me than describing it all separatelly.
2 replies 0 retweets 0 likes -
Replying to @Novack_ @really_bz and
With writing permissions on the spreadsheet, it all works for me now as expected, on FF Stable v74.
1 reply 0 retweets 0 likes
OK, what about on nightly?
-
-
Regreattably, it seems to be the same case. Either it was an incorrect report all along, or has been solved in the past 20 days since the original report. Apologies, and thank you for your help.
1 reply 0 retweets 0 likes -
No need to apologize. Thanks for following up on this!
0 replies 0 retweets 1 like
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.