Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors are hard to track down #18

Open
durkie opened this issue Jun 1, 2016 · 2 comments
Open

Errors are hard to track down #18

durkie opened this issue Jun 1, 2016 · 2 comments

Comments

@durkie
Copy link
Collaborator

durkie commented Jun 1, 2016

I'll get console errors that say: VM14878:1 Uncaught SyntaxError: Unexpected token S in JSON at position 17 -- so I know something went wrong, but I have to hunt through the Network tab to find it:

persons.php?id=1 returned:

{"error":{"text":SQLSTATE[42S22]: Column not found: 1054 Unknown column 'active' in 'where clause'}}

which isn't valid JSON, so the error doesn't get reported.

(I'll make sure to update my database and add the active column)

@ThePlushEater
Copy link

I am making a excel spread sheet to categorize and list all possible errors to make a more consistent error handling. https://github.com/PublicDesignWorkshop/FoodParent2.0/blob/master/serverconfig/errorlist.xlsx

@durkie
Copy link
Collaborator Author

durkie commented Jun 28, 2016

Another example of this: when I'm uploading an image, if the server returns any sort of error then it's only displayed in devtools and the site just says "Uploading..." forever. How about unless the server returns HTTP 200, then it displays the error along the bottom of the map?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants