View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006012 | OXID eShop (all versions) | 5. ------ UpdateApp / Update ------ | public | 2015-01-08 14:16 | 2017-04-05 09:25 |
| Reporter | martinwegele | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.9.0 / 5.2.0 | ||||
| Summary | 0006012: utf-8 update app breaks theme and module settings | ||||
| Description | It seems that the utf-8 update script does not select/insert the field oxmodule from oxconfig (introduced in 4.5.0). Therefore your theme and module settings will not be displayed any more because the default value for oxmodule is an empty string like before (e.g. theme:azure). | ||||
| Steps To Reproduce | Install a shop e.g. 5.2.2 without using utf-8 mode (i.e. uncheck the option during setup). Check theme settings of the default Azure theme in the admin panel. Activate the PayPal module. Edit some settings of the PayPal module. Then use the utf8-update script as described here: https://www.oxid-esales.com/en/support-services/documentation-and-help/oxid-eshop/installation/oxid-eshop-update-installation/update-eshop-to-utf-8-encoding.html Now check the settings of the Azure theme and the PayPal module. They are not displayed in the admin panel any more but still available in the database: select oxvarname, oxmodule from oxconfig where oxvarname like '%oepaypal%'; | ||||
| Tags | UTF-8 | ||||
| Attached Files | |||||
| Theme | All | ||||
| Browser | All | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
Reproduced with most recent EE UTF8-updatescript (http://support.oxid-esales.com/downloads/utf-8/OXID_UTF8UPDATE_EE_5.2.0.zip). confirmed. |
|
|
I uploaded a fixed update.php script file for the 5.2.x EE Edition. This fixed the problem and I could see the Theme/Module settings after the script was executed. |
|
|
The new update.php mentioned in 0006012:0011939 was tested and it works! |
|
|
We changed the update script according the proposal and published it on the mentioned website. |
