View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002130 | OXID eShop (all versions) | 5. ------ UpdateApp / Update ------ | public | 2010-09-24 10:26 | 2010-10-11 17:23 |
| Reporter | cpjolly | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 4.2.0 revision 23610 | ||||
| Summary | 0002130: upgrade 4.2.0 to 4.4.2 sConfigKey / DECODE error | ||||
| Description | When doing an upgrade of a shop from CE 4.2.0 to CE 4.4.2, using the cumulative upgrade, the core/oxconfigk.php file version moves from 16303/2009-02-05 to 25467/2010-02-01 and the value of sConfigKey is changed. But as far as I can tell there is no SQL code run to re-encode the data. After the upgrade, the SQL DECODE in the function _loadvarsFromDb, line 464, of core/oxconfig.php no longer works, because the data is encoded with the old key. Manually changing the key to the old value in core/oxconfigk.php seems to fix the problem. The result is that no articles are displayed in the shop and no setup data is displayed in admin. | ||||
| Steps To Reproduce | Take a standard 4.2.0 CE demo installation, check the version number of oxconfigk.php and sConfigKey value. Attempt to upgrade to 4.4.2, check the version number and key again. See if the shop still displays articles and if the admin displays the setup data | ||||
| Tags | No tags attached. | ||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
|
|
(typo in bug report - the filename is core/oxconfk.php not core/oxconfigk.php) |
|
|
Reminder sent to: cpjolly Hi, We cannot reproduce such case. I checked the sConfigKey value in few places (4.2.0 version installation package, 4.4.2 installation package, and the Cumulative Update package for 4.2.0=>4.4.2) - everywhere the value is the same: $this->sConfigKey = "fq45QS09_fqyx09239QQ"; (thought the file version is really different, but it's due to deployer tricks). And after upgrade - for us everything works fine, having in mind, that after Update you always _need_ to clean the tmp dir. Please check once again the value of sConfigKey in eShop 4.2.0 installation package and the Cumulative package - is it really different?... And make sure that after Update you cleaned tmp dir. Best regards, |
|
|
Thanks Dainius, I checked again and the original value of the key in core/oxconfk.php was as follows: $this->sConfigKey = "Jh3T6945_hbNGdd64N75"; I was not the original developer on this shop, so perhaps a previous upgrade was not done properly, and this key value has been incorrect for a while. I think we can consider this bug to be close. Regards, Chris Jolly |
|
|
Reminder sent to: cpjolly Hi, Thank you for your feedback. The case is closed. Best regards, |
