Empty cart in 2.0 and 1.35sp4

I’m hoping that my experience will help someone else by saving them a bunch of time!



I loaded 2.0 and went to process an order. But whenever I add anything to the cart, it displays correctly in the cart widget at the top of the screen but as soon as I go to view cart or checkout, the cart comes up empty.



I was having the same problem under 1.35.



What I learned.

  1. the AJAX add to cart button is broken in 2.0. Okay, progress can certainly be made without AJAX!
  2. Turning off AJAX add to cart did no good. But… I learned…(ta-da, see #3)
  3. You cannot run both 1.35 and 2.0 within the same browser (different tabs). There seems to be differences in the session cookies (should really be fixed, especially for developers) that causes the anonymous user to come out with an $auth[‘user_id’] of zero…



    So when I moved my 1.35 work to IE and left 2.0 in FF, all was well. I “believe” (but not certain) that a ^n (new) browser under FF will retain the session id of it’s parent.



    Hope this saves someone else a bunch of time…

[quote name=‘tbirnseth’]I’m hoping that my experience will help someone else by saving them a bunch of time!



I loaded 2.0 and went to process an order. But whenever I add anything to the cart, it displays correctly in the cart widget at the top of the screen but as soon as I go to view cart or checkout, the cart comes up empty.



I was having the same problem under 1.35.



What I learned.

  1. the AJAX add to cart button is broken in 2.0. Okay, progress can certainly be made without AJAX!
  2. Turning off AJAX add to cart did no good. But… I learned…(ta-da, see #3)
  3. You cannot run both 1.35 and 2.0 within the same browser (different tabs). There seems to be differences in the session cookies (should really be fixed, especially for developers) that causes the anonymous user to come out with an $auth[‘user_id’] of zero…



    So when I moved my 1.35 work to IE and left 2.0 in FF, all was well. I “believe” (but not certain) that a ^n (new) browser under FF will retain the session id of it’s parent.



    Hope this saves someone else a bunch of time…[/QUOTE]



    Tbirnseth,



    This error occurs when using Mysql type equal to 41.

    You can find more information about this problem and its solution here:



    [URL=“http://forum.cs-cart.com/showthread.php?t=9275”]http://forum.cs-cart.com/showthread.php?t=9275[/URL]



    Thank you.

this is caused by the cookie handle

[quote name=‘isergi’]Tbirnseth,



This error occurs when using Mysql type equal to 41.

You can find more information about this problem and its solution here:



[URL=“http://forum.cs-cart.com/showthread.php?t=9275”]http://forum.cs-cart.com/showthread.php?t=9275[/URL]



Thank you.[/QUOTE]



My config file is already defined as $db_type = ‘mysql’.

[quote name=‘ThomH’]this is caused by the cookie handle[/QUOTE]



That’s what I ultimately came to. This is not good. What about a customer who happens to be shopping at 2 cs-cart stores. One 1.35 and one 2.0. They will not be able to check-out.



My guess is that the same tag is being used in the cookie with different values between the two versions. Would strongly suggest that the tags be unique if their definition changes from version to version.

[quote name=‘tbirnseth’]My config file is already defined as $db_type = ‘mysql’.[/QUOTE]



My error… my 1.35 config.php had ‘mysql’ and my 2.0 config.php had ‘mysql41’ Changing this to ‘mysql’ in 2.0 enables the AJAX add to cart button to work.



Unfortunately, each click adds 2 items to the cart!

has nothing with mysql, wrong way!

“My guess is that the same tag is being used in the cookie with different values between the two versions.” exactly



There are somme problems with scripts too,

if you are using a popup blocker the buttons are not working or not properly.

(this happens in 1.3.4 versions)

v2.0 is beta, I mean will be fixed in final version.