How to cache a view display with add to cart forms

The issue here is that Views is then caching form HTML which will be invalid for anyone besides the initial user who generated the cache. It will even be invalid for that initial user after he or she submits the form once, because it will require a new token on subsequent submits. Unfortunately, for the Add to Cart form, you just can't cache it like that. You could cache it if you were using Add to Cart links instead of forms, but that might result in other issues web crawlers generating carts - I'm not sure if the Rules Links module can prevent that.

So we cant cache a view for a store using add to cart buttons? Seems rather limiting doesn't it?

This might be outside the scope of this issue.

Is it possible to cache "everything else" in the view - entities, nodes etc to increase performance, leaving the view without the time-based cache?

We are looking to a solution to increase performance, so any suggestions, modules are greatly appreciated.

Best

Eric

Hi,

Would the Views Per-User Cache solve this issue?

https://www.drupal.org/project/views_puc

Best Eric

Now I can suggest only cache query results, not the HTML code :(

This is a limitation of the Views form API, not something we control or can change at this point.

My recommendation is to unset the form token of the form. The security impact (CSRF) is low from our perspective.

Then cache the view as usual.

function mymodule_form_alter(&$form, &$form_state, $form_id) {
  if (strstr($form_id, 'commerce_cart_add_to_cart_form') || strstr($form_id, 'views_form_commerce_cart_form_default')) {
	// Remove tokens for add to cart forms
	unset($form['#token']);
}

If I disable the form token as in #6 will any Drupal Commerce functionality be affected?
ie. is the token only related to security? In which way?

My particular concern is about multiple anonymous user carts functionality (not a developer).

Sorry for this, eventually realised my comment and question had nothing to do with the issue posted.

I agree w/ Bojan and disagree with security implications; I'd never intentionally make form submission less secure.

Hi, Hopefully some kind soul can clarify this for me...

1. Is it approved to use query caching (not HTML) as ofry #6 suggested?

2. I'm also wondering if distinct or aggregation will affect this issue in any way?

Thanks!

/Mats

https://www.drupal.org/sandbox/xandeadx/2540000

That was causing our site's Add to cart button to fail if used on a 2nd product in a view (even a non-Ajax view). We found we could still cache if we used Views, caching > time based > cache raw query results (1 hour) but NOT cache rendered output.