Delete your browser cookies to resolve the most common cause of this problem. Sometimes when you are adding or editing products and other settings in Seller Admin while also testing your shopping cart buttons at the same time, the cookie we set in your browser to track your cart contents can get confused, so only the latest item added to a cart will show up in the cart, and any previously-added items will seem to disappear from your cart. Clearing the cookies in your browser will fix this for you.
E-junkie cart needs to be tested online. For the cart in your page to work correctly, the page where you paste your E-junkie cart button codes must be:
- Uploaded on a live Web site (a "local" copy of a page saved to your computer's hard drive won't work);
- Have a domain name in its URL (a URL using just a numeric IP address won't work);
- Tested in a regular Web browser (the "preview" mode built into many Web-design programs probably won't work);
- Accessed from a computer with a live Internet connection (loading the page and then going offline will not work).
If the information provided above didn't resolve the problem for you, see below for some other, more obscure reasons that may be causing your problem.
Also, make sure all your products are priced in the same currency. The cart can only hold items that are all priced in the same currency because payment processors cannot handle checkout totals split into differing-currency subtotals. Clicking an Add to Cart button/link for an item priced in a currency different from items previously added to the cart would "reset the cart" by dumping the earlier items and starting over with only the latest item added to the buyer's order.
Differing sites or E-junkie accounts
Items from different E-junkie accounts can't be added to the same cart together, so if you use more than one E-junkie account for different sales sites, make sure each site only uses E-junkie cart buttons from the same E-junkie account.
When our overlay-style cart appears within your page, it sets a "first-party" cookie for your own site's domain to track the contents of each buyer's cart. Due to the way browser cookies work, this means our overlay-style cart can only hold items added to it under the same site domain, as cart buttons on different site domains will set different cart cookies.
If you need buyers to be able to add items to a common cart from separate sites under different domains, one workaound for this would be to omit our Cart Script code from all your sales pages, so all cart buttons/links would open a new browser window/tab to display the cart at our
This could affect some sites hosted at a subdomain under a Web site host's shared-hosting domain—e.g.,
your-name.hosting-domain.com. Our overlay-style cart needs to set a cookie in each buyer's browser to track their cart contents; however, browsers won't allow setting a cookie on well-known shared-hosting base domains (e.g., the
appspot.com domain used by Google's AppEngine service), as that could allow different sites hosted under that domain to read each others' cookies.
In this case, one workaound would be to omit our Cart Script code from all your sales pages, so all cart buttons/links would open a new browser window/tab to display the cart at our
We have identified an issue affecting newer browsers and certain sites using frames, where the domain of the master frameset page URL does not match the domain of the actual pages being displayed inside the frame which are using our cart buttons.
E.g., if you are using a site-builder service that hosts your actual, individual pages at something like this:
...but you are displaying those individual pages inside a frameset "wrapper" page with a URL on your own custom domain, so that a visitor's browser only shows the site's Web address as:
...then our overlay-style will not work for certain visitors, depending on their browser's cookie settings. This also affects cases where the page at one domain is using an IFRAME to display a page from another domain which contains our cart buttons.
Modern browsers (starting with Internet Explorer 7, Safari 3, Firefox 3, Google Chrome and Opera) have increasingly added an option to "Block third party cookies" or "Only accept cookies from sites I navigate to directly"; Safari and lately Firefox 22 even make this the default setting, whereas the other browsers optionally allow the user to enable that setting. Our standard cart always sets the buyer's cart-tracker cookie as a "first party cookie" with the same domain as your page which contains our View Cart button code; however, if the URL of the cart page itself has one domain, but the Web address visible in the browser's address bar has a different domain (because of a frameset wrapper or IFRAME), then newer browsers will treat that as a third-party cookie (just as if it were a banner ad displayed in an IFRAME).