Open GoogleCodeExporter opened 8 years ago
Original comment by tfmorris
on 12 Oct 2011 at 9:47
Original comment by tfmorris
on 28 Oct 2011 at 7:58
r2375 adds basic support for public Google spreadsheets (including worksheet
selection) as well as the ability to sign out (ie deauthorize Refine) when
you're logged in.
The following URL forms work:
https://docs.google.com/spreadsheet/ccc?key=0AlD_6iEb8Ed9dGs3clVJYi0yYVBka181Z0Z
KRW9kQ0E#gid=0
http://spreadsheets.google.com/ccc?key=pc6ppXdYxYkRPmnSBmFDRUg
https://spreadsheets.google.com/spreadsheet/ccc?key=0AsaDhyyXNaFSdDJ2VUxtVGVWN1Y
za1loU1RPVVU3OFE&hl=en_US&authkey=CLXm3-ML
http://spreadsheets0.google.com/ccc?key=pmEMxYRcQzzATwbOb71BmGA
https://spreadsheets.google.com/pub?key=0Ah0xU81penP1dDNwSFROSU5KVlFRbmo5cERsTEl
KTGc&hl=en&output=html
These two don't yet:
https://docs.google.com/spreadsheet/ccc?key=0AuCc2KRWCBN7dDlSSVBpcU5IZnVTWW5TVzh
qY3V0WGc#gid=0
http://docs.google.com/spreadsheet/ccc?key=0AuCc2KRWCBN7dDlSSVBpcU5IZnVTWW5TVzhq
Y3V0WGc
There may also be cases where some things with public spreadsheets only work if
you're signed out for reasons I haven't fully investigated.
I'm not crazy about the UI design, so I'm open to suggestions (or
patches/fixes).
I'll leave this open, but the current implementation is probably good enough
for people to beat on (ie beta test).
Original comment by tfmorris
on 16 Nov 2011 at 7:41
Tom,
I'm just going to string the issues I see so far.
1. Part of the Error gets cutoff and probably would be nice to have the full
error given to the user in the popup... notice my command window has the full
error. Capture.PNG
2. There seems to be an EDIT checkbox available, but I didn't check it. But
what I did do was use File - Publish to the Web. There is also the SHARE
button option with settings such as shown in Maine-Lighthouses-XLSX.png
I think that for # 2 the issue is basically that you have to really use File ->
Publish to the Web in GDocs, in order for Refine to have access with the
current implementation you have. The SHARE button settings did not matter
which radio button it was set to during my testing.
For # 1, I think that changing the error message to give the user a hint that
they can use File -> Publish to the Web in GDocs to really make the file
"Public" for Refine to access it properly would might work ?
Original comment by thadguidry
on 17 Nov 2011 at 4:00
Attachments:
Tom,
It looks like for Google FusionTables you have to make a view of an uploaded
spreadsheet before Refine can access. See attached screenshot.
The view that I created here:
https://www.google.com/fusiontables/DataSource?docid=1HcVjgUbpAYRb3OIElW-vdnaq_u
daAitKOvEeJpA&hl=en_US does work with the Refine public url input now.
But my original table upload here:
https://www.google.com/fusiontables/DataSource?docid=1pykVFIFBBGRTNOSEs12uThsvzt
zQmTN4ceiVoTU&hl=en_US even though it is made public, cannot be accessed for
some reason.
Original comment by thadguidry
on 17 Nov 2011 at 4:21
Screenshot of from About menu on Google FusionTables View made from Table.
Original comment by thadguidry
on 17 Nov 2011 at 4:29
Attachments:
With r2378 , I cannot import any Google docs spreadsheet if it is NOT
PUBLISHED. See comments of details covering 3 sharing scenarios with results
in attached file. If I instead choose, File -> Publish to the Web, then it
every spreadsheet I have works and also works in 3 formats, csv, txt, xls.
Original comment by thadguidry
on 18 Nov 2011 at 3:03
Attachments:
Bump all unfinished 2.5 Milestone tags to next release
Original comment by tfmorris
on 12 Dec 2011 at 7:56
It looks like the requirement that a spreadsheet be published is a restriction
in the current API (according to the Google Spreadsheet team), so there's
nothing we can do about it for the time being.
http://groups.google.com/group/google-spreadsheets-api/browse_thread/thread/c6be
ca8610eb653c?hl=en&tvc=2
As a workaround, users can access the public spreadsheet URL in a browser and
download an Excel or CSV version which they can then import. That's the best
we can do for right now.
Original comment by tfmorris
on 20 Dec 2011 at 6:06
Original issue reported on code.google.com by
tfmorris
on 12 Oct 2011 at 9:47