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

Bug authentification sur utilisateur supplémentaire #2357

Closed
prolibre opened this issue Oct 4, 2016 · 9 comments · Fixed by #2359
Closed

Bug authentification sur utilisateur supplémentaire #2357

prolibre opened this issue Oct 4, 2016 · 9 comments · Fixed by #2359
Labels
Milestone

Comments

@prolibre
Copy link

prolibre commented Oct 4, 2016

Issue details

Aucun soucis avec l'utilisateur admin mais problème lors de l'utilisation d'un compte supplémentaire.
Lors de la connexion on arrive sur la page : URL/login_check

qui retourne :

Oops! An Error Occurred
The server returned a "500 Internal Server Error".

Si je retourne sur l'URL ( en virant /login_check ) je constate que l'authentification a bien eu lieu.

Environment

Debian stable
PHP 5.6.24-0+deb8u1
Wallabag 2.1.1
Install by git ( fresh install )
PDO Mysql

@tcitworld
Copy link
Member

Can you check your server logs ?

@prolibre
Copy link
Author

prolibre commented Oct 4, 2016

Voici les quelques lignes de mon prod.log
Je précise à nouveau qu'en tant qu'admin aucun soucis.

[2016-10-04 09:54:38] request.INFO: Matched route "{route}". {"route":"fos_user_security_check","route_parameters":{"_controller":"Wallabag\\UserBundle\\Controller\\SecurityController::checkAction","_route":"fos_user_security_check"},"request_uri":"https://URL_WALLABAG/login_check","method":"POST"} []
[2016-10-04 09:54:38] security.INFO: User has been authenticated successfully. {"username":"test"} []
[2016-10-04 09:54:38] request.CRITICAL: Uncaught PHP Exception Symfony\Component\Debug\Exception\FatalErrorException: "Error: Call to a member function getLanguage() on null" at /DOSSIER_WALLABAG/wallabag/src/Wallabag/CoreBundle/EventListener/UserLocaleListener.php line 33 {"exception":"[object] (Symfony\\Component\\Debug\\Exception\\FatalErrorException(code: 0): Error: Call to a member function getLanguage() on null at /DOSSIER_WALLABAG/wallabag/src/Wallabag/CoreBundle/EventListener/UserLocaleListener.php:33)"} []
[2016-10-04 09:54:38] security.DEBUG: Stored the security token in the session. {"key":"_security_secured_area"} []

@tcitworld
Copy link
Member

tcitworld commented Oct 4, 2016

Config is not created for the new user. This should have been fixed by #2320, @j0k3r ?

@prolibre
Copy link
Author

prolibre commented Oct 4, 2016

bon ... version inutilisable pour un utilisateur supplémentaire :-(
Je viens d'essayer d'ajouter un contenu est :

500: Internal Server Error
Error: Call to a member function getTaggingRules() on null

[2016-10-04 10:06:12] request.CRITICAL: Uncaught PHP Exception Symfony\Component\Debug\Exception\FatalErrorException: "Error: Call to a member function getTaggingRules() on null" at /DOSSIER_WALLABAG/wallabag/src/Wallabag/CoreBundle/Helper/RuleBasedTagger.php line 103 {"exception":"[object] (Symfony\\Component\\Debug\\Exception\\FatalErrorException(code: 0): Error: Call to a member function getTaggingRules() on null at /DOSSIER_WALLABAG/wallabag/src/Wallabag/CoreBundle/Helper/RuleBasedTagger.php:103)"} []
[2016-10-04 10:06:12] security.DEBUG: Stored the security token in the session. {"key":"_security_secured_area"} []


bon courage :-)

@j0k3r
Copy link
Member

j0k3r commented Oct 4, 2016

Comment tu as créé cet utilisateur supplémentaire?

@prolibre
Copy link
Author

prolibre commented Oct 4, 2016

@j0k3r : j'ai proposé à un copain de s'inscrire (donc via le formulaire public). Du coup j'ai testé de la même manière.
ET ... effectivement en créant le compte via l'admin ça fonctionne :-) je viens de faire l'essai.

@j0k3r
Copy link
Member

j0k3r commented Oct 4, 2016

Tu l'activation du compte par email ou pas?

@j0k3r
Copy link
Member

j0k3r commented Oct 4, 2016

Bon, j'ai la même erreur sur v2.wallabag 😞

@prolibre
Copy link
Author

prolibre commented Oct 4, 2016

oui donc l'utilisateur reçoit bien le mail ( en passant via le formulaire public ). L'activation fonctionne mais ensuite ça bug à tout va.

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

Successfully merging a pull request may close this issue.

3 participants