Several users have reported authentication failure. Piwigo was working as expected, the users were simply using their email address as username (as many web applications do).
It would be more convenient if Piwigo could allow/understand when a visitors tries to authenticate with its email address (that he never forgets, as opposed to the Piwigo username).
For now, the problem I see is that you can use an email address as username. Imagine 2 users 👍
Then what happens when you submit "alfonso@protonmail.com" on identification.php ? I would say, we match in priority the username (which does not follow an email address pattern 99.999% of the time) and if nothing matches, try among email address.
Reminder: email addresses must be unique in Piwigo.
Several users have reported authentication failure. Piwigo was working as expected, the users were simply using their email address as username (as many web applications do).
It would be more convenient if Piwigo could allow/understand when a visitors tries to authenticate with its email address (that he never forgets, as opposed to the Piwigo username).
For now, the problem I see is that you can use an email address as username. Imagine 2 users 👍
* username "alfonso" with email address "alfonso@protonmail.com"
* username "alfonso@protonmail.com" with email address "very@funny.com"
Then what happens when you submit "alfonso@protonmail.com" on identification.php ? I would say, we match in priority the username (which does not follow an email address pattern 99.999% of the time) and if nothing matches, try among email address.
Reminder: email addresses must be unique in Piwigo.
<!-- github-sync-id:257021447 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Several users have reported authentication failure. Piwigo was working as expected, the users were simply using their email address as username (as many web applications do).
It would be more convenient if Piwigo could allow/understand when a visitors tries to authenticate with its email address (that he never forgets, as opposed to the Piwigo username).
For now, the problem I see is that you can use an email address as username. Imagine 2 users 👍
Then what happens when you submit "alfonso@protonmail.com" on identification.php ? I would say, we match in priority the username (which does not follow an email address pattern 99.999% of the time) and if nothing matches, try among email address.
Reminder: email addresses must be unique in Piwigo.