• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

If you delete an image from the queue before upload it doesn't return bbcode

Status
Not open for further replies.
lovedigit

lovedigit

👽 Chevereto Freak
Hello,

I have noticed a bug. I am not sure if it was first spotted after the 3.8.5 upgrade or earlier. I wanted to report it earlier, but I thought it might be only me. At first, I thought it appears at random, but later I figured out that it happens only after a specific action.

Finally, I could replicate it on the demo website as well.

DS4.md.jpg


To replicate this issue, simply add some images to upload queue. Once it is added, remove one or two images from the queue and hit "Upload" button. After 100% progress, the "anywhere upload" won't return any bbcode or success message. You'll have to go back to your profile or select images from explore window to get the bbcode.
 
Last edited:
This bug also appear when you add images from two different folders/path. The uploader gets stucks with the checkmark on the last image and never finishes, and hence never return the bbcode.

Dz6.md.jpg
 
lovedigit said:
This bug also appear when you add images from two different folders/path. The uploader gets stucks with the checkmark on the last image and never finishes, and hence never return the bbcode.
Click to expand...

I can't replicate that issue. Also, is impossible that a different path will cause such issue.
 
Rodolfo said:
I can't replicate that issue. Also, is impossible that a different path will cause such issue.
Click to expand...
You cant replicate it? I just sent you an screenshot from demo website. I tested it on chevereto demo before posting it here.
 
Sorry, I can't replicate it. Unless I'm able to replicate I can't do anything.
 
This is how you can replicate it. Hope it is helpful. (It was tested on Google Chrome Browser)

Bug 1
ssJR2.gif



Bug 2
sstCk.gif
 
Last edited:
Actually the bug doesn't need two different folders, it can be triggered in the same folder and is all related with the new simultaneus upload functionality.

The bug exists because the simultaneus upload functionality added indexed keys for the CHV.fn.uploader.results array, which in JS doesn't work as you may expect. In JS, arrays get private properties like array_unique or length, being length = top key + 1, so when the index stuff adds named indexes (keys) you get errors in the queue, this stuff is returning a wrong length for the array (ie, the array indexes are 1, 3 so the expected length is 2 but is returning 4). This is one of the "JS special things" that always cause issues.

I've changed all those arrays for objects which changes all the array related functions like push() and everything else that can't be applied to JS objects.

I'm attaching a temporary fix for this, I've already test it but you should also test it just in case I forgot something.
 

Attachments

Thank you for looking into it. I am really happy that it will be fixed now. 🙂

However, it still didn't work for me. I replaced the chevereto.js on my server and tested it on my website, as well as chevereto demo website.
 
Demo doesn't have this patch. As always, you need to make sure that whatever you upload isn't cached (browser, cdn) otherwise you won't be testing the patch.
 
Last edited:
Status
Not open for further replies.
Back
Top