1.5 DB Schema

[cmaloux]

I upgraded automatically from 1.5.4.0 to 1.5.4.1 without any problem but I get some error message that I have some missing fields in the DB: id_lang is missing in ps_customer

 

Is there a tool to verify the schema of the DB somewhere (I have PhpMyAdmin)? I have the feeling I am using a DB from a version 1.4 which was badly updated maybe?

 

 

Server information

 

Server information: Linux #1 SMP Tue May 11 19:21:39 MSD 2010 i686

Server software version: Apache/2.2.8 (CentOS)

PHP version: 5.2.10

Memory limit: 128M

Max execution time: 3000

Database information

 

MySQL version: 5.0.84

MySQL engine: InnoDB

Tables prefix: ps_

Store information

 

PrestaShop version: 1.5.4.1

Shop URL: http://decolab.cz/

Current theme in use: elation-liquid

Edited May 16, 2013 by cmaloux (see edit history)

[Trip]

Id_lang was added in 1.5.4. already

https://github.com/PrestaShop/PrestaShop/blob/master/install-dev/upgrade/sql/1.5.4.0.sql

All SQL upgrades are here https://github.com/PrestaShop/PrestaShop/tree/master/install-dev/upgrade/sql

Make a copy of your website on local computer and try to run the sql files manualle or try another autoupgrade.

But do that all on a test installation and when you do it after that on the live server make a backup of everything before.

Sorry I can not get to much into detail here. Just 2 more advices. Turn SEO Urls on and some of your slides on the frontpage are linked to the prestashop website... maybe not to cool.

Good luck, trip

[cmaloux]

Thanks for the pointers Trip!

 

I now know what happened. A backup from a 1.5.3.1 database was restored onto a brand new 1.5.4.0 installation (on another host) and then it was auto-upgraded to 1.5.4.1

 

So my 1.5.4.1 is running on top of a database for 1.5.3.1 hence the missing fields.

 

so I should use this SQL?

https://github.com/P...sql/1.5.4.0.sql

 

and then:

https://github.com/P...sql/1.5.4.1.sql

 

Is that what you would do?

 

 

I know about the slides and the seo thanks. Still in 'dev' mode :-)

Edited May 16, 2013 by cmaloux (see edit history)

[Trip]

I can not guaranty if this works but assuming you have enough backups so you can revert in the worst case than it can be an option.

I just don't take the responsibility .

Good luck, trip

[vekia]

hey

 

awesome, thanks trip for urls i will test it too because im really interested in this topic.

 

@cmaloux, let us know if it works for you

[Trip]

@Vekia,

the problem with that approach is that only upgrading sql in some cases might not be enough.

The updater includes sometimes php code which changes values in the db too.

https://github.com/PrestaShop/PrestaShop/tree/master/install-dev/upgrade/php

That's why I said, no guaranty and backups and so on. I think it might be better to change the version number back to

 define('_PS_VERSION_', '1.5.4.last_working_version'); 

in settings.inc.php and run the updater (maybe even better the manual upgrade) again.

But as I did not test that I can only guess that this works and depending on the experience it is complicated at least for people that have little to no knowledge what they are doing - ok, I don't have to tell you that .

That's why I sometimes don't have a good feeling about that and only can hope enough backups are in place

All the best, trip

[cmaloux]

I tried to trick it to think it was 1.5.3.1 by changing define('_PS_VERSION_', '1.5.4.last_working_version'); but the 1-click upgrade gave me:

 

upload/index.php added to archive. 2 left.

webservice/dispatcher.php added to archive. 1 left.

webservice/index.php added to archive. 0 left.

all files have been added to archive.

No valid tables were found to backup. Backup cancelled.

 

I'm going to have a look at the manual process and if that doesn't work either I will try to upgrade just the SQL but I totally see Trip point, I think this is not a good idea if some values are added in the upgrade process. Oh happy times :-)

 

UPDATE: The manual upgrade worked partially so I did a SQL upgrade and now all seems to work perfectly. All the missing fields are here.

 

Problems solved:

- Customer could not create account

- Cart was always empty

 

 

Thanks Trip!

Edited May 17, 2013 by cmaloux (see edit history)