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
This post has been closed. You can still view previous posts, but you can't post any new replies.

Unable to Drag and Drop Compendium

Good morning! Using Google Chrome, D&D5E by roll20 character sheet. Across multiple games, dragging and dropping from the compendium into both maps and character sheets no longer works. Clicking things in the compendium pulls up their info tab, but dragging and dropping does nothing.
Same
Same here. I also have the charactermancer not working, while yesterday I  had the problem that the charactermancer gives Halflings, Gnomes and Dwarves a speed of 30'.
I'm having the same problem.  It was working earlier today, but seems to have broken in the last hour or so.
Same here. I just wasted an hour testing.
Same issue I expect, I can no longer drag monsters from the compendium to the tabletop.  F12 debug window shows error response 500 from the server. If the token is 'cached' in the journal already that seems to be fine.
Same problem.
I am having the same issue with the pathfinder 2e bestiary.
I'm not sure if I'm muddying the waters, but I am also having this issue, as are 2 of my partner GMs.
Also seeing this on the roll20 Dungeon World character sheet.
1584625589

Edited 1584625761
I am having the same issue with the 5E compendium. D&D5E by Roll20. Ran the tabletop on Safari, Chrome and Firefox.
same here and charactermancer not responding either.
I am also having this problem :/
I am also having this problem, and charactermancer will not work either
1584626960
Stephanie B.
Forum Champion
Sheet Author
Hi, there! Thanks for your report! We found an issue with drag-and-drop from the compendium this morning and are working on a fix. You can follow the progress in  this bug thread . Since this is being handled in the bug thread, I will be closing this thread to consolidate reports.