View Issue Details

IDProjectCategoryView StatusLast Update
0003474OXID eShop (all versions)5. ------ UpdateApp / Update ------public2013-03-01 17:33
Reporterray Assigned To 
PriorityhighSeveritycrashReproducibilityalways
Status resolvedResolutionunable to reproduce 
Product Version4.5.5 revision 40299 
Summary0003474: missing lines in cumulative-pack SQL
Descriptionpls. check here:

http://www.oxid-esales.com/forum/showthread.php?t=12722&page=2#post77752

There are two lines missing in the update-sql from 4.4.8 to 4.5.5 which lead to a major crash.
Those lines are include in the 4.4.8 to 4.5.0 cumulative pack.
TagsNo tags attached.
ThemeBoth
BrowserAll
PHP Versionany
Database Versionany

Activities

dainius.bigelis

2012-01-03 10:02

reporter   ~0005576

Reminder sent to: ray

Hi,

Those SQL lines were not lost, just moved from .sql file to the .php file, because it needed more handling. So those changes still should be executed during update. Do you checked the DB after update and there are those changes missing in the DB?

Regards,

ray

2012-01-03 11:12

reporter   ~0005577

The problem is, that after an update from 4.4.7 to 4.4.8 (which was successfull) this error occured while updating from 4.4.8 to 4.5.5:

Errors in SQL: INSERT INTO `oxconfig` (`OXID`, `OXSHOPID`, `OXMODULE`, `OXVARNAME`, `OXVARTYPE`, `OXVARVALUE`) SELECT md5( concat( RAND(), 'blLoadFullTree', oxshops.oxid, oxshops.oxurl )), oxshops.oxid, 'theme:basic', 'blLoadFullTree', 'bool', '' FROM oxshops, check this SQL script, fix it and run it manually. After this proceed updateApp by clicking "Continue" button.

http://www.oxid-esales.com/forum/showthread.php?t=12722#post77507

ray

2012-02-21 14:27

reporter   ~0005785

still same problem in patch 4.4.8 to 4.5.7

http://www.oxid-esales.com/forum/showthread.php?p=82234

ray

2012-04-17 00:02

reporter   ~0006305

same problem in patch from 4.4.8 to 4.5.9

http://www.oxid-esales.com/forum/showthread.php?p=87036#top

dainius.bigelis

2012-04-23 20:46

reporter   ~0006408

Reminder sent to: ray

Hi,

Tried once again, the updates on CE from 4.4.7->4.4.8, then 4.4.8-> 4.5.5, but still - for me went well, no errors displayed.
Also tried update in both cases, when this field "blLoadFullTree" is set to ON and OFF before update, in 4.4.7 version. Still worked fine.
Do you have any idea on what more conditions this error may occur? Could you please send us the line from your DB table oxconfig, where this option is set "blLoadFullTree"?
Also - what eShop edition you are using - CE/EE/PE?

dainius.bigelis

2012-04-23 20:52

reporter   ~0006409

Reminder sent to: ray

Btw, could you describe what you select when you do the update itself? there are two questions in update to 4.5.0 (one asks about moving template structure, and removing deprecated variables), other questions also occurs in update to 4.5.1, when it asks for replacing images.
Do you choose Yes or No in these questions?

ray

2012-04-24 08:06

reporter   ~0006411

have asked the users with those problem in forums for more details

By the way, it seems to be no good idea to move changes in database to php-part, as sometimes the update is made differently. In certain cases it makes sense to set up a vanilla installation of the new version, dump your old version database and insert it in your new installation, then execute the update-SQL - but the field 'oxmodule' will not be inserted then.

dainius.bigelis

2012-06-05 10:53

reporter   ~0006767

In this case they also should run the PHP update part, not only the SQL. It will work on the new vanilla installation, and will do the job, what's needed for changes on the DB. And sometimes we cannot do changes only using SQLs, as we need to perform update on all possible variations, like different subshops, themes per shops, etc. So this part is shifted to PHP for proper handling.

dainius.bigelis

2012-06-05 10:54

reporter   ~0006768

The entry is closed as we got no more feedback about erroneous situations during update. Most probably that cases occured after the updates, when only the SQL part was executed, but not the PHP. So for now the case is closed.