Upgrading from 1.4.0 causing unable to login to admin backend

[ukclearance]

I have recently tried to upgrade my store from TB 1.4.0 to a newer version, but ever version i have tried to upgrade to (1.5.0, 1.5.1 and 1.60) results in me being unable to login to the admin back end once I logout after the upgrade completes. The error i get when trying to login is:

Quote

 The employee does not exist, or the password provided is incorrect

I know its not an issue with the login or password. And ive even tried creating an additional admin user but that still doesn't allow login. And trying from a different browser and still the same results.
If i restore my 1.4.0 install from backups this allows access to the admin login again. So it definitely something that's happening during the upgrade procedure.

I have 2 stores running TB 1.4.0 on different servers and the one running on Ubuntu with PHP 8.1 upgraded without this issue and allows me login to the admin after the upgrade.
But the other which runs on Oracle Linux and PHP 8.0 is the one i am having issues with.

The only error i got when running the core updater is one that say:

Duplicate entry 'compile' for key 'PRIMARY' 

Other than this error above and the login issue everything else works fine after the upgrade, but obviously not being able to access the admin interface is a major sticking point meaning im unable to upgrade to newer than1.4.0. So any help would be appreciated.

 

 

[the.rampage.rado]

For the login issue try this:
 

And after you regenerate your pass delete this file as anybody would be able to enter your admin when it's present on the server.

[datakick]

9 hours ago, ukclearance said:

The only error i got when running the core updater is one that say:

Duplicate entry 'compile' for key 'PRIMARY' 

This most likely blocks the subsequent database migrations -- maybe new db column signature is not created in tb_employee table.

Try using the script @the.rampage.rado pointed to log in to your store. Then open core updater, and check database differences. Ensure that column signature exists in that table. Then change the password, that should populate this new column

[Yabber]

@datakick I think the only reason for the incomplete update process of thirtybees is the prestashop modules using overrides. Maybe "Core Updater" should disable all overrides before starting the update process?

[ukclearance]

On 1/24/2025 at 12:10 AM, the.rampage.rado said:

For the login issue try this:
 

And after you regenerate your pass delete this file as anybody would be able to enter your admin when it's present on the server.

Thanks. This allowed be to get into the back office and enable developer mode and finish the upgrade. I checked the database and it appears that the error

Duplicate entry 'compile' for key 'PRIMARY' 

Is caused because of

Missing key primary key in table ps_smarty_last_flush This is according the core updater database schema. But hitting fix throws up the duplicate entry error shown above. So i am not sure how to fix this?   Ok so as additional info. I think ive sorted the issue with the missing primary key in the smart_last_flush table. I did a clean install of TB and compared the table between my upgraded and the clean and could see that 'type' filed should be a primary field but it wasn't and i couldnt change it for some reason. So i figured its just easier to delete the table and recreate it the same as in the fresh install and that seemed to sort it. No more errors in core updater

Edited January 27 by ukclearance
Additional Info

[yaniv14]

try to fix other issues for same table before trying this one