Image update/replacement improvements
closed
Sergii Tiurin
At present, the workflow of updating/replacing existing images is not very convenient:
- If you replace the source image in the Drive, the updated image is shown in the public preview right away, however it takes several hours until the updated version becomes available in the WYSIWYG editor (while the notification message mentions that it should take up to 20 minutes). This makes it hard to track whether you see an updated image in the editor.
- The source image file cannot be replaced from the topic editor - you have to find the file in the drive and replace it from there. Also, to see the file name of the source image you have to check topic code or open it in a new browser window. It would be better to be able to easily see the source file name from the editor as well as initiate its replacement from there.
- Because the image update takes several hours, it's easier to add a new image rather than replace/update an existing one. In this case, the old file remains in the drive as an unused image.
- If you drop and image during upload with a file name that already exists, it doesn't warn you that there is already a file with the same name, and adds a copy with (1) added to its name in the root folder. It would be nice to have an option to replace the existing file(s) in the corresponding folders during upload.
Log In
Thiru
closed
Thiru
Merged in a post:
BUG: Replacing image on Drive is not working
Michelle Van Kolck
Test round 1:
I completed steps above then I waited 30 minutes. (I was told by Doc360 support team it can take up to 20 mins for Drive to update) Dependencies remained and image was not changed to Arrow 1.
I tested it multiple times. Same result each time.
Doc360 support team response:
Asked me to empty cache and hard refresh and re-test.
Test round 2:
I did the empty cache and hard refresh but exact same issues displayed.
please see image attached of steps taken to replace image file on Drive.
Thiru
Caroline Michelle Van Kolck we empathize your scenario, however there is dependency scenario that requires to be considered. Ideally the image replace will not take 20 minutes usually happens less than that. Factoring dependencies such as articles will be also be impacted and replace should immediately reflect back in the article contents as well.
We understand the challenges, but in 2.0 the time taken to replace has been improvised. We suggest you to validate them in new portal and suggest your thoughts.
Thank you
Abby Dong
It would be great if the "replace" feature for an image in an article actually replaced that particular file's image instead of uploading your replacement as a new file. I'd also like to see a "go to drive location" option for images in articles, and the ability to see the name of the image from the article. This would make managing and updating images much faster. Currently we have to hope someone uploading a file with a proper name and to a logical location (we're making a shift to auto upload new images to specific folders but this doesn't help us for previously uploaded images that need to be managed).
Mary Theis
I agree that this process should be easier. I have to delete and remove the image file from the Recycle Bin before I upload the newer image with the same name.
Thiru
planned
Caroline Tabach
Michelle Van Kolck I also could not make this work. There is a similar ticket somewhere
Sergii Tiurin
One point to add to the list:
Sometimes, you don't need to replace an image with a completely new one. You may need to only make some small adjustments, which could easily be done in an image editor.
I understand that it's probably impossible to associate an image editor and edit images in it, because the image files are stored on the remote drive and not on the local drive. However, in this case, it would be great if Document360 could implement its own editor within Document360 to perform simple operations, such as trimming, adding elements (shapes, arrows, lines, callouts, text, etc.), removing background, filling background, etc. See SnagIt editor as an example of user-friendly implementation for these simple image editing operations. A built-in editor would provide the ability to make simple changes without having to go through the tedious time-taking image replacements process, at least in some scenarios.
Gerard U
I spent a few months troubleshooting file image replace issues with the support team. We encountered the same items described.
Caroline Tabach
I am also encountering these issues
Load More
→