I have a document (FILE-1) with two parent folders (FOLDER-1 and FOLDER-2).
If I delete FOLDER-1, FILE-1 is also deleted. However, I expected that only FOLDER-1 would be deleted, and removed as a parent of FILE-1, which would be left intact.
Is this the intended behavior, or a bug?
It appears to be by design according to this Google Drive support documentation. It seems as though trashing a folder and removing a parent from a file are two completely different things.
3. The folder will be moved to Trash, and all items in that folder will also be moved to Trash.
I also found same thing but I think they want this only..that when a folder is moved to trash all the items in that folder will also be moved to trash.
They might have done something like if you are willing to delete a folder they would have asked for the confirmation messaging whether user wants to delete files inside it or not and if not they would have asked user to move it to another folder but again its there choice and there way of thinking.
Related
I'm using Make (formerly Integromat) to remove permissions on Folders, files and subfolders using Google Drive APIs.
When removing permissions on a folder (either through the UI or the API), Google will recursively remove like permissions from any files in that folder and any subfolders. There is naturally a propagation delay whilst this process completes.
So far so good.
Drive will necessarily leave some file and subfolder permissions intact where those permissions were specifically granted on that/those objects. We therefore need to iterate through those files and subfolders, checking for any residual permissions and removing them with the Remove Permissions API.
The problem here is that there is no way to determine whether permission removals are still being processed (propagated) from the parent folder. THe only (crude) way I can think of dealing with this is to introduce a fixed delay time between permission removals. If the delay time isn't long enough, Remove Permissions returns an error when trying to remove a permission which has already been removed.
Has anyone dealt with this in a more effective way?
how do you change the parent of a folder in a team drive. AddParents / RemoveParents generates an error "in a team drive a file has only one parent" and you can only read access to the parent collection. Should I make a copy of the file and delete the existing file?
Thank you
You need to remove the parent folder first then add the new parent.
Or you can do an update changing the parent from one to the next.
The main issue will be if this is even possible with team drive as your going to need to have the permission to do this.
When I am deleting a file from Google drive which someone else shared with me, it showed me a message like "one removed file is still accessible by collaborators".
It no longer appears in that folder, but will it be shown in "shared with me"? How can I delete it completely?
tl;dr
To completely delete file in gdrive of owner of the removed file:
Search for is:unorganized owner:me
Delete file
Remove it from trash (delete it permanently)
Explanation:
This is a common problem with Google Drive. Files removed from the Shared folder loses the location pointer and stays on the drive of the owner of the file with lost location property (cannot be accessible in standard way as we browse files in Google Drive).
The removed file can be found by searching for it by name or content, or using suggested the search phrase is:unorganized owner:me.
A scenario that commonly causes this problem and fix:
U (as you) and S(someone else) have shared folder with name Cats pictures
U add cat.jpg (and U is an owner of this file then)
S don't like this picture and use option Remove
The message removed file are still accessible by collaborators pops up
File cat.jpg is removed from shared folder Cats pictures
S is happy and never see a cat.jpg in Cats pictures folder
U cannot see this file either in Cats pictures folder but cat.jpg is still on U private Google Drive!
If U search in Google Drive for cat.jpg it find the file, and it location will be - (file lost it's location in folder tree).
The file found by U can be moved to Trash and then completely deleted 🎈
You mentioned you'd deleted the file from Google drive which was shared by someone else with you. After deleting you saw a message that stated, "one removed file is still accessible by collaborators". Perhaps the one who is sharing the file is one of the mentioned collaborators, or depending on how this document was shared, other members of the group.
Hope this helps!
Rename file a number then delete twice or 3 times it won't recognize it I had 6and there gone now
I'm playing with the Google Drive API and one thing that I keep wondering about is IDs in the case of an arbitrary file (non-Google App) like an image.
If a user is working locally, offline and they turn off the Google Drive client. And then they make some changes to a file, let's say they rename it, move it from one folder to the next and edit it.
Will the ID remain the same when the client comes back on, or will it break? I imagine the client will interpret either one or all of the move, rename and edit as delete and new file.
Would appreciate any help here!
The file id (within Google Drive) remains the same from the original creation to its deletion.
In the Google Docs format, I could save one file to two (or more) folders by checking multiple boxes. Now that I've switched to Google Drive, I find that the files that were already in more than one folder stay that way, but I am unable to save a new file to two (or more) files/collections. Am I not doing something correctly or is this an intentional change?
Drag the file to the desired folder and press the Ctrl key before dropping it.
The action changes from Move to Add (mover/Añadir in Spanish).
You get a linked file with joined share permission