View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001249 | OXID eShop (all versions) | 1.03. Basket, checkout process | public | 2009-08-26 21:43 | 2012-12-10 13:23 |
| Reporter | d3 | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 4.1.5 revision 21618 | ||||
| Fixed in Version | 4.2.0 revision 23610 | ||||
| Summary | 0001249: shippingtype not saved | ||||
| Description | if shippingtype "oxstandard" is deleted by shopowner, it can be happen that no ShipSet is saved to order. reproduce: - pls delete oxstandard and set one or two new shipsets. - make a new order and DONT CHANCE the shipset in step3 - the shipset dont will displeyed in step4 and dont saved to order The problem is the changes in oxbasket::getShippingSet(). If any customer started a new session, the shipset will be set to "oxstandard". If the customer dont changed the shipset in step3, there are no method in "order" or "payment" that saved the actual selected shipset in basket. The result ist a still seted shipset "oxstandard" in step4 and it set to order, but failed in oxdeliveryset. Only payment::changeshipping() do this if the customer changed to other shipset one in step3. | ||||
| Tags | Order | ||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | 5.2.6 | ||||
| Database Version | 5.0.33 | ||||
| related to | 0001224 | resolved | birute_meilutyte | module PayPal | paypal express checkout redirects to order step3 instead of step4 if user was not logged in |
| has duplicate | 0001527 | resolved | dainius.bigelis | OXID eShop (all versions) | Empty deliveryset at step 4 and in admin |
| related to | 0001593 | resolved | alfonsas_cirtautas | OXID eShop (all versions) | Shipping set information is cached in basket object and not updated corectly |
|
|
I mean Ident 'oxidstandard' |
|
|
can't reproduce it localy. but looks like its the same problem, as described in 0001224 |
|
|
No, its not the same problem. We can reproduce this in two different shops and also in http://demoshop.oxid-esales.com/professional-edition/ !! The base is to delete the existing deliveryset "oxidstandard". What you doing to test this? |
|
|
Reminder sent to: d3 Hello, the way I was testing: 1) setup PE shop with standard demodata 2) created new delivery rule (available for all countries) 3) deleted standard delivery set 4) created new delivery set with sorting 0 (this is default), available for all countries, with all payments. assigned created delivery rule to it 5) deleted cookies and tmp 6) in frontend: login as admin and made an order. in step 3 newly created delivery set was offered (skonto payment was selected as default one). changed nothing and clicked next. delivery was correctly displayed in order step 4 and saved to order. this scenario also worked on online demoshop. information was saved correctly. Also tried same testcase, when order is done with oxstandard delivery set, and only then this set was deleted and new one setupped. in next order for same user newly created delivery set was offered and saved correctly. could you please let us know, how you setupped new delivery set? maybe the case is in some of delivery set options. greetings, Birute M. |
|
|
Reminder sent to: d3 Hi, Could you please take a look to the comments of the bug entry: https://bugs.oxid-esales.com/view.php?id=1249 and let us know what we are doing wrong to reproduce this case? Best regards, |
|
|
@Developers: please check from the source code side, if this behavior is possible and not existing shipping set is selected by default. |
|
|
fixed |
