Re: Miva Merchant 5.5 Dream Features
I have two requests for the basket. I do a lot of customizing of the Basket for clients and the same type of problems comes up over and over.
I'd like the basketitems database to have two more fields.
1. category_code.
If g.Category_code was passed in the form when add to basket is clicked, just store it. Then the link back to the product page can be coded with the category code. Also Continue Shopping buttons would be easier to code.
2. user_data -- 255 characters or more.
This fields only purpose it to allow additional data to be stored with each line item by scripts and by third party modules. It happens often that I need to track additional basket data for incomming links, third parties, special products, special handling, calculation results etc. Sometimes I can hide the data using <!-- --> in the name field. If the data is too long, I have had to resort other more convoluted methods like stuffing the data into an attribute, then hidding the attibute from display and keeping it out of the emails.
It seems to me other modules and processes would ignore these fields so they should have no impact on the way Merchant works.
I have two requests for the basket. I do a lot of customizing of the Basket for clients and the same type of problems comes up over and over.
I'd like the basketitems database to have two more fields.
1. category_code.
If g.Category_code was passed in the form when add to basket is clicked, just store it. Then the link back to the product page can be coded with the category code. Also Continue Shopping buttons would be easier to code.
2. user_data -- 255 characters or more.
This fields only purpose it to allow additional data to be stored with each line item by scripts and by third party modules. It happens often that I need to track additional basket data for incomming links, third parties, special products, special handling, calculation results etc. Sometimes I can hide the data using <!-- --> in the name field. If the data is too long, I have had to resort other more convoluted methods like stuffing the data into an attribute, then hidding the attibute from display and keeping it out of the emails.
It seems to me other modules and processes would ignore these fields so they should have no impact on the way Merchant works.
Comment