View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003323 | OXID eShop (all versions) | 1.03. Basket, checkout process | public | 2011-10-21 13:53 | 2012-04-13 11:33 |
| Reporter | saulius | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | won't fix | ||
| Product Version | 4.5.2 revision 38481 | ||||
| Fixed in Version | 4.6.0_RC1 | ||||
| Summary | 0003323: removeBtn button chekking | ||||
| Description | oxcmp_basket.php, _getItems() line 337 .. if (oxConfig::getParameter( 'removeBtn' ) !== null) { .. Consider button existence checking inappropriate as this prevents substitution with <a> element in the frontend and forces fake element creation with a required name. | ||||
| Steps To Reproduce | Try changing removeBtn button element to <a> element with js form submission. | ||||
| Tags | No tags attached. | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
|
|
I thin you want to achieve old functionality, when each item had to be removed separaly There was a discussion in dev-general mailing list: http://comments.gmane.org/gmane.comp.php.oxid.general/33 |
|
|
This button name and check is not without purpose, it is mandatory for html forms with several submit buttons, Otherwise shop can not determine if update or remove action was called. With javascript you can easily achieve similar functionality, bu you MUST pas parameter removeBtn=1 using dynamically added hidden field, appending it to form submit or any other way |
