View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004844 | OXID eShop (all versions) | 1.01. Products (product, categories, manufacturer, promotions etc.) | public | 2013-01-11 15:20 | 2015-12-01 09:31 |
| Reporter | Linas Kukulskis | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Product Version | 4.7.2 / 5.0.2 revision 53018 | ||||
| Summary | 0004844: Missing article in list when used blUseTimeCheck | ||||
| Description | With the blUseTimeCheck option you can turn on the feature to specify a time frame (from/to) in which a product is active. When this option is on, shop act wrong in this situations: 1. Shop does not recalculate article count in /manufacturer/vendor list when product becomes active 2. Price from is calculated wrongly 3. Product with time-limited variants stays inactive Possible solutions: Use cron jobs to recalculate products with from/till dates related data. | ||||
| Steps To Reproduce | Case 1 ====== Steps to reproduce: - Imagine it is Monday - Create a category Foo with four active products in it (article count = 4) - Create product A in category Foo - Configure product A to become active from Tuesday to Thursday - Activate the configuration option "Show article count near category|manufacturer|..." - Wait until Tuesday and open listing view for category Foo What happens: - The product A appears in the category Foo's listing view - The article count is still 4, because it is cached What is expected: - The product A appears in the category Foo's listing view - The article count is 5, because product A became Active Additional Information: On Friday, product A becomes inactive again. Then, it should not show up in Foo's listing view anymore and article count should be 4 again. Case 2 ====== Steps to reproduce: - Imagine it is Monday - Create product A with variant Foo and Bar - Configure variant Foo to become active from Tuesday to Thursday, whereas Bar is always active - Set price for variant Foo to 0.99 EUR and for variant Bar to 2.99 EUR (s. th. Foo is cheaper than Bar) - Wait until Tuesday What happens: - Foo becomes active and has the lowest price (0.99 EUR) - "Price from" for product A still reads "2.99 EUR" (price of variant Bar) What is expected: - Foo becomes active and has the lowest price (0.99 EUR) - "Price from" for product A reads "0.99 EUR" (price of variant Foo instead of variant Bar) Additional Information: Sorting is also broken in this case. Note that on Friday, when variant Foo becomes inactive again, the "Price from" should be 2.99 EUR again. Case 3 ====== Steps to reproduce: - Image it is Monday - Create a product with one variant - Make sure the variant has a stock of 20 items - 10 items of this variant are on sale - 10 items of this variant will be activated from Thursday to Sunday - Buy 10 items of the variant on Tuesday (product sold out, becomes inactive) - Wait until Thursday What happens: - The product is not activated again, even though the second half of the stock (10 items) is active since Thursday What is expected: - The product becomes active again, as soon as the variant items become active on Thursday Additional information: If the product has more than one variant, then the variant which is time-boxed does not become active at the beginning of the time-box (depends on stock flag). | ||||
| Additional Information | If we use cron and remove subselect it can increase performance | ||||
| Tags | Cache, Category, Products, Stock | ||||
| Theme | All | ||||
| Browser | All | ||||
| PHP Version | Not defined | ||||
| Database Version | Not defined | ||||
