Shared folders appears empty

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create account foo@gmail.com
2. Create account bar@gmail.com
3. Create folder "Foobar" in foo's Google Docs. Put a few documents 
into it. Share folder "Foobar" with bar@gmail.com
4. gmount /home/bar/docs bar@gmail.com

What is the expected output? What do you see instead?

"Foobar" is available in /home/bar/docs but with no documents in 
it.

What version of the product are you using? On what operating 
system?

google-docs-fs 1.0beta4-1
Linux angband 2.6.33-ARCH #1 SMP PREEMPT

Original issue reported on code.google.com by oleg.smirnov@gmail.com on 1 Jun 2010 at 12:59

[GoogleCodeExporter]

I am able to successfully mount and see my local docs and all shared folders, 
but the shared folders are empty. I am using Google Apps Premier. Let me know 
if I can assist in any testing.

Original comment by *...@cloudbakers.com on 26 Aug 2010 at 2:16

[GoogleCodeExporter]

All my folders are empty, shared or not.

Original comment by pjt...@gmail.com on 11 Nov 2010 at 6:46

[GoogleCodeExporter]

My folders also appear to be empty, shared or not. There were no problems 
yesterday. Hopefully, this is a temporary problem at Google. 

Original comment by henrik.gorlin on 11 Nov 2010 at 9:59

[GoogleCodeExporter]

Problem with empty folders still persists as of Nov. 24, 2010. Is it really a 
fault at Google end?

Original comment by jarek.zg...@gmail.com on 24 Nov 2010 at 2:38

[GoogleCodeExporter]

I wrote stripped version of google-docs-fs which provides read-only access to 
accounts with shared folders.  

 * It uses version 3.0 of GDocs List API via gdata v.2.0.13 library.  
 * It also allows you to download any file types (hello, PDFs!) 
 * and shows correct file size for files which use quota (e.g. not native GDocs formats).
 * I also added caching of directory listings, so it should work faster, but after you mount GDocs you won't see ongoing changes. (As far as I know it was already true for file contents.)

I attached this version with bundled gdata.  Hope it'll ease your pain. :)

Original comment by dmalinov...@gmail.com on 25 Nov 2010 at 8:59

Attachments:

• google-docs-fs_readonly_3.0.tgz

[GoogleCodeExporter]

@dmalinovsky. Works great, except that only 2/8 folders are visible and most of 
my files at root level are not. This only happens at root level, sub folders 
are not affected (as far as I can tell).

I also tried it on my test account. On my test account I have three folders 
that I own and one of them is a shared folder. My shared folder is not listed 
with ls and is not accessible. The test account also have one folder shared 
from my other account. This folder is visible and accessible. One other thing: 
one or two files from the sub directories are listed directly on root level 
(without any apparent pattern).

However, it felt good to download a pdf's and other files. :) 

Original comment by henrik.gorlin on 25 Nov 2010 at 7:04

[GoogleCodeExporter]

@henrik.gorlin. I guess I need to test it more yet. :) Can you tell what's the 
difference between your visible and invisible folders?  Also, do you have other 
version of google-docs-fs installed, maybe it's interfering with new one?

Original comment by dmalinov...@gmail.com on 26 Nov 2010 at 4:33

[GoogleCodeExporter]

Sorry, I was writing in a hurry (as I do now). What I mean by not 
visible/invisible is that the files and folders just do not appear in the mount 
folder (~/gdocs), as if they does not exist.

I do have an older version of gdata installed globally. But I run your version 
locally (without running setup.py). Perhaps this is not enough? Therefore I 
tested it all again in a chroot environment and the problem persists. 

This is what should present in my mount folder at root level:
Folder1 (old and shared by me)
Folder2 (old and shared with me)
Folder3 (new)
Folder4 (new)

What is present? Folder 2, 3 and 4 are present but Folder1 is not. Well this is 
my test account. 

On my ordinary account most of my files and folders at root level are not 
showing up at all, regardless of whether they are shared (by/with me) or not. 
Like before, I see no apparent pattern. 

These problems aside, it works and it is fast. Nice!

Original comment by henrik.gorlin on 26 Nov 2010 at 6:40

[GoogleCodeExporter]

OK, Henrik, thanks for your feedback. I'll do more testing later with more 
data, hopefully I find bugs.
Local version doesn't need to run setup.py, this file can be removed safely.

Original comment by dmalinov...@gmail.com on 26 Nov 2010 at 6:54

[GoogleCodeExporter]

Hmm, I see missing folders with my other Google account.  So I'll fix it sooner 
then I thought.

Original comment by dmalinov...@gmail.com on 26 Nov 2010 at 7:29

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I added fix to retrieve more files & folders for the root folder. For some 
reason not all folders are retrieved still, but now it works better.

Original comment by dmalinov...@gmail.com on 29 Nov 2010 at 5:32

Attachments:

• google-docs-fs_readonly_3.0.tgz

[GoogleCodeExporter]

Hi, do we have a solution with the empty shared folders?

@dmalinovsky: do you have read-write patch for your script modification?

Original comment by eli...@mhlegal.eu on 12 Mar 2012 at 11:36

[GoogleCodeExporter]

> do you have read-write patch for your script modification?

No, I choose not to bother myself with it since we didn't use writing anyway.

Original comment by dmalinov...@gmail.com on 13 Mar 2012 at 1:54

[GoogleCodeExporter]

Umm, is this an issue with Google or what?? I read the whole thread but no idea 
what's up??

Original comment by agi...@gmail.com on 26 Feb 2013 at 4:09