View Issue Details

IDProjectCategoryView StatusLast Update
0003323OXID eShop (all versions)1.03. Basket, checkout processpublic2012-04-13 11:33
Reportersaulius Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status resolvedResolutionwon't fix 
Product Version4.5.2 revision 38481 
Fixed in Version4.6.0_RC1 
Summary0003323: removeBtn button chekking
Descriptionoxcmp_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 ReproduceTry changing removeBtn button element to <a> element with js form submission.
TagsNo tags attached.
ThemeBoth
BrowserAll
PHP Versionany
Database Versionany

Activities

alfonsas_cirtautas

2012-04-13 11:25

reporter   ~0006273

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

alfonsas_cirtautas

2012-04-13 11:33

reporter   ~0006274

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