View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007169 | OXID eShop (all versions) | 2.1. Master Settings | public | 2020-08-24 11:49 | 2020-08-25 07:03 |
| Reporter | kaistrecker | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Summary | 0007169: The backend is broken after creating language "en". | ||||
| Description | The problem is application/controllers/admin/oxadminview.php->_getCountryByCode. This function loads the view "oxv_oxcountry_en" as soon as there is a language with "en" as "Abbreviation". This breaks the backend, because we have to manually create the view after creating the language, but we can't do this, because the backend is broken. I think there are three solutions for this bug: 1. Automatically create views after creating a new language. 2. Change oxadminview->_getCountryByCode, so it will check if "oxv_oxcountry_en" exists, before loading data from it. 3. Wrap the code in oxadminview->_getCountryByCode in a try-catch. | ||||
| Steps To Reproduce | 1. Go to "Master settings" > "Languages". 2. Create a language that has "en" as "Abbreviation". => The backend is broken, because it tries to access the view "oxv_oxcountry_en", which does not exist yet. | ||||
| Tags | No tags attached. | ||||
| Theme | Not defined | ||||
| Browser | Not defined | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
Dear kaistrecker, i cannot reproduce this behavoir in the actual version of the Shop (6.2.2). Could you please verify your version? Nevertheless i would also recommend you to check if some modules changed your backend so some functions are called. And those function trigger your error. Best regards QA - SG - |
|
|
Hi, thanks for the fast reply. I had this problem in a shop with the version 4.10.8. Also no module changed this part of the backend. So this is a OXID core bug. I also tested this in one of our 6.2.2 shops. I had no problems there. So this bug does not exist in 6.2.2 anymore. Best regards, Kai Strecker |
|
|
Dear Kai Strecker, thank you for your feedback. I closed the bug-report. Best regards, QA - SG - |
