View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006380 | OXID eShop (all versions) | 4. ------ eShop Core ------- | public | 2016-04-21 19:10 | 2016-04-22 12:12 |
| Reporter | leofonic | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 4.9.7 / 5.2.7 | ||||
| Summary | 0006380: incorrect date in oxinsert column in oxorderarticles | ||||
| Description | Bug 0005216 is marked resolved but the issue 1) is still present: 1) oxorder->execute calls oxorder::_setOrderArticles which calls oxOrderArticles::copyThis($oProduct) oxOrderArticles::copyThis appears to copy oxarticle__oxinsert to oxorderarticle_oxinsert, which it should not do. oxorderarticle_oxinsert should be current date | ||||
| Steps To Reproduce | - place an order - look at oxinsert in oxorderarticles, it is copied from article but should be set to order date instead. | ||||
| Tags | No tags attached. | ||||
| Theme | Not defined | ||||
| Browser | Not defined | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
|
|
if order is placed oxorderarticles__oxinsert and oxorderarticles_oxtimestamp are copied from oxarticle__oxinsert and oxarticles_oxtimestamp. The oxorder_oxorderdate is not set in db table oxorderarticles. The field oxorderarticles__oxinsert, you mentiond, shows the timestamp the article is inserted not when the order is placed. Therefore you have the field oxorder_oxorderdate. So its no bug and can be closed |
