View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006069 | OXID ERP Interface | OXID ERP Interface - sub | public | 2015-03-04 10:51 | 2024-01-17 14:28 |
| Reporter | winkelmann | Assigned To | |||
| Priority | low | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Product Version | 2.14.0 | ||||
| Summary | 0006069: Language implementation is inconsistent | ||||
| Description | The language implementation is inconsistent. For categories it all works fine with languages. If I have more than the standard languages (0, 1, 2, 3) I just need to add the new fields for ID 4 and upwards. Same for mostly all other tables (like manufacturers, vendors, ..). The problem is articles. There was this bug with too many joins, because the query used the "all view" from oxarticles, oxartextends and oxfield2shop. OXID made a bugfix (link in additional information) which replaced the views from oxartextends and oxfield2shop with the core table. Problem now is, every language beyond ID 3 will not work, even I add the table fields for the other languages. The query fails with the error message that specific columns are missing in the field list. It would be nice to get some kind of working solution which corrects this inconsistency: For articles it should work like for categories, etc and give all translations. | ||||
| Steps To Reproduce | Call the OXERPGetArticle for a specific article in a shop which has more than one set table. | ||||
| Additional Information | The bugfix mentioned in the description: https://bugs.oxid-esales.com/view.php?id=5875 | ||||
| Tags | Product domain and basket rewrite | ||||
|
|
Shop version: EE 5.1.7 Protocol: 2.14 Steps to reproduce: Call the OXERPGetArticle for a specific article in a shop which has more than one set table. And there was a bug, you can read about that in the comments. I am quoting the comment: "We are thinking that this bug was fixed with bug 0005875. The fix is added from ERP version 2.14.0. You can add this fix and this problem would be solved." |
|
|
If I understand it correctly this issue only occurs if there are more than iLangPerTable (default 8) languages in a shop. |
