View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004902 | OXID eShop (all versions) | 2.4. Administer products | public | 2013-02-05 22:47 | 2013-06-11 10:50 |
| Reporter | leofonic | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.7.3 / 5.0.3 revision 54408 | ||||
| Target Version | 4.7.5 / 5.0.5 | Fixed in Version | 4.7.6 / 5.0.6 | ||
| Summary | 0004902: updateUpcomingPrices sets wrong varmin prices | ||||
| Description | oxarticle::_setVarMinMaxPrice was changed in 0004701. But periodically once a day oxarticlelist::updateUpcomingPrices is called, which calculates minmax prices wrong, not taking into account oxactive and prices inherited from parent. A better way would be to fetch all articles that need updating, and update them with oxarticle object one by one, so onChange gets executed. btw "once a day" means that a product can appear in the shop a whole day with the wrong price. "Once an hour" would be more appropriate. | ||||
| Tags | No tags attached. | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
| has duplicate | 0004990 | resolved | Linas Kukulskis | updateUpcomingPrices calculates wrong varminprice values |
|
|
added activity check etc |
|
|
If this is supposed to be fixed in latest git dev repo, it is not fully resolved. If price of father is 5, first variant is 7, second variant is 0, price shown at parent is "from 5", which is correct. After oxmaintenance is executed, price shown at parent is "7". |
|
|
changed sql code to direct article call |
