You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Laravel introduced fancier email validation in 5.8 (laravel/framework#26503), but made it too permissive by default, supposedly following the RFC exactly (although there are inconsistencies reported). This has caused breaking changes in emails reported as valid even though they may not be: laravel/framework#28233, laravel/framework#27875.
We need to make sure that October overrides Laravel's email validator to make the default filter used email:filter, which uses PHP's built in email validator, instead of email:rfc which isn't even technically accurate to the RFC (reportedly).
Laravel 5.8 introduced a new email validation library, with a more permissive default filter (supposedly, following the RFC). To maintain the expected functionality of October, we have reverted the default back to the 'filter' method, which uses PHP's inbuilt 'filter_var' method.
Fixesoctobercms/october#5070
Originally reported by @datune.
Laravel introduced fancier email validation in 5.8 (laravel/framework#26503), but made it too permissive by default, supposedly following the RFC exactly (although there are inconsistencies reported). This has caused breaking changes in emails reported as valid even though they may not be: laravel/framework#28233, laravel/framework#27875.
We need to make sure that October overrides Laravel's email validator to make the default filter used
email:filter
, which uses PHP's built in email validator, instead ofemail:rfc
which isn't even technically accurate to the RFC (reportedly).We should still support the other filters used, we just need to change the default filter used: https://laravel.com/docs/6.x/validation#rule-email.
The text was updated successfully, but these errors were encountered: