View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001162 | OXID eShop (all versions) | 1.03. Basket, checkout process | public | 2009-08-03 16:24 | 2012-12-10 13:24 |
| Reporter | d3 | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | duplicate | ||
| Product Version | 4.1.3 revision 19918 | ||||
| Summary | 0001162: Problem with copy-Fields in oxarticles and oxorderartiles | ||||
| Description | For some modules we use the copythis() functionality for oxorderarticles. All fields in oxorderarticles with the same name as in oxarticles get the data from the article (oxtitle, oxartnum etc.) The same thing works in oxid version 3 fine with new own fields like "foobar". The shop copied the data in foobar from oxarticles to oxorderarticles. But now this procedure failed if the field "foobar" is not used during the order process. We think the shop "dont know" new fields because of lacy loading. | ||||
| Additional Information | you can test this very easy: Insert a new field in oxarticles and oxorderarticles with the same name like "foobar". Input some data in oxarticles in a testarticle. Buy this article. The shop should copied the data to oxorderarticles. But it failed. Now let display the field maybe in order.tpl as [{ ...->oxarticles__foobar->value}] After another order the field is filled in oxorderarticles. Because now the shop "knows" the field. But in some cases any fields we dont need to display in order process and the copy failed. | ||||
| Tags | Order | ||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | 5.2.6 | ||||
| Database Version | 5.0.33 | ||||
| duplicate of | 0000979 | resolved | vilma_liorensaityte | Some fields are not set in oxorderarticles table |
| related to | 0000773 | resolved | vilma_liorensaityte | Do not use article lazy loading on order save |
