-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Got empty folder from shortcut (shortcut's objectID can not using for parentsID) #413
Comments
Google Drive API not support shortcut objectID as parentsID. |
Can you try building plexdrive from this branch https://github.com/felixbuenemann/plexdrive/tree/fix-shortcut-dir-listing or use the attached binary and see if it works now? You mush delete ~/.plexdrive/cache.bolt before starting the new version! plexdrive-list-shortcut-dir-fix-linux-amd64.zip Please report if it works correctly with the new version. I did some quick testing and it seems to work for me. |
Here is a new build that also fixed delete, rename and mkdir in shortcut dirs: plexdrive-shortcut-dir-fixes-linux-amd64.zip Please use this build instead for testing. |
Hi, Felix. |
I query a file ObjectID and TargetID in the cache.bolt, which from a 'team drive' had been linked by parent folder shortcut and should be cached, but unfortunately, there found nothing. |
I'm not sure shortcut folders to a team drive can work, I only tested with shortcuts to another folder in the same drive. For another team drive the change history that is used to build the cache.bolt would have to include items from the team drive the shortcut points to. |
All right, thats the key point, seems google api not responded the change history from another drive that the shortcut points to. So if the shortcut points to the different drive, than we will miss files. |
Hi, there.
I noticed exciting update had supported the shortcut, but unfortunately I got an empty folder from the shortcut.
I have rebuilt the cache bolt and the subfolder which symlinked from shortcut are counted correctly in first caching as well.
Thanks for any help. @RoyXiang
The text was updated successfully, but these errors were encountered: