You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
After uploading image the page is stucked, unable to scroll it #470
After uploading image the page is stucked, unable to scroll it, any solution for it please?
Also is there a way in next js to update/ replace the old image with new one and also send the updated image URL to DB? currenctly I am just trying to send new updated image URL to DB but not working
when you say after uploading, can you help identify exactly when after? is this before a callback is fired, after a callback is fired, is this after you set state, etc. do you have a code example?
you're able to replace old images using Cloudinary, but tricky using the Upload Widget. one potential example that i didnt try is using the upload preset to turn on using the filename and having overwrite on, so that when uploading the same filename twice, i would expect it to replace instead of re-upload?
the tricky part is that your uploads need to have the same public ID
i keep hitting this at times too but haven't had a way to reproduce
i'll work through reproducing with those steps and I'm curious if this is a component issue or an underlaying Upload Widget issue, so will attempt to reproduce with a vanilla installation of the Upload Widget
thanks for the additional info everyone
Edit: i can't reproduce with the autominimize steps unfortunately...
just to be clear i think it is an issue with the component, it's happened to me at times too, i just haven't been able to get it to happen when i have visibility into what's going on or regularly reproduce it so that i can work on debugging it.
the challenging thing is being able to determine if it's CldUploadWidget or if it's the underlaying Upload Widget script that this is a wrapper around
i suspect its related to the Upload Widget though given what's going on with the overflow. im trying to see if anyone internally has hit this issue to try to find leads, in the meantime if anyone is able to get reproducible steps please let me know as those weren't working for me :(
I had this same issue, and what worked for me (although Im not clear why) was popping the close() function into the onSuccess param in the CldUploadWidget.
@Poise-Paul are you able to regularly reproduce this? are you able to share the code, create a reproduction, or explain how to do so? really would love to get this fixed but haven't been able to find anyone that can reproduce or regularly so
@jlooper-cloudinary - Ok, I'll start working on this. I have read all of the comments above, so I am unsure how to reproduce this. I'll try doing that first and then I'll go about working on a fix.
@jlooper-cloudinary - Seeing as this is becoming stale, I'm no longer actively watching this. Feel free to mention me if there are definitive reproduction steps or any new information.
Activity
colbyfayock commentedon May 6, 2024
when you say after uploading, can you help identify exactly when after? is this before a callback is fired, after a callback is fired, is this after you set state, etc. do you have a code example?
you're able to replace old images using Cloudinary, but tricky using the Upload Widget. one potential example that i didnt try is using the upload preset to turn on using the filename and having overwrite on, so that when uploading the same filename twice, i would expect it to replace instead of re-upload?
the tricky part is that your uploads need to have the same public ID
Poise-Paul commentedon Jul 26, 2024
I have the same issue i think after i setState
andrewsmithdesign commentedon Aug 2, 2024
We're having the same issue too - here's the testing flow to recreate:
<CldUploadWidget />withautoMinimize={true)in optionsMy guess is there's faulty logic somewhere that's pushing overflow-hidden into or
or something! Going to try recreating it without using autoMinimize. I'll edit this with an update.colbyfayock commentedon Aug 2, 2024
i keep hitting this at times too but haven't had a way to reproduce
i'll work through reproducing with those steps and I'm curious if this is a component issue or an underlaying Upload Widget issue, so will attempt to reproduce with a vanilla installation of the Upload Widget
thanks for the additional info everyone
Edit: i can't reproduce with the autominimize steps unfortunately...
andrewsmithdesign commentedon Aug 4, 2024
Thanks for getting back so fast! I'll have a look for some faulty modal overflow-hidden logic on our end. Challenging to debug!
colbyfayock commentedon Aug 4, 2024
just to be clear i think it is an issue with the component, it's happened to me at times too, i just haven't been able to get it to happen when i have visibility into what's going on or regularly reproduce it so that i can work on debugging it.
the challenging thing is being able to determine if it's CldUploadWidget or if it's the underlaying Upload Widget script that this is a wrapper around
i suspect its related to the Upload Widget though given what's going on with the overflow. im trying to see if anyone internally has hit this issue to try to find leads, in the meantime if anyone is able to get reproducible steps please let me know as those weren't working for me :(
stephen-leisy commentedon Aug 8, 2024
I had this same issue, and what worked for me (although Im not clear why) was popping the
close()function into the onSuccess param in theCldUploadWidget.Something like:
onSuccess={(result, { close }) => {
updateState(result);
close();
}}
Again, this is just what worked for me, but figured I'd share in case it helps unblock someone.
colbyfayock commentedon Aug 8, 2024
thanks @stephen-leisy - were you able to regularly reproduce it prior to that fix? are you able to share the code you had to reproduce it if so?
stephen-leisy commentedon Aug 8, 2024
@colbyfayock I can't currently because its in a private work repo, but I'll try and reproduce it in a sandbox and share.
Poise-Paul commentedon Aug 18, 2024
@stephen-leisy That fix is not working for me .., page is still stuck
colbyfayock commentedon Aug 18, 2024
@Poise-Paul are you able to regularly reproduce this? are you able to share the code, create a reproduction, or explain how to do so? really would love to get this fixed but haven't been able to find anyone that can reproduce or regularly so
evansosei0707 commentedon Oct 6, 2024
@stephen-leisy You saved my ASS🤧🤧. Thanks buddy.
colbyfayock commentedon Oct 7, 2024
@evansosei0707 were you able to regularly reproduce this?
5 remaining items
jlooper-cloudinary commentedon Sep 24, 2025
@Znoy108x I have assigned this bug over to you
TomerPacific commentedon Oct 10, 2025
@jlooper-cloudinary - Is this still relevant?
jlooper-cloudinary commentedon Oct 10, 2025
hi, looks like no one is assigned, so @TomerPacific if you want, please PR
TomerPacific commentedon Oct 10, 2025
@jlooper-cloudinary - Ok, I'll start working on this. I have read all of the comments above, so I am unsure how to reproduce this. I'll try doing that first and then I'll go about working on a fix.
TomerPacific commentedon Oct 11, 2025
@jlooper-cloudinary - I've created this minimal project trying to reproduce the issue and have not managed to do so (I attached it below).
next-cloudinary-demo.zip
How sure are we this issue still exists?
jlooper-cloudinary commentedon Oct 12, 2025
@eportis-cloudinary I couldn't reproduce the issue either. Perhaps we close?
TomerPacific commentedon Oct 14, 2025
@jlooper-cloudinary - Seeing as this is becoming stale, I'm no longer actively watching this. Feel free to mention me if there are definitive reproduction steps or any new information.
jlooper-cloudinary commentedon Oct 16, 2025
Since we have trouble reproducing this after several tries, we'll keep this alive but I have edited the tags