View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001799 | OXID eShop (all versions) | 1.01. Products (product, categories, manufacturer, promotions etc.) | public | 2010-04-28 22:58 | 2012-12-07 14:20 |
| Reporter | Firefax | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 4.3.0 revision 26948 | ||||
| Summary | 0001799: The Just Arrived articles are calculated wrong in the Update -Version of 4.3.0 | ||||
| Description | When you have activated the feature "Just Arrived" with the automatic calculation, every sold item is counted as a just arrived item. This means, that every sold item is the one which just arrived. This behavior is not the intended one. The problem is that only the Update Version of the shop is affected, not a fresh installation. The update was done correctly and according to the manual. | ||||
| Additional Information | Maybe a developer can give us a hint, in which file the calculation of the Just arrived items happens, so we can try to find any differences by ourself. | ||||
| Tags | Promotion | ||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
| related to | 0001618 | resolved | vilma_liorensaityte | Category quick sorting by "last changes" |
|
|
This issue occurred because solution for bug 0001618 was implemented and since then the timestamp of products is updated when product is sold. Because this issue (Just Arrived) - the solution for updating timestamps or selecting products as "Just Arrived" should be changed. We are considering about new solution. |
|
|
Today, we have waited for over a month, the version 4.3.2 was announced today, we have already seen 2 Patches for the 4.3.x but with this bug, there is no improvement. Is there any progress for this bug ? The latest demoshop 4.3.2 still has this bug. |
|
|
Reminder sent to: Firefax Hello, you can find option "Calculate newest Products by Date of Creation (otherwise by Date of last Change)" in Core settings -> Settings (tab) -> Products (selection) It is recommended to use date of creation for newest products (oxinsert db field). Please, check this option in your shop configuration, it should solve your problems with newest products. previously in 0001618 was fixed problem, when product date of last change (oxtimestamp db field) was not always updated correctly (oxtimestamp should allways be updated, when something changes in product information. in this case, stock change after product was bought should also affect oxtimestamp). greetings, |
|
|
Hello Birute, I know the options in the admin and i like to have an automated calculation according to the last significant change for my "Just arrived" Items at the starting page of my shop. I don't feel comfortable with the product date of creation. I think the Feature you implemented instead of solving the Bug 1618 (timestamp was set to 00000) should be called "Last Sold Item" and not "Just arrived". The second "bug" in 1618 was a changing of features, see below: First of all we should define what "just arrived" really should do: a) newest Products by Date of Creation (that we have already seperate) b) Date of last significent changes (changes done unter products -> main | I think this was the behaviour for version 4.1.6 and below) c) Date of any changes, as it is right now in 4.3.x, every sold item creates a change of the product. (That could be called and used as "Last sold item") d) Date of last stock increase. I think, this option would match best for the "Just arrived" title. |
|
|
Hi Birute, trying to explain it again :-) How to reproduce: 1. Go to front end, start page and keep the "just arrived" products in mind :-) 2. In admin, go to Core Settings -> Perform. and switch the List of newest Products to "automatic". 3. Go to front end, buy the Bush Beach Radio and proceed the checkout. 4. Go to start page again and have a look at the "just arrived" products. BUSH Beach Radio appears here. The list of newest products (just arrived), set to automatic, shall only be altered by querying OXINSERT instead of OXTIMESTAMP. |
|
|
There is an option: "Calculate newest Products by Date of Creation (otherwise by Date of last Change)" that would do the job. No change needed IMO. |
|
|
At least i realise now, what the consequences of the bug 1618 are. Every (also every stock change) causes the oxtimestamp to get a new time and the timestamp is the base for the last changed product. With the changes of the bug 1618 my focus came to this topic. Now i know that the implementation for the "Fresh arrived" Feature was already suboptimal before the changes. The next thing I realised is, that there is no real working feature "Just arrived" in the Oxid shop. The date of creation gives me the list when I have listed the items / added the items to my catalog, that is not what i want. Right now, the newest product according to the oxtimestamp is the last sold item in a regular working shop. I think i can get used to the "Last sold" List, its dynamic and always changing. So there is no need to change anything for me right now. You can close this bug when you rename this feature to "Just Listed Items" and "Last sold items". Then you should also make a new feature request for the "just arrived" Feature, a list where the items are sorted according to the last increase in stocks / with the latest incoming goods. I hope that cleariefys the problem. |
|
|
Ok, after thinking a while about this here, I started to like the "Last Sold" Feature you implemented by solving bug 1618. Please do not modify this feature any more (you may just rename it). You may open a new feature request for a real "Just arrived" - Feature. This bug can be closed! |
|
|
Feature request to improve logic in "Just arrived" list is inserted here: http://oxid.uservoice.com/forums/31940-feature-requests/suggestions/817305 |
