Closed GoogleCodeExporter closed 8 years ago
gentoo 10.0 kernel 2.6.32-r7
python 2.6.5-r2
gdata 2.0.9
googlecl 0.9.7-r1
Original comment by johnson....@gmail.com
on 1 Jul 2010 at 12:35
Same here:
Arch Linux
python 2.6.5
gdata 2.0.10
googlecl 0.9.8
Original comment by icarnales
on 5 Jul 2010 at 2:42
I have the same issue:
Red Hat Enterprise Linux v5.5
Python 2.7rc2
gdata 2.0.10
googlecl 0.9.8
Original comment by mjeli...@gmail.com
on 5 Jul 2010 at 8:02
I haven't been able to reproduce those exact errors, but the attached patch
(against 0.9.8) may help, especially with the second error.
For the first, the bad request -- what editor are you using, what type of
document are you editing, and what format are you downloading it as?
Original comment by tom.h.mi...@gmail.com
on 9 Jul 2010 at 11:04
Attachments:
I'm using vim, the document is simple text.
Original comment by step...@gmail.com
on 9 Jul 2010 at 2:22
Patch fixes document creation for me, but I'd really like to edit my existing
docs again. :)
Original comment by ichth...@gmail.com
on 9 Jul 2010 at 2:35
Well, I've been able to reproduce the "Could not convert" error, but only when
doing something weird like editing a spreadsheet with vim.
The problem is that when the document gets uploaded after editing, the content
type disagrees with what Docs expects. I'm not sure how to figure out what Docs
expects.
This (or something like it) has been reported at
http://code.google.com/p/gdata-issues/issues/detail?id=1480, and someone claims
a fix for html files is being pushed as soon as possible. So anyone still
having issues may want to check out that issue from time to time and update to
the most recent version.
icthyos: Out of curiosity, can you edit an existing doc that was created
through the patched document creation?
Everyone: Does the "Could not convert" error occur with every file of the same
type, or just one or two?
Original comment by tom.h.mi...@gmail.com
on 9 Jul 2010 at 3:50
I get the error for every file I have tried. And they are simple text files
which were originally created via the Google Docs web interface. And this
still holds true even after applying the patch--which you probably expected.
Original comment by mjeli...@gmail.com
on 9 Jul 2010 at 4:43
I'm guessing the first problem (Could not convert...) lies with the new-version
documents that Google recently rolled out.
Could everyone try the most recent version in the trunk? It should catch this
problem and direct you to the FAQ which tells you how to convert to old-style
docs.
It seems that all new-version documents have a grey margin around the actual
document editing space. If you're getting the could not convert error with
old-style docs, let me know.
Original comment by tom.h.mi...@gmail.com
on 9 Jul 2010 at 11:11
The most recent version from trunk works for me with the new version documents.
I crafted an svn ebuild in my local portage overlay (googlecl-9999) and
installed googlecl. It worked great.
python-2.6.5-r2
gdata-2.0.9
googlecl - from svn trunk - revision 339
And, yes, older documents do indeed get caught and did direct me to the FAQ:
{'status': 400, 'body': 'Could not convert document.', 'reason': 'Bad Request'}
Is this a new-version document? gdata has a bug preventing updates on new
version documents.
Please follow the instructions on the FAQ in the wiki on how to convert your
document.
Original comment by johnson....@gmail.com
on 10 Jul 2010 at 2:28
I updated to the trunk and changed my Google docs settings not to use the
latest Google doc format and I can now successfully edit my google docs again.
Thanks for the support!
Original comment by mjeli...@gmail.com
on 11 Jul 2010 at 12:56
r337 fixes this issue.
Thanks for reporting in, everyone!
Original comment by tom.h.mi...@gmail.com
on 12 Jul 2010 at 7:15
Issue 202 has been merged into this issue.
Original comment by tom.h.mi...@gmail.com
on 12 Jul 2010 at 9:44
Original issue reported on code.google.com by
step...@gmail.com
on 30 Jun 2010 at 10:57