I've noticed something strange, was able to replicate it on the ys demo site as well
seems there is a strange download token issue regardless of what the concurrent download setting is set to
1. open a file download page
2. open a second file's download page in a new tab
3. go back to tab 1 and navigate through until you get to the 'download' or 'download / view now' (Don't click it though)
4. go to tab 2 and navigate through till you get to the same page as in step 3 (Don't click it though as well)
5. obviously there's a few tokens generated already, go back to tab 1 and click the download button now, it wont work and will generate a new token and you'll start the process again, if you go to tab 2 the same will happen
i used these files for the above test:
https://fhscript.com/DxB/Screenshot_2016-01-18-18-41-33.png
https://fhscript.com/Dxz/480730.jpg
its almost as if it not dealing with multiple tokens simultaneously, im not sure if i'm completely out to lunch here but i noticed this on my site then was able to replicate it on fhscript.com, if it makes any difference im using chrome
i think this is an urgent issue as a user can easily do this, plus it would be hard to explain to a user that once they've clicked on the file they have to commit to downloading it, and since the page just refreshes with a new token they'll get confused and just assume the site doesn't work and close the tab altogether
thanks
seems there is a strange download token issue regardless of what the concurrent download setting is set to
1. open a file download page
2. open a second file's download page in a new tab
3. go back to tab 1 and navigate through until you get to the 'download' or 'download / view now' (Don't click it though)
4. go to tab 2 and navigate through till you get to the same page as in step 3 (Don't click it though as well)
5. obviously there's a few tokens generated already, go back to tab 1 and click the download button now, it wont work and will generate a new token and you'll start the process again, if you go to tab 2 the same will happen
i used these files for the above test:
https://fhscript.com/DxB/Screenshot_2016-01-18-18-41-33.png
https://fhscript.com/Dxz/480730.jpg
its almost as if it not dealing with multiple tokens simultaneously, im not sure if i'm completely out to lunch here but i noticed this on my site then was able to replicate it on fhscript.com, if it makes any difference im using chrome
i think this is an urgent issue as a user can easily do this, plus it would be hard to explain to a user that once they've clicked on the file they have to commit to downloading it, and since the page just refreshes with a new token they'll get confused and just assume the site doesn't work and close the tab altogether
thanks