Oh god... looking at my own Ratings cookie, sometime relatively recently (or at least for my most recent half-dozen upvotes), post rating clusters that used to look like "15%2C1955705%2C1%7C" (unescaped: "15,1955705,1|") now look like "15%2C3981677%2C1%2Cundefined%7C" (unescaped: "15,3981677,1,undefined|")! The ratings modal added an entire new field that does nothing but take up a whole 12 extra characters of space in the cookie per upvote!
Also it looks like you can't "remove" a Like from a post, or at least it doesn't clear that entry from the cookie, so my suggested fix was pointless... Crap.
Edit: Wait... actually, those "undefined"s go away if you delete the cookie and reload the thread. That also makes any upvote you cleared disappear from the cookie. So there's that... and it would explain why things get a lot better right after you delete that cookie. Until you've made so many upvotes that the cookie still hits the header size limit.
The one good thing is it seems that the Ratings stuff is stored on the server side and just populates the cookie so that you see which posts you've upvoted. Perhaps the creator of the ratings modal could shave some length off each entry in the cookie... like, I dunno, by using hexadecimal numbers? (And dropping the "undefined" part...)
Oh god... looking at my own Ratings cookie, sometime relatively recently (or at least for my most recent half-dozen upvotes), post rating clusters that used to look like "15%2C1955705%2C1%7C" (unescaped: "15,1955705,1|") now look like "15%2C3981677%2C1%2Cundefined%7C" (unescaped: "15,3981677,1,undefined|")! The ratings modal added an entire new field that does nothing but take up a whole 12 extra characters of space in the cookie per upvote!
Also it looks like you can't "remove" a Like from a post, or at least it doesn't clear that entry from the cookie, so my suggested fix was pointless... Crap.
Edit: Wait... actually, those "undefined"s go away if you delete the cookie and reload the thread. That also makes any upvote you cleared disappear from the cookie. So there's that... and it would explain why things get a lot better right after you delete that cookie. Until you've made so many upvotes that the cookie still hits the header size limit.
The one good thing is it seems that the Ratings stuff is stored on the server side and just populates the cookie so that you see which posts you've upvoted. Perhaps the creator of the ratings modal could shave some length off each entry in the cookie... like, I dunno, by using hexadecimal numbers?
That sounds like a change rolling through. Not sure if changing to hex would really help long term though; it will still grow, it will take a little longer to cap.
The cookie is probably to offload stuff so the server doesn't have to feed you the rating information each and every time (its the only guess I have).
All we can do is keep this post on the top until the devs actually tell the moderators what's going on.
Oh yeah, I'd say the cookie is definitely so that it doesn't need to hit up the server every time you browse through the forums or homebrews. And yeah, adjusting to hexadecimal is still delaying the inevitable some, though doing that and removing the "undefined"s would make some difference for now. I'm still not sure why exactly it cuts into loading images so much.
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
The reason AboveVTT users are having this issue is because the extension links directly point to images from ddb. If you are affected by this issue, an AboveVTT user knows immediately that images are not loading. I don't see an extension being able to affect the site cookie and if so that would be a huge risk or something, right?
AboveVTT is not causing this issue, AboveVTT cannot be used when someone is affected by this issue.
Haven't cleared my ratings cookie yet today, so I'm coming to interact on the forum first. I've taken to referring to this issue as "getting rid of the rat" ... Ugh, images not loading again - time to look for the rat in the house, and kill it.
I'll just add, again, for the record - the appearance of a correlation between this issue and AboveVTT is due to a lurking variable, not to causation. AboveVTT users interact with a broader range of image files hosted on DDB more directly / more frequently... so AboveVTT users know something is wrong across the board sooner than an average user that might think "oh, that's weird, the images in that one source book didn't load" and then just move on.
and, IMO, AboveVTT users are a fairly dedicated and tech-involved crowd (since many/most of 'em are actively helping to code and otherwise develop the VTT collaboratively) - so AboveVTT users are ALSO extra likely to self-report here on the forums when we've noticed something wonky. This creates a misleading proportion of AboveVTT users in the forum "sample size."
My current question is based entirely on curiosity: modern internet users interact with zillions of rating systems online every day. Facebook likes, Netflix likes, ups and downvotes on reddit, any website that tracks "favorites" or "frequently purchased" like a grocery store or a merch vendor.... All of these sites surely have some sort of cookies tracking the users' input, and passing it back and forth to preload that info rather than re-load every site visit. Sooooooo... why have I (and other "average" internet users) never seen anything like this before on any of those other sites that also track user ratings of some sort? Is there something that DDB coded differently or something?
Reminder that forum upvotes might negatively effect the infinite size of the 'ratings cookie.' And also, my personal note that I would absolutely be upvoting some of these wonderful comments and attempts to help resolve the issue with experiential data.
and now I'm off to clean my ratings cookie for the day. Cheers ~ 💜
Has there been any DDB staff acknowledgment of this issue? Any responses to this thread in the past 6 months?
The moderators have seen it (back track in this thread), commented and recommended clearing cookies.
Whether the developers have seen it, acknowledge it, or if it is in their backlog isn't clear. But that is the case with most complex issues, so that isn't new. It is however quite irksome.
Considering that users seem to have tracked down the problems and recommended solutions. It is quite irksome, indeed.
!!!! Well that's just great. I had my current primary D&D beyond browser open, and I accidentally clicked on my notifications , thus bringing me to this thread. I closed the tab. But it was too late. All of my portraits are broken again. And despite deleting the ratings cookie multiple times, using cookie editor extension; they remain broken.
Having the same issue, nothing I do seems to fix it. This has effected most images on the website, including my homebrew pictures. Can we get a fix please staff? Cleared all cookies and data at great cost to my time and my homebrew races pictures are still broken. I managed to get my profile picture to work again after reuploading it. That trick refuses to work for the homebrew races though.
Cleared all the cookies. Still not working. This is a site issue, not a "cookies" issue.
Its a combination of large cookies, and site design. And it isn't unique to this site either. But as you have noticed, not all cookie clears actually work as you would expect. I had to do the following in edge to fix it for me:
Reset Microsoft Edge in Settings>Apps>Apps and Feature, scroll down to Microsoft Edge, highlight it, choose Advanced Options, then Repair, or if that fails, Reset."
For others, another solution that worked is in post #23.
A detailed explaination and some solutions to other sites having the same issue:
But you are correct; it isa site issue. Mairondil,Cyrantirand I have spent a lot of passion time on the root cause that the server code responds with an error, when the client sends up a cookie that is too large, and then the server refuses to send back the file.
All we have client side are workarounds; the server implementation needs adjustment (see Honza's discussion for developer options). But until then we have to be patient.
All we have client side are workarounds; the server implementation needs adjustment (see Honza's discussion for developer options). But until then we have to be patient.
How long do we have to remain patient? It was first reported May 2021, it is now February 2022.
Reading through this thread, many of us believe this is related to the upvote system on forum posts and published homebrew. It's difficult to quantify though because there's users that upvote posts and homebrew that are unaffected by this issue. I just know my experience and the method I found to quickly get around it.
Reading through this thread, many of us believe this is related to the upvote system on forum posts and published homebrew. It's difficult to quantify though because there's users that upvote posts and homebrew that are unaffected by this issue. I just know my experience and the method I found to quickly get around it.
Well its any cookie that gets too large...so it is a valid question for each person that is impacted, which cookie is the culprit. But getting to the right one isn't exactly something I want to walk my mother through.
If we could get a list that might help the developers. On the other hand, I have no idea where this issue is on their priority list. I'm sure they can mine the server logs to know how often it happens.
Oh god... looking at my own Ratings cookie, sometime relatively recently (or at least for my most recent half-dozen upvotes), post rating clusters that used to look like "15%2C1955705%2C1%7C" (unescaped: "15,1955705,1|") now look like "15%2C3981677%2C1%2Cundefined%7C" (unescaped: "15,3981677,1,undefined|")! The ratings modal added an entire new field that does nothing but take up a whole 12 extra characters of space in the cookie per upvote!
Also it looks like you can't "remove" a Like from a post, or at least it doesn't clear that entry from the cookie, so my suggested fix was pointless... Crap.
Edit: Wait... actually, those "undefined"s go away if you delete the cookie and reload the thread. That also makes any upvote you cleared disappear from the cookie. So there's that... and it would explain why things get a lot better right after you delete that cookie. Until you've made so many upvotes that the cookie still hits the header size limit.
The one good thing is it seems that the Ratings stuff is stored on the server side and just populates the cookie so that you see which posts you've upvoted. Perhaps the creator of the ratings modal could shave some length off each entry in the cookie... like, I dunno, by using hexadecimal numbers? (And dropping the "undefined" part...)
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
That sounds like a change rolling through. Not sure if changing to hex would really help long term though; it will still grow, it will take a little longer to cap.
The cookie is probably to offload stuff so the server doesn't have to feed you the rating information each and every time (its the only guess I have).
All we can do is keep this post on the top until the devs actually tell the moderators what's going on.
Oh yeah, I'd say the cookie is definitely so that it doesn't need to hit up the server every time you browse through the forums or homebrews. And yeah, adjusting to hexadecimal is still delaying the inevitable some, though doing that and removing the "undefined"s would make some difference for now. I'm still not sure why exactly it cuts into loading images so much.
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
Specific places I've noticed issues where deleting the Ratings section of the site cookie and hard reloading fixes on that particular page:
How to: Replace DEX in your AC | Jump & Suffocation stats | Build a (Spell & class effect buff system | Wild Shape effect system) | Tool Proficiencies as Custom Skills | Spells at higher levels explained | Superior Fighting/Martial Adept Fix | Snippet Codes Explored - Subclasses | Snippet Math Theory | Homebrew Weapons Explained
Check out my: FEATS | MAGIC ITEMS | MONSTERS | SUBCLASSES Artificer Specialist: Weaveblade
Dndbeyond images not loading A PERMANENT WORKAROUND!!! (thank you Jay_Lane)
Haven't cleared my ratings cookie yet today, so I'm coming to interact on the forum first. I've taken to referring to this issue as "getting rid of the rat" ... Ugh, images not loading again - time to look for the rat in the house, and kill it.
I'll just add, again, for the record - the appearance of a correlation between this issue and AboveVTT is due to a lurking variable, not to causation. AboveVTT users interact with a broader range of image files hosted on DDB more directly / more frequently... so AboveVTT users know something is wrong across the board sooner than an average user that might think "oh, that's weird, the images in that one source book didn't load" and then just move on.
and, IMO, AboveVTT users are a fairly dedicated and tech-involved crowd (since many/most of 'em are actively helping to code and otherwise develop the VTT collaboratively) - so AboveVTT users are ALSO extra likely to self-report here on the forums when we've noticed something wonky. This creates a misleading proportion of AboveVTT users in the forum "sample size."
My current question is based entirely on curiosity: modern internet users interact with zillions of rating systems online every day. Facebook likes, Netflix likes, ups and downvotes on reddit, any website that tracks "favorites" or "frequently purchased" like a grocery store or a merch vendor.... All of these sites surely have some sort of cookies tracking the users' input, and passing it back and forth to preload that info rather than re-load every site visit. Sooooooo... why have I (and other "average" internet users) never seen anything like this before on any of those other sites that also track user ratings of some sort? Is there something that DDB coded differently or something?
Reminder that forum upvotes might negatively effect the infinite size of the 'ratings cookie.' And also, my personal note that I would absolutely be upvoting some of these wonderful comments and attempts to help resolve the issue with experiential data.
and now I'm off to clean my ratings cookie for the day. Cheers ~ 💜
💜 Spes Æternum Oritur 💜
Has there been any DDB staff acknowledgment of this issue? Any responses to this thread in the past 6 months?
The moderators have seen it (back track in this thread), commented and recommended clearing cookies.
Whether the developers have seen it, acknowledge it, or if it is in their backlog isn't clear. But that is the case with most complex issues, so that isn't new. It is however quite irksome.
Considering that users seem to have tracked down the problems and recommended solutions. It is quite irksome, indeed.
!!!! Well that's just great. I had my current primary D&D beyond browser open, and I accidentally clicked on my notifications , thus bringing me to this thread. I closed the tab. But it was too late. All of my portraits are broken again. And despite deleting the ratings cookie multiple times, using cookie editor extension; they remain broken.
Having the same issue, nothing I do seems to fix it. This has effected most images on the website, including my homebrew pictures. Can we get a fix please staff? Cleared all cookies and data at great cost to my time and my homebrew races pictures are still broken. I managed to get my profile picture to work again after reuploading it. That trick refuses to work for the homebrew races though.
Cleared all the cookies. Still not working. This is a site issue, not a "cookies" issue.
If you want sugar coating, go buy a dessert....
Its a combination of large cookies, and site design. And it isn't unique to this site either. But as you have noticed, not all cookie clears actually work as you would expect. I had to do the following in edge to fix it for me:
But you are correct; it is a site issue. Mairondil, Cyrantir and I have spent a lot of passion time on the root cause that the server code responds with an error, when the client sends up a cookie that is too large, and then the server refuses to send back the file.
All we have client side are workarounds; the server implementation needs adjustment (see Honza's discussion for developer options). But until then we have to be patient.
How do we clear the cache for ONLY dndbeyond on the Chrome browser?
Quickest method I've found to work around this issue.
How to: Replace DEX in your AC | Jump & Suffocation stats | Build a (Spell & class effect buff system | Wild Shape effect system) | Tool Proficiencies as Custom Skills | Spells at higher levels explained | Superior Fighting/Martial Adept Fix | Snippet Codes Explored - Subclasses | Snippet Math Theory | Homebrew Weapons Explained
Check out my: FEATS | MAGIC ITEMS | MONSTERS | SUBCLASSES Artificer Specialist: Weaveblade
Dndbeyond images not loading A PERMANENT WORKAROUND!!! (thank you Jay_Lane)
Step 1 didn't work - deleting the Ratings cookie - it was only 2847 bytes long, not that long really?
I don't want to do Step 2, since I don't want to flush the cache for every single web site - I only want it fixed on dndbeyond.com
If you aren't seeing your background image, then set your browser window to at least 1921 pixels wide, then the full image appears.
Anything smaller and there's just a white sheet instead of a background image!
(How is THIS bug related to cookies?!)
How long do we have to remain patient? It was first reported May 2021, it is now February 2022.
Try CTRL+Shift+R
Or hit F12 to open the console, then right click the refresh button and Empty Cache and Hard Reload is an option for just dndbeyond.
How to: Replace DEX in your AC | Jump & Suffocation stats | Build a (Spell & class effect buff system | Wild Shape effect system) | Tool Proficiencies as Custom Skills | Spells at higher levels explained | Superior Fighting/Martial Adept Fix | Snippet Codes Explored - Subclasses | Snippet Math Theory | Homebrew Weapons Explained
Check out my: FEATS | MAGIC ITEMS | MONSTERS | SUBCLASSES Artificer Specialist: Weaveblade
Dndbeyond images not loading A PERMANENT WORKAROUND!!! (thank you Jay_Lane)
That solution works, but why do we have to do it?
I haven't had to do it in my entire time using dndbeyond since March 2020.
Reading through this thread, many of us believe this is related to the upvote system on forum posts and published homebrew. It's difficult to quantify though because there's users that upvote posts and homebrew that are unaffected by this issue. I just know my experience and the method I found to quickly get around it.
How to: Replace DEX in your AC | Jump & Suffocation stats | Build a (Spell & class effect buff system | Wild Shape effect system) | Tool Proficiencies as Custom Skills | Spells at higher levels explained | Superior Fighting/Martial Adept Fix | Snippet Codes Explored - Subclasses | Snippet Math Theory | Homebrew Weapons Explained
Check out my: FEATS | MAGIC ITEMS | MONSTERS | SUBCLASSES Artificer Specialist: Weaveblade
Dndbeyond images not loading A PERMANENT WORKAROUND!!! (thank you Jay_Lane)
Well its any cookie that gets too large...so it is a valid question for each person that is impacted, which cookie is the culprit. But getting to the right one isn't exactly something I want to walk my mother through.
If we could get a list that might help the developers. On the other hand, I have no idea where this issue is on their priority list. I'm sure they can mine the server logs to know how often it happens.