Cookie Corruption

[Gerald Lee]

Actinic drives our website www.queenshill.com which supplies tailor-made curtains. The user can calculate a price for curtains with various size and finish options then add it to the shopping basket. It uses a default product called 'curtain' with a price of £1 and uses quantity to achive the correct amount (e.g. a curtain for £350 would go the basket as 350 £1 curtains).
The calculator uses cookies to store information. Unfortunately the cookies used by Actinic seem to conflict with those of the calculator and vice versa. So for example if the calculator writes a cookie it empties the shopping basket.
Does anyone have any suggestions? I would ideally like the cookies for the calculator and Actinic to be stored in seperate cookie files.

Thanks
Gerald

[Guest]

Hi Gerald,

I tried adding a curtain to the shopping cart, the value is carried to the basket correctly. Am I on the right track here?

[Duncan Rounding]

I don't know the answer but I do see what you mean. I chose a material for curtains then calculated the requirements and added to cart. I then chose another material for curtains and calculated these requirements - when adding to cart the cart cleared.

Hopefully Sumiya can take it further with this example.

[Guest]

Hi Gerald,

Can you let me know how the calculator is implemented on the site and send the code offline to sfsupport@actinic.co.uk

[NormanRouxel]

If whoever wrote the cookie code used the same name for that cookie as Actinic does for it's customer or cart data, that's what you'd get.

A quick and dirty way to examine the cookie is to put the following into the Description field of a dummy product.

!!<<script type="text/javascript">
document.write(unescape(document.cookie.replace(/;/g,'<p>')));
</script>>!!

Put that in a product and it'll be possible to diagnose what's happening.