Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Alex Hansen

Custemers login don't work anymore ? :-(

Recommended Posts

Posted (edited)

I have just updated to version 1.2.0 and I don't know if  this is the reason, but suddenly Custemers login don't work anymore.
Even with new password it will not accept any login at all, not even my own testuser (has always be worked).

When entering wrong password I get the message: Invalid password.

When entering right password I get the meesage: Approval failed.

 

Any idea how to fix this issue?

 

The site: www.sportspower.dk

 

Edited by Alex Hansen

Share this post


Link to post
Share on other sites

"Approval failed" is not thrown by thirtybees core. Maybe some module/override?

Share this post


Link to post
Share on other sites
20 minutes ago, datakick said:

"Approval failed" is not thrown by thirtybees core. Maybe some module/override?

Any suggestions on how to fix this?

Share this post


Link to post
Share on other sites

@Alex Hansen Tried to disable 3rd party modules? There is an option in Performance preferences, to disable them. Then check if works.

If it works, then one one third party modules is doing something wrong.

Share this post


Link to post
Share on other sites
Posted (edited)

As Datakick and Kashir said:
Go to "Advanced Parameters / Performance" and set as on picture:

1079711135_Screenshot_2021-04-03Performance.png.78549820da4c92a2b98b27d0247b6bb7.png

 

I'm always using Bleeding edge ever since this option was introduced in Core Updater and don't have any issues.
I mostly update within couple of hours after I notice there was update on github.

Currently running "Bleeding Edge - Main"

Edited by toplakd

Share this post


Link to post
Share on other sites
2 hours ago, toplakd said:

As Datakick and Kashir said:
Go to "Advanced Parameters / Performance" and set as on picture:

1079711135_Screenshot_2021-04-03Performance.png.78549820da4c92a2b98b27d0247b6bb7.png

 

I'm always using Bleeding edge ever since this option was introduced in Core Updater and don't have any issues.
I mostly update within couple of hours after I notice there was update on github.

Currently running "Bleeding Edge - Main"

Well ... Thank you for your suggestions, but it didn't help me.
Still can't login as a customer.
I think I will contact Datakick for paid support, as I can't solve this my own.

I'm not sure if is the update itself who has made the error, just saying that I (and my custemers) have these problem after the update.

Share this post


Link to post
Share on other sites
2 hours ago, Kashir2000 said:

@Alex Hansen Tried to disable 3rd party modules? There is an option in Performance preferences, to disable them. Then check if works.

If it works, then one one third party modules is doing something wrong.

It didn't help 😞
Thank for for 
 suggestion.

 

Share this post


Link to post
Share on other sites

I don't think its the update who has created the problem, because I just tried to go back to old versions without any luck.
Now I have update to 1.3.0-main and still have the same problem.
Maybe something has been overwrittten like an htaccess (can see in FTP that this is updated)?

 

Share this post


Link to post
Share on other sites

did you try to create a new customer account and log out/log in back? Does it work or not?

 

Share this post


Link to post
Share on other sites

Ok. So to debug this, please follow instructions:
 

  • Download your shop onto hardDrive (direcotries: modules, classes, controllers, overrides mainly). Do not download pictures.
  • Perform a test search for message "Approval failed" and locate which file is emitting this error.
  • Come back, and report.

Just a guess, but this may be some 3rd party module or modification integrated as override etc. Maybe some kind of CAPTCHA?
Some modules can modify core controllers and classes by preg replaces.

Share this post


Link to post
Share on other sites

I had a look at it. I created an account; logged out and tried to login again. I couldn't login again but I always got the same error - no matter whether the password was right or not.

My gut feeling is that it could have something to do with groups.

Share this post


Link to post
Share on other sites
23 hours ago, datakick said:

did you try to create a new customer account and log out/log in back? Does it work or not?

 

Hi Datakick

I have tried this, but it don't work 😞

 

Share this post


Link to post
Share on other sites
2 hours ago, musicmaster said:

I had a look at it. I created an account; logged out and tried to login again. I couldn't login again but I always got the same error - no matter whether the password was right or not.

My gut feeling is that it could have something to do with groups.

Thanks for trying, but I experience the same thing 😞

 

Share this post


Link to post
Share on other sites
5 hours ago, Alex Hansen said:

Thanks for trying, but I experience the same thing 😞

 

Do you use the knowband OPC? Have you asked them if it is is compatible with TB .2?

Share this post


Link to post
Share on other sites

If ALL you did was update to 1.2.0 and THEN it stopped working....If thats all that you did, and it worked before... I would have simply restored my files via the core updaters backup files.  If you look in your admin folder there are backups from when you used the updater, like CoreUpdaterBackup-(date).  I would have just copied those files over your present setup.  As you have used the core updater since the update to 1.2.0,  it makes it a little more complicated probably.  Have you tried to delete cache files, both theme and system, manually?

Share this post


Link to post
Share on other sites
On 4/4/2021 at 9:26 PM, SLiCK_303 said:

If ALL you did was update to 1.2.0 and THEN it stopped working....If thats all that you did, and it worked before... I would have simply restored my files via the core updaters backup files.  If you look in your admin folder there are backups from when you used the updater, like CoreUpdaterBackup-(date).  I would have just copied those files over your present setup.  As you have used the core updater since the update to 1.2.0,  it makes it a little more complicated probably.  Have you tried to delete cache files, both theme and system, manually?

As mentioned earlier, I am absolutely NOT sure that it is the update itself that is the reason why my customer login no longer works.
It's just after the update that I have been made aware that it no longer works.
I have a test account, which I myself have used by March 4 without any problems, so at that time it worked without any problems.
I do not remember making any other changes since then, which is why I initially thought it was the update that was causing the problem.
Now I suspect more closely the theme I use (IQIT warehouse). Maybe even a combination of the update and the theme.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...