mirror of
https://github.com/jwilsson/spotify-web-api-php.git
synced 2026-04-27 07:55:49 +03:00
[GH-ISSUE #118] Internal Server Error #71
Labels
No labels
bug
docs
enhancement
enhancement
enhancement
feedback wanted
good first issue
help wanted
help wanted
help wanted
invalid
pull-request
question
question
upstream
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/spotify-web-api-php#71
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @justrealmilk on GitHub (Mar 21, 2018).
Original GitHub issue: https://github.com/jwilsson/spotify-web-api-php/issues/118
Haven't had one of these useless Apache error pages in years.
Turned on PHP error display everywhere and got nothing.
This is in the server log.
I followed the authorization code flow quickstart and narrowed it down to
$session->requestAccessToken($_GET['code']);in the callbackIt grabs the code from Spotify fine and then blows up. I looked at the function in Session.php and it seems to simple to not work so I dunno haha
@justrealmilk commented on GitHub (Mar 21, 2018):
I should note: I'm not using Composer - I'm just doing the inline
require_oncebusiness@jwilsson commented on GitHub (Mar 21, 2018):
Hi!
Could you post the code you're using?
Thanks!
@justrealmilk commented on GitHub (Mar 21, 2018):
@jwilsson commented on GitHub (Mar 22, 2018):
Hmm, nothing strange there.
Could you drop a
error_reporting(E_ALL);at the top and see if we get any better errors? You might need aini_set('display_errors', 'on');too.@justrealmilk commented on GitHub (Mar 22, 2018):
As I said, I already did that to no effect. I even turned them on in Session.php
@jwilsson commented on GitHub (Mar 26, 2018):
Right, sorry!
I don't know what to tell you, though. I've never seen that error message before, and a quick Google search gives all kind of different reasons for it. I guess you'll just have to try one of those solutions for it.