Not able to login backoffice website working

[charlestcr]

Pls help not able to login back office... website is working ...

while logging to back office its rounding only...after some times i am getting error message(pls check attached images)

prestashop version is 1.6.1.18.. pls help very urgent..

Thank You.

[Knowband Plugins]

Might be due to addon store down issue. (We have noticed the same issue in one of our store)

Use the following method mentioned in the URL below.

https://www.prestashop.com/forums/topic/908018-error-found-premature-end-of-data-in-tag/

[Inaki919]

We suggest you use this workaround to temporary disable API calls: http://bit.ly/2zIVejJ  

Edited October 9, 2018 by Inaki919 (see edit history)

[Daniele Groff]

13 minutes ago, Inaki919 said:

We suggest you use this workaround to temporary disable API calls: http://bit.ly/2zIVejJ  

Same problem with PS version 1.7.2.4

I've tried your fix but nothing changes.
My frontoffice is working well, but i can't login in my Backoffice (503 error)

someone have found a solution?

[Daniele Groff]

i've renamed the folder /modules/gamification and it actually works

 

[Inaki919]

hace 53 minutos, Daniele Groff dijo:

Same problem with PS version 1.7.2.4

I've tried your fix but nothing changes.
My frontoffice is working well, but i can't login in my Backoffice (503 error)

someone have found a solution?

 

It is the solution that prestashop has facilitated. I have done it and it has been solved. Can you show the files that you have modified?

[anjoalre]

Renaming the folder /modules/gamification also worked for me! Thanks Daniele Groff!

[contactovisual]

I had this same problem after using Autoupdate (1-Click Upgrade), from version 1.7.6.4 to 1.7.6.8

It all went well, the frontoffice is fine, but I couldn't login in the backoffice. Always returning to the same Login screen.

After desperate hours digging and searching here, I finally found out that since Prestashop 1.7.6.6 there are 2 new tables in the database: ps_employee_session and ps_customer_session. The information can be found in github: https://github.com/PrestaShop/PrestaShop/releases

These tables are crucial to login. Without them, we can never success the login. For some reason the autoupdate procedure did not add these tables.

 

Solution:

If you can access the MySQL database, add these 2 tables

CREATE TABLE `PREFIX_employee_session` (
  `id_employee_session` int(11) unsigned NOT NULL auto_increment,
  `id_employee` int(10) unsigned DEFAULT NULL,
  `token` varchar(40) DEFAULT NULL,
  PRIMARY KEY `id_employee_session` (`id_employee_session`)
) ENGINE=ENGINE_TYPE DEFAULT CHARSET=utf8 COLLATION;

CREATE TABLE `PREFIX_customer_session` (
  `id_customer_session` int(11) unsigned NOT NULL auto_increment,
  `id_customer` int(10) unsigned DEFAULT NULL,
  `token` varchar(40) DEFAULT NULL,
  PRIMARY KEY `id_customer_session` (`id_customer_session`)
) ENGINE=ENGINE_TYPE DEFAULT CHARSET=utf8 COLLATION;

Remember to replace  PREFIX_ by your tables prefix (mine is the usual ps_), and COLLATION by the one used in your tables, or simply remove it from the code.

After that, I could access again the backoffice.
Note: A fresh Prestashop installation will add the tables, which is also a solution.

Nelson / Contacto Visual

 

 

 

Edited October 7, 2020 by contactovisual (see edit history)

[dwfcommunication]

On 10/7/2020 at 10:09 AM, contactovisual said:

I had this same problem after using Autoupdate (1-Click Upgrade), from version 1.7.6.4 to 1.7.6.8

It all went well, the frontoffice is fine, but I couldn't login in the backoffice. Always returning to the same Login screen.

After desperate hours digging and searching here, I finally found out that since Prestashop 1.7.6.6 there are 2 new tables in the database: ps_employee_session and ps_customer_session. The information can be found in github: https://github.com/PrestaShop/PrestaShop/releases

These tables are crucial to login. Without them, we can never success the login. For some reason the autoupdate procedure did not add these tables.

 

Solution:

If you can access the MySQL database, add these 2 tables

CREATE TABLE `PREFIX_employee_session` (
  `id_employee_session` int(11) unsigned NOT NULL auto_increment,
  `id_employee` int(10) unsigned DEFAULT NULL,
  `token` varchar(40) DEFAULT NULL,
  PRIMARY KEY `id_employee_session` (`id_employee_session`)
) ENGINE=ENGINE_TYPE DEFAULT CHARSET=utf8 COLLATION;

CREATE TABLE `PREFIX_customer_session` (
  `id_customer_session` int(11) unsigned NOT NULL auto_increment,
  `id_customer` int(10) unsigned DEFAULT NULL,
  `token` varchar(40) DEFAULT NULL,
  PRIMARY KEY `id_customer_session` (`id_customer_session`)
) ENGINE=ENGINE_TYPE DEFAULT CHARSET=utf8 COLLATION;

Remember to replace  PREFIX_ by your tables prefix (mine is the usual ps_), and COLLATION by the one used in your tables, or simply remove it from the code.

After that, I could access again the backoffice.
Note: A fresh Prestashop installation will add the tables, which is also a solution.

Nelson / Contacto Visual

 

 

 

THANKS ! It worked for me