I can confirm this. Same thing happens to me. No matter if the Username and Password input fields are empty or if there’s some text inserted, if you click the Login button, it display this error:
Fatal error: Call to a member function get_option() on a non-object in /…/…/public_html/[site-name]/wp-content/plugins/theme-my-login/modules/custom-redirection/custom-redirection.php on line 93
This only happens with the widget login and NOT with login that’s inside of some page inserted via shortcode [theme-my-login].
So widget works only if you enter valid credentials. But if you enter wrong credentials, it breaks the site.
tried adding default_action=”login” still having this problem too
I’ve discovered that this problem happens only if you create some page (for example Login) and add the [theme-my-login] shortcode into that page, and then if you try to log-in through the Theme My Login Widget but you enter wrong credentials. Something to do with the fact that you can’t have 2 instances of the same log-in form (1 on the page and 1 in the widget area) on the same page. Funny thing is that if you’re on the Login page (with another log-in form in the widget area) and you try to log-in using page form (not the widget form) and you give wrong credentials, it behaves normally by displaying the error message.
Funny thing is that if you’re on the Login page (with another log-in form in the widget area) and you try to log-in using page form (not the widget form) and you give wrong credentials, it behaves normally by displaying the error message.
I have a security plugin suppressing the display of errors, so I just get returned to that same login page. However, and consistent with the reports in this thread, wrong credentials in the widget box lands me on a strange login page with no “Log In” button to click.
Same here – I’ve got some instances of this message in my log files.
Hi. I tried to comment out the function called in “modules/custom-redirection/custom-redirection.php” on line 93, and everything seems to work.
The function of the redirection model is a callback called by the hook “login_form” in login-form.php, so you can comment it out without a fatal error, BUT I really don’t know if this hack has some other effect.
According to the commented source, the function is including “_wp_original_referer” from the hidden fields of login form: maybe if a user wants to login to access to some protected resource, he were nota able to come back directly to the page he was looking at.
