I'm not sure if this problem is due to a problem with views caching in general, compatibility with the views content cache module, or a bad mix between caching, js, and quicktabs. I've created a basic VBO view for deleting user generated content with only a Delete button. This is nested inside a view style tab within quicktabs. It works as expected until I enable views caching on the view. The form renders fine, but clicking the delete node button does not delete the node. I don't absolutely need the caching, but it would be helpful as there are 7 tabs, one for each content type the user can manage. Any help would be great.

Comments

infojunkie’s picture

infojunkie
Location Vancouver
commented

Thanks for your report. I was able to reproduce this issue with the stock VBO and caching turned on.

KeyboardCowboy’s picture

KeyboardCowboy
Primary language English
Location Denver, CO, USA
commented

I was also able to replicate this issue, though not by choice. :)

For what it's worth, I was able to move through each step of the form only when I used Devel to clear the cache between each step, which makes sense since it is a views caching issue.

For me, when I submit the form, it simply takes me back to the view, no errors reported. I've have some experience with the Form API, and my guess is that the form token or some internal part of the form is being cached with the view.

Hope that helps.

shane birley’s picture

shane birley commented

I ran into this recently. I believe the issue is the same:

  1. Views 2.16
  2. VBO 1.13
  3. Views are have caching turned on.

When nodes are selected, they are not deleted. Part of the nodes are have imagecache elements in them and the images are removed but the nodes themselves are not removed.

tomhung’s picture

tomhung commented

We also have this issue.
VBO: 7.x-3.0-rc1
Views Content Cache: 7.x-3.x-dev

Greg

azinck’s picture

azinck commented

Also having this issue, but I think it's tied to *any* Views caching plugin. Seeing it with Views Content Cache and Views' built-in time-based cache.

bojanz’s picture

bojanz commented
Issue summary: View changes
Status: Active » Closed (works as designed)

VBO can't work with the views cache on (it's architecturally impossible). Disable the cache.

jweirather’s picture

jweirather commented
Version: 6.x-1.11 » 7.x-3.x-dev

Is this still true in VBO 7.x? Turn off views content cache?

azinck’s picture

azinck commented
Title: Node delete action doesn't fire if views content cache is enabled. » Node delete action doesn't fire if views cache is enabled.

@jweirather: Yes, that's correct. VBO won't work with Views caching in 7.x.

kopeboy’s picture

kopeboy
Primary language Italian
Location Milan
commented

wow

Maybe document this?
was not so easy to find.. and it's quite a big thing :/

joelpittet’s picture

joelpittet
he/him
Primary language English
Location Vancouver
commented
Status: Closed (works as designed) » Active

Haven't dug into the architectural problem yet but I can't see why caching wouldn't work if we just cleared the views cache for the view CID after delete?

Reopening to see if someone wants to try it.

alex.bukach’s picture

alex.bukach commented
Status: Active » Closed (works as designed)

The issue seems to be caused by Views module itself, please check https://www.drupal.org/node/2354809.

giorgio79’s picture

giorgio79 commented

I was able to circumvent this form issue by disabling "Rendered output" caching, so only the query result is cached.