search

salimoha / googlecl

Automatically exported from code.google.com/p/googlecl
0 stars 0 forks source link

"docs get --title "*******" --format html" not working ( 'reason': 'Invalid exportFormat: html' ) ¿? #300

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Save a Spreadsheet on Docs
2.Try to download it from the google cl
3.

What is the expected output? What do you see instead?
to download the spreadsheet on html format, instead of that I see:

> docs get --title "Publica" --format html
Downloading Publica to C:\Documents and Settings\carlos\Application Data\googlec
l-0.9.9\Publica.html
Download of Publica failed: {'status': 400, 'body': '<HTML>\n<HEAD>\n<TITLE>Inva
lid exportFormat: html</TITLE>\n</HEAD>\n<BODY BGCOLOR="#FFFFFF" TEXT="#000000">
\n<H1>Invalid exportFormat: html</H1>\n<H2>Error 400</H2>\n</BODY>\n</HTML>\n',
'reason': 'Invalid exportFormat: html'}

What version of the product are you using? On what operating system? What
version of gdata-python-client (aka python-gdata)?

googlecl-0.9.9

Please provide any additional information below.

Original issue reported on code.google.com by carlosab...@gmail.com on 29 Sep 2010 at 6:37

GoogleCodeExporter commented 9 years ago 
I've started getting the same error as of this morning. All other export types 
work fine: csv, xls, pdf, etc.

http://spreadsheets.google.com/feeds/download/spreadsheets/Export?key=SOMEKEY 
HERE&exportFormat=csv - works

http://spreadsheets.google.com/feeds/download/spreadsheets/Export?key=SOMEKEY 
HERE&exportFormat=html - returns "Invalid exportFormat: html"

Original comment by shin...@gmail.com on 30 Sep 2010 at 5:08

GoogleCodeExporter commented 9 years ago 
Were you able to download spreadsheets as HTML files before? I didn't think 
that was possible. I'm able to download text documents as HTML just fine.

Original comment by thmil...@google.com on 4 Oct 2010 at 5:43

GoogleCodeExporter commented 9 years ago 
Yes, it was possible. =(

Original comment by carlosab...@gmail.com on 4 Oct 2010 at 5:53

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I'm having this same problem, and it was definitely possible to do before.  I'm 
NOT using a client library, just a direct call to the API.  I've checked both 
the 2.0 and 3.0 protocols and they both return the same error as described 
above.  Thanks for your prompt attention to this issue!

Original comment by n...@nealf.com on 5 Oct 2010 at 12:05

GoogleCodeExporter commented 9 years ago 
Seems like Docs broke somehow. I found this issue on the API issue tracker:

http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=2294

Please star that issue to receive updates -- I can't do anything about this 
problem :(

Original comment by thmil...@google.com on 5 Oct 2010 at 12:20

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r456.

Original comment by tom.h.mi...@gmail.com on 9 Oct 2010 at 1:51

GoogleCodeExporter commented 9 years ago 
We also got bit by this with our Google Docs connector for Confluence 
(standalone) on the 11th hour before a huge rollout (found the issue today) - 
but we applied the workaround and seems to work again. 

Thanks for this thread.. ! :)

Original comment by efeah...@gmail.com on 9 Oct 2010 at 6:43

GoogleCodeExporter commented 9 years ago 
One of the side benefits of being ranked well by PageRank, I guess :)

For other visitors -- the issue linked to in comment 6 contains a workaround: 
change 'html' to '102' in your exportHTML query parameter.

Original comment by thmil...@google.com on 9 Oct 2010 at 7:59