Have just implemented GBradley's MiniCart javascript on our site, and in the process noticed something... s'not a biggie, but a fix would be useful.
As some are aware, our store resides on http://store.over-clock.com, and cgi scripts reside on http://www.over-clock.com/cgi-bin
http://store.over-clock.com = http://www.over-clock.com/acatalog/
Now, when you add an item to your cart, the cart summary is displayed fine showing however many items and their value in the cart. BUT, once the cart has then forwarded the user back to the http://store.over-clock.com/ based URL to continue shopping, the cookie path becomes invalid... and the cart summary reverts back to showing 0 items and 0 value (and thus so does the MiniCart script).
AKA - the "usual" problem that folks have when they have a mix of http://domain.com and http://www.domain.com in network settings, however, in my case, this setup is entirely intentional and somewhat necessary... our store has resided at http://store.over-clock.com for years, and to change it now would cause complications for us.
So... how does one set the actinic cookie to be a domain-wide cookie assigned to .over-clock.com (& thus including ALL subdomains - both www. & store.) rather than allowing it to default (to www.over-clock.com)?
As standard in actiniccore.js, the domain field isn't used, so it defaults to the path of the cgi script that set it... thus www.over-clock.com
Have tried appending as follows in actiniccore.js...
But nada.
I recall going thru all this YEARS ago with Actinic v4 for a client rather than ourselves, and someone at Actinic (John someone-or-other - doesn't work there anymore) sorted it out for me, and it was a farily minor change...
As some are aware, our store resides on http://store.over-clock.com, and cgi scripts reside on http://www.over-clock.com/cgi-bin
http://store.over-clock.com = http://www.over-clock.com/acatalog/
Now, when you add an item to your cart, the cart summary is displayed fine showing however many items and their value in the cart. BUT, once the cart has then forwarded the user back to the http://store.over-clock.com/ based URL to continue shopping, the cookie path becomes invalid... and the cart summary reverts back to showing 0 items and 0 value (and thus so does the MiniCart script).
AKA - the "usual" problem that folks have when they have a mix of http://domain.com and http://www.domain.com in network settings, however, in my case, this setup is entirely intentional and somewhat necessary... our store has resided at http://store.over-clock.com for years, and to change it now would cause complications for us.
So... how does one set the actinic cookie to be a domain-wide cookie assigned to .over-clock.com (& thus including ALL subdomains - both www. & store.) rather than allowing it to default (to www.over-clock.com)?
As standard in actiniccore.js, the domain field isn't used, so it defaults to the path of the cgi script that set it... thus www.over-clock.com
Have tried appending as follows in actiniccore.js...
Code:
Function setCookie(sName, sValue, sExpire)
{
var sCookie = sName + "=" + escape(sValue) +"; path=/"; domain=".over-clock.com";
I recall going thru all this YEARS ago with Actinic v4 for a client rather than ourselves, and someone at Actinic (John someone-or-other - doesn't work there anymore) sorted it out for me, and it was a farily minor change...
Comment