View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005906 | OXID eShop (all versions) | 2.8. Service | public | 2014-10-05 14:22 | 2022-02-01 14:42 |
| Reporter | gerldental | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Product Version | 4.8.7 / 5.1.7 | ||||
| Summary | 0005906: Pricealarm list: - column Name is empty ( pricealarm_list.tpl ) | ||||
| Description | There seems to be a problem with missing DB-fields. for example ( Line 107, pricealarm_list.tpl ) <td valign="top" class="[{$listclass}]" height="15"><div class="listitemfloating">Javascript:top.oxid.admin.editThis('[{ $listitem->oxpricealarm__oxid->value}]');</div></td> $listitem->oxpricealarm__userlname->value and $listitem->oxpricealarm__userfname->value doesn't exists in the oxpricealarm table! | ||||
| Additional Information | unfortunarly, there is no possibility to save a name if user is not logged in. | ||||
| Tags | Documentation, Price Alert | ||||
| Theme | Azure | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
|
|
Reminder sent to: gerldental Hi, This is not a bug, because if user is not logged in to the shop, then how shop could know the user name, because for price alarm you are enter only email. If user is login then the Name field is no empty because user is identifying by OXUSERID If you are talking about other case as: Test case: 1. Register to the shop use email for registration e.g. [email protected], 2. Go to the product-> price alarm (enter email [email protected] and fill other fields) and click on the button SEND 3. Go to DB and open TABLE oxpricealarm 4. OXUSERID is saved --> CORRECT 5. Log out from shop 6. Open the detail page of the product (1402) then open tab Pricealarm and fill all fields. As you using the same email [email protected] for pricealarm , then in the table oxpricealarm is not added entry to the field OXUSERID. --> And then if we are assuming that it is not correct then it is as more feature request Best regards, Jurate |
|
|
ok, that's more feature request. just my expirience: from about 60 price alerts, nobody (!) was logged in. People are going to login in 99% cases only to make an order. Thanks! |
|
|
Waiting for PO decision. |
|
|
We will update the documentation to reflect the current status of the implementation and the correct usage of this feature |
