Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Can't upload token markers

1742145395

Edited 1742145742
I'm trying to add an icon to an already populated custom token marker set but it fails. Here are the steps I follow : Open the token marker set I want to add the image to. Click on the "Add images" button. Drag the file in the popup or click the "choose a file" button within it. Wait for the image to be uploaded (or at least for the progress bar to fill). Click on the "Upload" button. A new popup appears claiming to be processing the files and warning me that it may take a few minutes. This dialog contains a progress bar that is filled almost immediately upon being displayed, but the process never seems to end. After about 20 minutes of waiting, nothing changed : the "Processing files" dialog was still up, asking me to wait, and the set remained not updated. Checking the console, I noticed the POST request sent during step 3 resulted in a 403 status ( <a href="https://app.roll20.net/marker-library/uploadimage/305007" rel="nofollow">https://app.roll20.net/marker-library/uploadimage/305007</a> ) with no relevant error message (the response is just a bigass html file, possibly roll20's landing page). When clicking the "Upload' button in step 5, an error message appears in the console : Uncaught TypeError: Cannot read properties of null (reading 'join')&nbsp;at 305007:1547:88 Since I've had no problem adding token markers to a new, empty set, I tried adding this file to a new set but it failed the same way. I tried adding to this empty set a file I had already managed to import in another set but it failed too. Misc infos : The file I'm trying to add is a 256x256 png file named "Reveal_icon.png". I currently have&nbsp;213.2 KB of token markers and about 3.8 MB of free space on my account. I have a stable internet connection. I'm using the latest version of the Vivaldi browser. I've used previous versions of this browser to upload token markers successfully. That's about it. Tell me if there's anything I can do to circumvent this problem or help solve it. Edit: I did try to refresh my browser, empty its cache, close it and restart it, and even reboot my PC. PS: kind of unrelated but I had my browser console opened when I went to the My Account page. I'll skip over the error stack traces printed as regular messages to just point this message out : You are running a development build of Vue. Make sure to use the production build (*.prod.js) when deploying for production. ._.
1742180377
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Hi Mnioni! I don't know if this would cause a failure, but when creating sets for the marketplace, I believe the spec is for 512x512. You could try deleting your browser's cache, but your best bet would be capturing a&nbsp; Console Log ( Chrome , Firefox ), and filing a&nbsp; Help Center Request . The help forums are mostly for community-level help.
1742200709

Edited 1742200740
I believe none of my existing token markers are 512x512 and would like to believe the dev team didn't make any breaking update on this feature since october. I have contacted the support, thank you for the convenient links ! Have a good day.
1742228512

Edited 1742232719
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Yeah, it's just a marketplace spec, and I have been told it results in better final rendering. I wouldn't think it would be a technical limitation, but was throwing it out just in case. I hope the team is able to help you.
In the end, my browser got a new update a few days later and I was able to upload the token marker after installing it. I had to log back into roll20 before though, so either the update, logging out or something else to do with the cache could have fixed it.