I am using beyond20 on chrome, but to be clear, this is not on a character page. This is on the page for rogues https://www.dndbeyond.com/classes/rogue My friend believe it is a cookie issue.
The fact that it seems to be *only* on the rogue page indicates to me that there is something wrong with that specific page... but I decided to investigate. Turning off beyond20 stops the issue.
I am using beyond20 on chrome, but to be clear, this is not on a character page. This is on the page for rogues https://www.dndbeyond.com/classes/rogue My friend believe it is a cookie issue.
The fact that it seems to be *only* on the rogue page indicates to me that there is something wrong with that specific page... but I decided to investigate. Turning off beyond20 stops the issue.
The issue is not with the page, it's with Beyond20. The fact that disabling Beyond20 resolves the issue is evidence of that. This is why we recommend against using such third party extensions
I am using beyond20 on chrome, but to be clear, this is not on a character page. This is on the page for rogues https://www.dndbeyond.com/classes/rogue My friend believe it is a cookie issue.
The fact that it seems to be *only* on the rogue page indicates to me that there is something wrong with that specific page... but I decided to investigate. Turning off beyond20 stops the issue.
The issue is not with the page, it's with Beyond20. The fact that disabling Beyond20 resolves the issue is evidence of that. This is why we recommend against using such third party extensions
None of the other pages have any issues. It's just the Rogue page, where something is different from the other pages.
You can recommend against using third-party extensions, but the reality is that without this extension, I (and I assume others) would probably not use DDB as heavily.
I'd appreciate if staff could take a look into this and, if possible, fix whatever the discrepancy is.
I am using beyond20 on chrome, but to be clear, this is not on a character page. This is on the page for rogues https://www.dndbeyond.com/classes/rogue My friend believe it is a cookie issue.
The fact that it seems to be *only* on the rogue page indicates to me that there is something wrong with that specific page... but I decided to investigate. Turning off beyond20 stops the issue.
The issue is not with the page, it's with Beyond20. The fact that disabling Beyond20 resolves the issue is evidence of that. This is why we recommend against using such third party extensions
None of the other pages have any issues. It's just the Rogue page, where something is different from the other pages.
You can recommend against using third-party extensions, but the reality is that without this extension, I (and I assume others) would probably not use DDB as heavily.
I'd appreciate if staff could take a look into this and, if possible, fix whatever the discrepancy is.
The discrepancy is with the extension and not something D&D Beyond can fix
Because one of the user-posted comments on that article contains something that reacts with Beyond20. This is apparently not the first time it’s happened; apparently the same thing happened on the Wizard page a while ago.
The staff have the ability to edit the user’s comment to rectify the issue, which is apparently what happened when the Wizard page suffered the same issue. I’m not sure why they haven’t in this case.
More broadly, it would be nice if there were some stopgap to prevent this issue from occurring in the first place—but I do acknowledge that might not be possible.
Because one of the user-posted comments on that article contains something that reacts with Beyond20. This is apparently not the first time it’s happened; apparently the same thing happened on the Wizard page a while ago.
The staff have the ability to edit the user’s comment to rectify the issue, which is apparently what happened when the Wizard page suffered the same issue. I’m not sure why they haven’t in this case.
More broadly, it would be nice if there were some stopgap to prevent this issue from occurring in the first place—but I do acknowledge that might not be possible.
This was really helpful insight, thanks. I wasn't aware of the historical issue.
I checked the comments and it looks like another moderator helped resolve the issue, as it's no longer occurring.
Because one of the user-posted comments on that article contains something that reacts with Beyond20. This is apparently not the first time it’s happened; apparently the same thing happened on the Wizard page a while ago.
The staff have the ability to edit the user’s comment to rectify the issue, which is apparently what happened when the Wizard page suffered the same issue. I’m not sure why they haven’t in this case.
More broadly, it would be nice if there were some stopgap to prevent this issue from occurring in the first place—but I do acknowledge that might not be possible.
Just found that thread. It was Alertify tags in a comment that caused the issue. And a staff member DID intervene to fix it in that case which is great. The issue seems to have subsided so either we got some help here from either side. Thanks fellow commentors!
For a couple days now multiple people in my group have reported that the rogue class page just keeps reloading over and over. Very strange!
Is your group by chance using an extension such as Beyond20?
Find my D&D Beyond articles here
I have been having the same issue, as well as a friend of mine. So it seems to be a widespread problem...
Again, are you by any chance using an extension such as Beyond20 (or any other extension that interacts with D&D Beyond or modifies website data)?
I'm not seeing this issue, but the only other time I have heard it reported, it was caused by the Beyond20 extension
Find my D&D Beyond articles here
I am using beyond20 on chrome, but to be clear, this is not on a character page. This is on the page for rogues https://www.dndbeyond.com/classes/rogue My friend believe it is a cookie issue.
The fact that it seems to be *only* on the rogue page indicates to me that there is something wrong with that specific page... but I decided to investigate. Turning off beyond20 stops the issue.
The issue is not with the page, it's with Beyond20. The fact that disabling Beyond20 resolves the issue is evidence of that. This is why we recommend against using such third party extensions
Find my D&D Beyond articles here
None of the other pages have any issues. It's just the Rogue page, where something is different from the other pages.
You can recommend against using third-party extensions, but the reality is that without this extension, I (and I assume others) would probably not use DDB as heavily.
I'd appreciate if staff could take a look into this and, if possible, fix whatever the discrepancy is.
The discrepancy is with the extension and not something D&D Beyond can fix
You should contact the creator of the extension
Find my D&D Beyond articles here
Why is Beyond 20 specifically effecting the Rogue page do you think?
Because one of the user-posted comments on that article contains something that reacts with Beyond20. This is apparently not the first time it’s happened; apparently the same thing happened on the Wizard page a while ago.
The staff have the ability to edit the user’s comment to rectify the issue, which is apparently what happened when the Wizard page suffered the same issue. I’m not sure why they haven’t in this case.
More broadly, it would be nice if there were some stopgap to prevent this issue from occurring in the first place—but I do acknowledge that might not be possible.
This was really helpful insight, thanks. I wasn't aware of the historical issue.
I checked the comments and it looks like another moderator helped resolve the issue, as it's no longer occurring.
Just found that thread. It was Alertify tags in a comment that caused the issue. And a staff member DID intervene to fix it in that case which is great. The issue seems to have subsided so either we got some help here from either side. Thanks fellow commentors!
Nice! Glad to hear it got fixed!
-
View User Profile
-
View Posts
-
Send Message
ModeratorYes. Somebody found the exact comment causing the issue and reported it. I've removed the offending code from the comment.
Homebrew Rules || Homebrew FAQ || Snippet Codes || Tooltips
DDB Guides & FAQs, Class Guides, Character Builds, Game Guides, Useful Websites, and WOTC Resources
Thank you for doing that!
Thanks, you're a huge help!