Jump to content
thirty bees forum
  • 0

How to check integrity of database after several updates from 1.0.0 to 1.0.7




I have been experiencing difficulties when my customer pay. I have been using the Adyen module by WebKUL. 

I have explained some of the problems in these two posts. 



Basically, the problem arises when a customer pays. The order status is changed to "Payment accepted" before "Awaiting payment". This screws up the order and invoicing. 


As usual, the module developer didn't want to know once he discovered it was running on Thirty Bees. I installed the module on a fresh install of Prestashop 1.6 and there were no problems. The Apache, CentOS, PHP, MYSQL versions are the same. 

I performed a fresh install of Thirty Bees to see if it was a compatibility issue. There were no problems on the fresh install. 

I reverted to the community theme and disabled all of the modules that I have installed apart from the Adyen module. I disabled the cache. I also copied the files from Thirty Bees over the top of my site in case any files had been corrupted. The problem remained. 

The last thing I tried, was replacing the database of the site that was causing problems with the one created by the clean install of Thirty Bees. There were no problems. 

I believe that the problem is with the database or some settings. Is there any way to check there all the database changes have been adopted correctly? I started development on TB 1.0.0 and it is now 1.0.7 so I believe that one of the updates could have affected something.

Any help would be greatly appreciated.

Kind regards,


Link to comment
Share on other sites

0 answers to this question

Recommended Posts

There have been no answers to this question yet

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...