search

OpenSprites / OpenSprites-Origin

The original OpenSprites website, written in PHP. Discontinued - remains for historical reasons. See OpenSprites-Next for the new generation of Scratch resource sharing.
MIT License
19 stars 9 forks source link

[BACKEND] 'Something bad has happened and our servers sent back a bad response' #199

Closed Arinerron closed 8 years ago

Arinerron commented 8 years ago

'Something bad has happened and our servers sent back a bad response. Contact us if this continues'. This message occurs when doing certain actions that include (but are not limited to):

This is extremely important that this gets fixed @OpenSprites/backend-php , because the entire purpose of OpenSprites no longer works, due to this bug.

Arinerron commented 8 years ago

^ I can't assign the entire backend team :P

towerofnix commented 8 years ago

I can't assign the entire backend team :P

whoa @github team please add assigning organization groups o_o

matthewr6 commented 8 years ago

lol php

bates64 commented 8 years ago

lol php

this.

109C commented 8 years ago

I suppose this is why one should not push to master.

matthewr6 commented 8 years ago

lol pushing directly to prod

jamesd-uk commented 8 years ago

This pretty much happens with most uploads.

trumank commented 8 years ago

Has anyone tried a $ git bisect?

Tymewalk commented 8 years ago

@trumank I'll take a look. Does anyone know of the last commit this worked at?

jamesd-uk commented 8 years ago

It hasn't ever been completely reliable, but it was workable in earlier versions of the site - hundreds of commits down the line.

Tymewalk commented 8 years ago

@The-Cheese-Eater Do you have an idea of when that was, or at what release? Also, how would I test the backend?

jamesd-uk commented 8 years ago

Trying to look at when the code worked probably won't help here, this is more analysing and fixing bugs and problems. All the uploader files are here: https://github.com/OpenSprites/OpenSprites/tree/master/public_html/upload. Testing code is a bit difficult because OpenSprites is built around our setup and requires two databases to function. Testing is basically revising over changes for common errors and pushing it to GH, where I can update the site.

QuillzLouis commented 8 years ago

Still, something should be done, it is much more productive to be able to find errors in your code instantly.

Tymewalk commented 8 years ago

@The-Cheese-Eater @QuillzLouis Either way, it's better than nothing. Is there a way to get specific errors from the server? Maybe we're just missing a semicolon :stuck_out_tongue:

Tymewalk commented 8 years ago

Checked the PHP files with php -l, looks like it's not just a missing semicolon.

Arinerron commented 8 years ago

Thank you @The-Cheese-Eater!