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
Using wrong credentials, Wordpress automatically calls a function that generates the lost password login. Since this plugin hook an event that occurs early, the method that produces permalinks is not already available and generates an error.
Hooking the plugin after that moment make the login feature unavailable. It seems that hacking the plugin adding
$GLOBALS['wp_rewrite'] = new WP_Rewrite();
avoid this error but generates another one
Undefined property: WP_Error::$ID in /srv/www/test.com/current/wp/wp-includes/class-wp-user.php on line 165
It's a e_notice so think it could be ignored, but I am wondering if there is any way of make basic auth 100% working without errors at all. Any ideas?
The text was updated successfully, but these errors were encountered:
BrianHenryIE
added a commit
to BrianHenryIE/Basic-Auth
that referenced
this issue
Aug 9, 2017
Sometimes, with an incorrect username and password (or using email address rather than username, which made `wp_authenticate_username_password` error) when `$user = wp_authenticate( $username, $password );` errored, it would call `$wp_rewrite->get_page_permastruct();` before `$wp_rewrite` was initialized, returning a 500 server error. In my case, this would happen when I enabled the SkyVerge WooCommerce Print Invoices/Packing Lists plugin.
BrianHenryIE
added a commit
to BrianHenryIE/Basic-Auth
that referenced
this issue
Aug 9, 2017
This is related to #27
Using wrong credentials, Wordpress automatically calls a function that generates the lost password login. Since this plugin hook an event that occurs early, the method that produces permalinks is not already available and generates an error.
Hooking the plugin after that moment make the login feature unavailable. It seems that hacking the plugin adding
avoid this error but generates another one
It's a e_notice so think it could be ignored, but I am wondering if there is any way of make basic auth 100% working without errors at all. Any ideas?
The text was updated successfully, but these errors were encountered: