Skip to content

After uploading image the page is stucked, unable to scroll it #470

Open

Description

@juddin0802

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

Activity

  1. colbyfayock commented on May 6, 2024

    @colbyfayock
    Collaborator

    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?

    image

    the tricky part is that your uploads need to have the same public ID

  2. Poise-Paul commented on Jul 26, 2024

    @Poise-Paul

    I have the same issue i think after i setState

  3. andrewsmithdesign commented on Aug 2, 2024

    @andrewsmithdesign

    We're having the same issue too - here's the testing flow to recreate:

    • upload a file using <CldUploadWidget /> with autoMinimize={true) in options
    • once the smaller cloudinary progress modal appears in the bottom right, open it up again (un-minimizing it)
    • the cloudinary modal disappears once complete, and the fileUrl etc feeds into the state successfully
    • now can't scroll the page

    My 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.

  4. colbyfayock commented on Aug 2, 2024

    @colbyfayock
    Collaborator

    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...

  5. andrewsmithdesign commented on Aug 4, 2024

    @andrewsmithdesign

    Thanks for getting back so fast! I'll have a look for some faulty modal overflow-hidden logic on our end. Challenging to debug!

  6. colbyfayock commented on Aug 4, 2024

    @colbyfayock
    Collaborator

    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 :(

  7. stephen-leisy commented on Aug 8, 2024

    @stephen-leisy

    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.

    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.

  8. colbyfayock commented on Aug 8, 2024

    @colbyfayock
    Collaborator

    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?

  9. stephen-leisy commented on Aug 8, 2024

    @stephen-leisy

    @colbyfayock I can't currently because its in a private work repo, but I'll try and reproduce it in a sandbox and share.

  10. Poise-Paul commented on Aug 18, 2024

    @Poise-Paul

    @stephen-leisy That fix is not working for me .., page is still stuck

  11. colbyfayock commented on Aug 18, 2024

    @colbyfayock
    Collaborator

    @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

  12. evansosei0707 commented on Oct 6, 2024

    @evansosei0707

    @stephen-leisy You saved my ASS🤧🤧. Thanks buddy.

  13. colbyfayock commented on Oct 7, 2024

    @colbyfayock
    Collaborator

    @evansosei0707 were you able to regularly reproduce this?

  14. 5 remaining items

  15. jlooper-cloudinary commented on Sep 24, 2025

    @jlooper-cloudinary
    Collaborator

    @Znoy108x I have assigned this bug over to you

  16. TomerPacific commented on Oct 10, 2025

    @TomerPacific

    @jlooper-cloudinary - Is this still relevant?

  17. jlooper-cloudinary commented on Oct 10, 2025

    @jlooper-cloudinary
    Collaborator

    hi, looks like no one is assigned, so @TomerPacific if you want, please PR

  18. TomerPacific commented on Oct 10, 2025

    @TomerPacific

    @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.

  19. TomerPacific commented on Oct 11, 2025

    @TomerPacific

    @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?

  20. jlooper-cloudinary commented on Oct 12, 2025

    @jlooper-cloudinary
    Collaborator

    @eportis-cloudinary I couldn't reproduce the issue either. Perhaps we close?

  21. TomerPacific commented on Oct 14, 2025

    @TomerPacific

    @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.

  22. jlooper-cloudinary commented on Oct 16, 2025

    @jlooper-cloudinary
    Collaborator

    Since we have trouble reproducing this after several tries, we'll keep this alive but I have edited the tags

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingwontfixThis will not be worked on

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions