by (140 points)
When I attempt to login with a user I created during the installation process, I cannot.  I created "", checked that the user is in the mysql database, which it is, but it doesn't work.

I also cannot see a log anywhere that logs this failed attempt and a reason why it happens.

1 Answer

by (14.9k points)
Hello lifeboy,

most of the times, login errors are simple matters such as mistyping email or password.

first let me ask you : is a valid email address?

If so, then have you tried to simply reset the password by going to http://www.(your-install-domain).com/go - you should receive a new password in your mailbox and then try to log in with this new password.

If you tried all this and still get the same "error", please provide us your error.log (or whatever php error log) file contents.

Regarding not finding logs on this failed login attempts, and if you are running the Apache web server, add this to the .htaccess file in toaster root

php_flag log_errors On
php_flag ignore_repeated_errors On
php_value error_log /path/to/your/erro/log/file

Also you can provide us phpinfo configuration to speed things along.

Let us know if this works for you now, we will make sure this get fixed timely so you can get to work with your install asap :)

Thank you for using SeoToaster!
by (140 points)
edited by
I just noticed that a flag box next to the email box pops up when I hover over it after login failure that says: "login should be a valid email address".

It looks like, as happens with many other sites, overzealous developers check for a "valid" email address based on old (pre-nTLD) names and it doesn't like "".  Can you change the natural expression that tests for this, or better still, scrap the test!  If the email is invalid, it's invalid.  Surely such a test at this stage gives no benefit to the user?  The check should be done against the record in mysql and nothing else.

Also, the changes to .htaccess don't work.  Nothing it logged.  Ubuntu 14.04 with Apache...  

I'm doing a trail for a new client and this is becoming time critical now...  I will try with another email address to see if I can bypass the problem in the meantime, but I need a fix, since the client is also using a new TLD email address, so I will have the same problems as with
by (1.3k points)
edited by
Thanks for your answer, we will consider your suggestion, and in the future will certainly make a new standard validation email address.