Help with error WHERE id_cart = 5852 LIMIT 1

[bnadauld]

I was testing a copy of my 1.6 site on a dev area of my shared hosting before i upgrade it. Now when i go back to the actual live site i get this error - it only shows when i enable my one page checkout module.

Any idea what might be up and what i might try to get it fixed?

 

Table 'panga_2020.ps_kb_checkout_behaviour_stats' doesn't exist
 

SELECT * FROM ps_kb_checkout_behaviour_stats WHERE id_cart = 5852 LIMIT 1

 

 

[musicmaster]

The error message is very clear. A table connected to this module is missing.

Your situation description is less clear:

"I was testing a copy of my 1.6 site on a dev area of my shared hosting before i upgrade it. Now when i go back to the actual live site i get this error - it only shows when i enable my one page checkout module."

It leaves me just puzzled how those two shops interfere.

You could start by cleaning the cache. But if you have somehow mixed up the two databases I am not sure what to think. Re-installing the module is one option.

[bnadauld]

thanks for your help.

I also thought that a table of my db got messed up or deleted -  so i reverted to a backup and then an even older backup. Problem persists. I know that the problem wasn't there in the backup as i ran a test buy previously and everything was fine.

 

In regard to the backup bit: I was wanting to upgrade my store but i was worried that the one click upgrade would ruin the shop - so to test on a dev version: i created a subdomain on another .com domain i had - uploaded all the files via ftp. I then manually did a find replace (notepad++) on a sql backup of my main the store (to the point it to the subdomain url) and uploaded the sql backup to the dev site. I did the upgrade on teh dev site and everything seemed to work. Then this problem with the main site.

My thought was that there was something in the dev site that i upgraded that was still pointing to the main site? Im too much of a noob to know

Edited March 21, 2021 by bnadauld (see edit history)

[musicmaster]

24 minutes ago, bnadauld said:

thanks for your help.

I also thought that a table of my db got messed up or deleted -  so i reverted to a backup and then an even older backup. Problem persists. I know that the problem wasn't there in the backup as i ran a test buy previously and everything was fine.

 

In regard to the backup bit: I was wanting to upgrade my store but i was worried that the one click upgrade would ruin the shop - so to test on a dev version: i created a subdomain on another .com domain i had - uploaded all the files via ftp. I then manually did a find replace (notepad++) on a sql backup of my main the store (to the point it to the subdomain url) and uploaded the sql backup to the dev site. I did the upgrade on teh dev site and everything seemed to work. Then this problem with the main site.

My thought was that there was something in the dev site that i upgraded that was still pointing to the main site? Im too much of a noob to know

It is possible that you replaced something important with this find-and-replace and that that caused the problem.

Anyway, as I said, re-installing is the main option. Some modules also allow a "reset" option.

 

[bnadauld]

As you suggested - I uninstalled the module and this time installed the latest version. It was the db table missing. All sorted

Really appreciate your help (again)!

Thank you!