PHP Version: 7.0.13-1~dotdeb+8.1
MySQL Version: MariaDB 10.1
Expected Behavior:
Login via google
Actual Behavior:
Getting an error 'Whoops, looks like something went wrong' when accessing 'http://rcit-wiki.redclay.k12.de.us/login/service/google/callback' per https://www.bookstackapp.com/docs/admin/social-auth
I can register my account, and confirmed it is available inside the user settings. However, logging in with Google gives the Whoops error. The API keys, permissions, etc all appear to be set properly.
There is nothing in the apache2 error logs nor in the storage\logs folder. I'm assuming since I can register, the API is setup properly.
Any suggestions is appreciated. Thanks.
I enabled debugging. Here is the error.
ReflectionException in compiled.php line 8535:
Method BookStack\Http\Controllers\Auth\RegisterController::getSocialLogin() does not exist
in compiled.php line 8535
at ReflectionMethod->__construct('BookStack\Http\Controllers\Auth\RegisterController', 'getSocialLogin') in compiled.php line 8535
at Route->signatureParameters('Illuminate\Database\Eloquent\Model') in compiled.php line 8222
at Router->substituteImplicitBindings(object(Route)) in compiled.php line 9977
at SubstituteBindings->handle(object(Request), object(Closure)) in compiled.php line 9870
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in compiled.php line 3151
at VerifyCsrfToken->handle(object(Request), object(Closure)) in compiled.php line 9870
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in compiled.php line 13464
at ShareErrorsFromSession->handle(object(Request), object(Closure)) in compiled.php line 9870
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in compiled.php line 11907
at StartSession->handle(object(Request), object(Closure)) in compiled.php line 9870
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in compiled.php line 13210
at AddQueuedCookiesToResponse->handle(object(Request), object(Closure)) in compiled.php line 9870
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in compiled.php line 13147
at EncryptCookies->handle(object(Request), object(Closure)) in compiled.php line 9870
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in compiled.php line 9855
at Pipeline->then(object(Closure)) in compiled.php line 8148
at Router->runRouteWithinStack(object(Route), object(Request)) in compiled.php line 8139
at Router->dispatchToRoute(object(Request)) in compiled.php line 8130
at Router->dispatch(object(Request)) in compiled.php line 2472
at Kernel->Illuminate\Foundation\Http\{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in Debugbar.php line 51
at Debugbar->handle(object(Request), object(Closure)) in compiled.php line 9870
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in compiled.php line 3213
at CheckForMaintenanceMode->handle(object(Request), object(Closure)) in compiled.php line 9870
at Pipeline->Illuminate\Pipeline\{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing\{closure}(object(Request)) in compiled.php line 9855
at Pipeline->then(object(Closure)) in compiled.php line 2416
at Kernel->sendRequestThroughRouter(object(Request)) in compiled.php line 2400
at Kernel->handle(object(Request)) in index.php line 53
@mackcoding Thanks for pointing out this issue. It was indeed an error caused by the latest update. I will release a bugfix release soon to cover this.
Thank you, Dan. Good to know I wasn't going crazy 馃憤
Most helpful comment
@mackcoding Thanks for pointing out this issue. It was indeed an error caused by the latest update. I will release a bugfix release soon to cover this.