What is happening here is that the product is being added to the cart via a javascript call and then it displays the cart modal over the top to confirm this - hitting the continue shopping button simply closes the modal window. So the form and page _itself_ doesn't actually do a POST and refresh.

So what you are seeing is as per the design/code.

Personally I've never seen this as a point of confusion, as I think the process is pretty clear that the item has been added to the cart and when you close that dialog you're not un-doing that action.

I'd actually find it if the options (and displayed price/image) selected on the product changed back after hitting add to cart a bit disconcerting:
- I'd pick my large size and yellow and see the price and image change
- I'd add it to the cart and get confirmation that it's in there
- I'd hit continue shopping and see the cart disappear
- The page updates and I now see the price change, the options change to small and purple and an imagine of a small purple thing.

I think that would I think make me stop and wonder what I'd just added to the cart.

If the shop is really only selling one thing, like a ticket, there is also the option to send the person directly to the checkout after they have added it to the cart.

Thanks for the confirmation. I thought it was how it was supposed to be, rather than an error.

I'm naturally comparing to systems I currently use. If I had a list of tickets/products that was just name, price and Add to cart button, and then on button click it opened the product block in a modal window, would that give me the end result I'm after?

I'm really just trying to understand Community Store and then see what tweaks I need to do in my thinking, or to the system to make it work for me situation.

As I keep saying this is an amazing add on.