Discuss Scratch
- Discussion Forums
- » Bugs and Glitches
- » Issues with reports not working, and how to fix them
- mrsrec
-
500+ posts
Issues with reports not working, and how to fix them
Currently the Scratch site is somewhat unstable, with some pages not loading or showing the Whoops! error. Sometimes comments won't post unless you attempt them several times. This is an issue that multiple people have noticed.
However, among the most concerning are the fact that reporting something will sometimes fail. That's not a huge deal as if you know it failed you can simply try again. However, sometimes it may look as though the report has succeeded even if it has failed. And to make things even more complex, how to tell if it really worked or not depends on what you're reporting– a project, a comment, or something else. That's why I have created this topic, so that people can check.
Reporting Projects
Projects are the easiest, because if it says the report has successfully gone through, then it has– if it failed, you'll know that it failed. Reporting a project can fail either via in two ways: one of them will simply tell you that it has failed:

The other way is for the report box to simply hang forever. If it's been 5-10 seconds and the report still hasn't confirmed as having gone through, it's best to copy your report text, refresh the page and try again.
Sometimes, reporting a project can just continuously fail no matter how many times you try. If it doesn't work even after multiple attempts, you can always report it via the Contact Us page.
Reporting Comments (projects/studios)
Pay attention when reporting comments on projects and studios, because sometimes a dialog box saying the report worked may appear, even if it did not work. This confirmation looks like this:

The way to check if reporting a comment worked is to check if the comment turns pink. A comment that was successfully reported looks like this:

If the pink border does not show up around the comment within a few seconds, the report likely failed (even if a dialog box said it succeeded) and you should try again until the comment turns pink. Once the comment turns pink, it has been successfully reported.
Reporting Comments (profiles)
Comments on user profiles are similar to on projects or studios, the main difference being that the (somewhat misleading) dialog box after reporting does not show up. Instead, the dialog box simply closes and the comment may or may not turn pink. A successfully reported comment looks like this:

If it does not turn pink, just like with project or studio comments, try again until it does.
—-
These issues have been brought to the Scratch Team's attention, though they are already spending a lot of time working to make the site more stable in general, it is hoped they will make it more clear when a report has or has not worked, but in the meantime, I'm posting this information here to let everyone know– it ensures community safety, because if people think they have reported something when they haven't, this is obviously bad and can leave a lot of inappropriate content on the site, so I am putting this information out there.
Also, try not to report things that aren't inappropriate just to test this stuff out – all of the above examples were either reports that were made to fail, or legitimately inappropriate comments that I inspect-elemented to have my own name and text. Let's not make the Scratch Team's job any harder than it already is.
However, among the most concerning are the fact that reporting something will sometimes fail. That's not a huge deal as if you know it failed you can simply try again. However, sometimes it may look as though the report has succeeded even if it has failed. And to make things even more complex, how to tell if it really worked or not depends on what you're reporting– a project, a comment, or something else. That's why I have created this topic, so that people can check.
Reporting Projects
Projects are the easiest, because if it says the report has successfully gone through, then it has– if it failed, you'll know that it failed. Reporting a project can fail either via in two ways: one of them will simply tell you that it has failed:

The other way is for the report box to simply hang forever. If it's been 5-10 seconds and the report still hasn't confirmed as having gone through, it's best to copy your report text, refresh the page and try again.
Sometimes, reporting a project can just continuously fail no matter how many times you try. If it doesn't work even after multiple attempts, you can always report it via the Contact Us page.
Reporting Comments (projects/studios)
Pay attention when reporting comments on projects and studios, because sometimes a dialog box saying the report worked may appear, even if it did not work. This confirmation looks like this:

The way to check if reporting a comment worked is to check if the comment turns pink. A comment that was successfully reported looks like this:

If the pink border does not show up around the comment within a few seconds, the report likely failed (even if a dialog box said it succeeded) and you should try again until the comment turns pink. Once the comment turns pink, it has been successfully reported.
Reporting Comments (profiles)
Comments on user profiles are similar to on projects or studios, the main difference being that the (somewhat misleading) dialog box after reporting does not show up. Instead, the dialog box simply closes and the comment may or may not turn pink. A successfully reported comment looks like this:

