Uh oh, that's a 500

[Henry Lau]

Hi,

Really interested in trying out Library. Have followed the steps in the Getting Started with Library section but was having lots of problems with OAuth. Had to put the "http://digital-content-toolkit.herokuapp.com/auth/redirect" in the authorized URIs in the OAuth settings, but now when going to the URL of the heroku app it's giving me a 500 error. The only clue in the console is personalizeHomepage is not defined.

Any ideas?

[Isaac White]

Hey Henry,

The 500 response code is caused by a backend error scenario, so the Chrome console won't tell you what the problem is. The particular error message you are pointing out is a result of the error page having different functionality than normal page, and is to be expected.

Your best bet for figuring out the cause of the problem is probably to look at the application logs and see what might be going wrong. There's a few common pitfalls you might be running into that we're working on documenting as well.

Isaac

[Henry Lau]

Thanks for the tips. It resolved itself in the end.

Henry

[Joe H]

Hi Henry, I've encountered the same issue. Any chance you could let me know what you did / how it resolved itself?

Thanks, Joe

[Henry Lau]

Hi Joe,

I think I had to fiddle about with the settings when I was setting up the OAuth Client.

Henry