View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004071||OXID eShop (all versions)||1. ----- eShop frontend -----||public||2012-05-22 14:06||2012-12-10 14:37|
|Status||resolved||Resolution||no change required|
|Product Version||4.6.0 revision 44406|
|Target Version||Fixed in Version|
|Summary||0004071: new code prevents displaying individual persparams in basket|
|Description||since in 4.6.0 was implemented following code into views/oxcmp_basket.php - the persparams-fields in basket are only shown if persparam "details" is present and has a value:|
$aPersParam = ( isset( $aProductInfo['persparam'] ) && is_array( $aProductInfo['persparam'] ) && strlen( $aProductInfo['persparam']['details'] ) )?$aProductInfo['persparam']:null;
no problem when using old code (as condition for "details" is not added):
$aPersParam = isset( $aProductInfo['persparam'] )?$aProductInfo['persparam']:null;
|Steps To Reproduce||add individual persparam - fields|
use some while ordering, but do not enter a value into the "details" - field
|Additional Information||is there any deeper reason for adding this condition?|
|Tags||No tags attached.|
There were fixes made for issues 0002867 and 0003907, also related with persparams.
After the fix for 0003907, there was this check for empty value, because there is no other way how to compare the same product with persparam, when product is added from different places in eShop (i.e. lists and details view).
In standard eShop source code there is one persparam implemented. In this case if you also have one,just renamed to other title - then just rename it also in the mentioned source code:
But if somebody has several persparams implemented in eShop - this is more custom change then and then you should take care about that part - override also the handling of these persparams with proper logic, how to compare the values in your case.