If it does not turn pink, just like with project or studio comments, try again until it does.
—-
These issues have been brought to the Scratch Team's attention, though they are already spending a lot of time working to make the site more stable in general, it is hoped they will make it more clear when a report has or has not worked, but in the meantime, I'm posting this information here to let everyone know– it ensures community safety, because if people think they have reported something when they haven't, this is obviously bad and can leave a lot of inappropriate content on the site, so I am putting this information out there.
Also, try not to report things that aren't inappropriate just to test this stuff out – all of the above examples were either reports that were made to fail, or legitimately inappropriate comments that I inspect-elemented to have my own name and text. Let's not make the Scratch Team's job any harder than it already is.
Last edited by mrsrec (Aug. 24, 2024 19:49:30)
- breakfast_for_dinner
-
1000+ posts
Issues with reports not working, and how to fix them
very informative!! congrats on the sticky ^^
- Misabell
-
83 posts
Issues with reports not working, and how to fix them
Omg yes, thank you for this!
- EDawg2011
-
1000+ posts
Issues with reports not working, and how to fix them
I refreshed the page and it's still hanging forever. The other way is for the report box to simply hang forever. If it's been 5-10 seconds and the report still hasn't confirmed as having gone through, it's best to copy your report text, refresh the page and try again. Projects are the easiest, because if it says the report has successfully gone through, then it really has.
- mrsrec
-
500+ posts
Issues with reports not working, and how to fix them
Yes, that's been happening to me as well. Unfortunately, I can only tell you if it worked or not, I can't make it work more often.I refreshed the page and it's still hanging forever. The other way is for the report box to simply hang forever. If it's been 5-10 seconds and the report still hasn't confirmed as having gone through, it's best to copy your report text, refresh the page and try again. Projects are the easiest, because if it says the report has successfully gone through, then it really has.
There's also been a bit of weirdness with reports not just on the technical side, but on the moderation side as well. Someone posted a project whose description was just “@mrsrec is stupid” and nothing else. I reported it but it wasn't removed. A few days later, just in case that report didn't work (since there's been instability on that in general as laid out in the OP) I wrote to Contact Us. And no answer. This problem may be a bit deeper than my OP shows. I am hoping a developer or someone can comment on the site issues in general– even though I'm sure they're already spending a lot of time working on just keeping the site up, keeping the community safe is just as important.
- PaperMarioFan2024
-
100+ posts
Issues with reports not working, and how to fix them
I like how everything is worded so formatively.
What “happened” to you, exactly? IT HAPPENED TO ME
Last edited by PaperMarioFan2024 (Aug. 25, 2024 18:37:08)
- bren319
-
5 posts
Issues with reports not working, and how to fix them
Excuse me, I have a problem with reporting. When I try to report some projects, it takes forever to load, but they never submit. What's going on? Honestly, I want to report some projects that sound like I could get harassed more, but surprisingly, they're not reporting. Why is sending reports slow?
- mrsrec
-
500+ posts
Issues with reports not working, and how to fix them
Yeah, usually just report a few times, but for projects in particular it seems like sometimes they just may never go through even if you try like 15 times.In those cases you can use Contact Us but it's a bit slow. Excuse me, I have a problem with reporting. When I try to report some projects, it takes forever to load, but they never submit. What's going on? Honestly, I want to report some projects that sound like I could get harassed more, but surprisingly, they're not reporting. Why is sending reports slow?
On August 17th I reported a project to Contact Us whose description was “@mrsrec is stupid” (this was via Contact Us because reporting directly wasn't possible). Yesterday (August 23rd) I got back a response, and the project is now unshared.
However, Contact Us for every single inappropriate project is still not really a great long-term solution. I hope the developers have an update soon.
Last edited by mrsrec (Aug. 24, 2024 19:50:11)
- medians
-
1000+ posts
Issues with reports not working, and how to fix them
That person literally posted here I like how everything is worded so formatively.What “happened” for you, exactly? IT HAPPENED TO ME
- Depressoy
-
2 posts
Issues with reports not working, and how to fix them
Ooooh no wonder why my report won't go through ;-;
- PaperMarioFan2024
-
100+ posts
Issues with reports not working, and how to fix them
But it still doesn't answer my question: That person literally posted here
#4 What “happened” to you, exactly?Unless maybe I misunderstood and they probably didn't read the OP or something.
Last edited by PaperMarioFan2024 (Aug. 25, 2024 18:37:48)
- A-MARIO-PLAYER
-
1000+ posts
Issues with reports not working, and how to fix them
I've figured the issue out.
Note that this was a legitimate report for tagspamming so false reporting isn't much of an issue here.
Uncaught DOMException: XMLHttpRequest.responseText getter: responseText is only available if responseType is '' or 'text'.
r https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
o https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
setTimeout handler*69005/u/c.onreadystatechange https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
u https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
l https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
n https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
exports https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
use https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
get https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
use https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
exports https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
reportProject https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
r https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
reportProject https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
t https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
handleReportSubmit https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
getProjectThumbnail https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
draw https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
draw https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
getProjectThumbnail https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
t https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
handleReportSubmit https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
t https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
handleSubmit https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
t https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
submit https://scratch-mit-edu.ezproxyberklee.flo.org/js/projects.bundle.js:2
s https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
h https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
_ https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
_ https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
st https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
at https://scratch-mit-edu.ezproxyberklee.flo.org/js/common.bundle.js:2
common.bundle.js:2
- mrsrec
-
500+ posts
Issues with reports not working, and how to fix them
This seems to *still* be happening occasionally! It is happening a lot less often, but sometimes project reports are not going through.
Last edited by mrsrec (Oct. 18, 2024 16:49:21)
- alboxer2000
-
500+ posts
Issues with reports not working, and how to fix them
I think I know what happened: when I try to send more than 2 reports, they don't work, maybe that's why!
- mihatshop
-
36 posts
Issues with reports not working, and how to fix them
removed–don't name names
Last edited by spectre_specs (Oct. 27, 2024 15:39:45)
- luckybushes
-
20 posts
Issues with reports not working, and how to fix them
When try to comment on groups, it wont work? can I get help?
- mrsrec
-
500+ posts
Issues with reports not working, and how to fix them
I will report this to be un-stickied as it doesn't seem to be happening as often anymore. Can always bump this topic if it starts happening again.
Last edited by mrsrec (Nov. 6, 2024 12:09:37)
- mrsrec
-
500+ posts
Issues with reports not working, and how to fix them
Are you still having this issue? I reported it to be un-stickied because it didn't seem to be happening anymore. Is it still happening? Bump
- Discussion Forums
- » Bugs and Glitches
-
» Issues with reports not working, and how to fix them