[ic] mv_price and CommonAdjust

Ed LaFrance interchange-users@icdevgroup.org
Mon Oct 14 13:04:01 2002


At 11:47 AM 10/14/2002 +0100, you wrote:
>Dan Browning wrote:
>
>>At 03:59 PM 10/11/2002 +0100, you wrote:
>>
>>>Hi - I'm still trying to manually set the price of an item when 
>>>ordering. I've managed to set mv_price for that item to a new value and 
>>>have confirmed that the item has this new value for mv_price in the cart 
>>>by using [dump]. I am having problems getting it to display this new 
>>>price on the basket page. I'll be the first to admit that my 
>>>understanding of CommonAdjust is as vague as can be but i believe i need 
>>>to alter it in catalog.cfg to allow me to override the price with 
>>>mv_price? I've tried CommonAdjust $ in catalog.cfg but it makes no difference.
>>>
>>>I am quite over my head here - can anyone point me in the right direction?
>>>
>>>John
>>
>>
>>Make sure your after.cfg isn't overwriting your CommonAdjust.
>I have no etc/after.cfg. There only appears to be one CommonAdjust statement
>
>[root@linux1 hoi.new]# grep -r CommonAdjust *
>catalog.cfg:# CommonAdjust   "[hoipricesub]"
>catalog.cfg:CommonAdjust $
>catalog.cfg:# CommonAdjust   pricing:price_group,q5,q10: ;:wholesale ;$
>catalog.cfg:# This makes CommonAdjust effective, since no_price doesn't exist
>[root@linux1 hoi.new]
>
>I found a mail before in the archives where Mike Heins pretty much spelt 
>out how to do this but search as i might i have been unable to find it:(
>
>Reading the documentation, there seems to be something called 
>attribute-based adjustment:
>
>*"==attribute:table*:column*:key**
>
>      Does an attribute-based adjustment. The attribute is looked up in
>      the database *table*, with the optional *column* defaulting to the
>      same name as the /value/ of the *attribute*. If the column is not
>      left blank, the /key/ is set to the /value/ of the *attribute* if
>blank."
>
>Has anyone had any experience using this? Ideally what i want is that if 
>an attribute is set for an item, a database lookup is done and the price 
>is set to the value of a specific field for that item. Is there better way 
>to do this? I dont really understand how to use the above CommonAdjust 
>string to do what i want and i cant find an example in the documentation. 
>Could someone post one?
>
>I found the following in the documentation which is confusing me a lot:
>
>      "If the value of the CommonAdjust directive is set to a
>      CommonAdjust string, and the price field is empty or specifically
>/0/, then it will be used to set the price of the items."
>
>This seems to imply that if the price field is not empty and is not 
>speciffically 0 then the CommonAdjust string will not be used no matter 
>what... Am i misunderstanding?

That is correct - and specifically the price field is determined by the 
PriceField directive. When you want to use a CommonAdjust string, 
PriceField needs to NOT be pointing to a price field, i.e.

         PriceField no_price_field

...will enable CommonAdjust usage (assuming you do not have a price field 
named 'no_price_field')

- Ed L.


===============================================================
New Media E.M.S.              Technology Solutions for Business
463 Main St., Suite D         eCommerce | Consulting | Hosting
Placerville, CA  95667        edl@newmediaems.com
(530) 622-9421                http://www.newmediaems.com
(866) 519-4680 Toll-Free      (530) 622-9426 Fax
===============================================================