Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Moving images from recent uploads to folders causing duplication

At present time if I move an image from recent uploads to an open folder in folder view it remains in recent uploads and creates a duplicate in the folder. This can be avoided by dragging them to the folder entirely in the righthand menu rather than the pop out folder, but this is very inconvenient. Not sure when this started, but it wasn't always like this.
1713066963
Gauss
Forum Champion
Hi McBeardly,  Since there is nothing a user can do about this and the Bug Report forum is primarily for users helping users I suggest filing a report with the Devs via the Help Center .  With that said, I can think of reasons for that kind of duplication. My understanding is Recent Uploads is it's own thing while folder view is different. It isn't actually duplicating the memory used. 
1713067426

Edited 1713067547
If I delete them from the folder there are then two entries in recent uploads. I have however submitted a bug report
1713077284

Edited 1713077312
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Hi McBeardly! Have you toggled the Recent Uploads filter? Dragging a file from Recent Uploads to a folder doesn't actually move it. It puts a pointer in the folder to the original files. All of your files "live" in Recent Uploads. There is a filter button at the top of the list that can hide items that have been filed. If that filter is not active, you will see the pointer in the folder and the original in Recent Uploads. It's not very intuitive because it doesn't duplicate the appearance of a OS-level file system. But toggling that filter would cause the behavior to look different. EDIT:  Just read your second post. That part does sound odd.
I have toggled the filter on and off, the duplicates remain. Really not sure what's going on.
I've had the same thing happening for a long time now. I put in a help ticket and received what I considered a good faith effort to look into it, but since it's more of an annoyance than a priority it's likely been back-burnered due to all the larger issues being worked on. Here is the text of the last response that I got. Being that it doesn't impact my upload quota and that I rarely look in the "recent upload" section once organize a file into a folder I've ignored it. On 9/2/2022 4:48 PM, Support wrote: Thank you for the detailed steps, I was able to reproduce this pretty regularly as a result. Apologies for the delayed response as I spent a good bit of time looking into what was going on (probably more than I should as a support rep...). It seems that the core of the issue is actually in the function "copy to library" which seems to also be duplicated within the "Copy to folder" functionality as well. It seems that this copy actually makes a copy. Which... typing out sounds intuitive, but in practice, seems somewhat odd as having duplicate versions of the same image is not very helpful or useful most of the time (I can see a world where someone wants to sort assets by game and wants to copy an image to two folders). But what causes this to display oddly, is that the "copy" is actually an entirely separate NEW image. Since the NEW image is a full on new image, it ALSO shows up in recent uploads.  As such, when you filter images from your art library, it filters the NEW image, but NOT the original image that was uploaded. Because the NEW image is in the folder/library and the original never actually moved from recent uploads. It is a bit difficult to say for certain if this is the intended functionality (given the scenario I outline, in addition to the fact that the copy does not contribute to storage quotas) so I am passing it along to product and development to make that determination. But it is definitely confusion and deserves a look. What I did find, is that you can work around this. If you make the folder and then manually move the original upload from "Recent Uploads" to the folder you made by dragging it, you won't run into this issue. I can't say for certain when the issue will be addressed or fixed, but now we know what's going on and that's a start!
1713181688
Lithl
Pro
Sheet Author
API Scripter
What I did find, is that you can work around this. If you make the folder and then manually move the original upload from "Recent Uploads" to the folder you made by dragging it, you won't run into this issue. I've been having this same issue for around a week now, and this workaround works for me.