Issues with filter cache and embedding views slideshow
Scenario:
Drupal 7
Views and Views Slideshow module
Custom blocks with PHP_CODE input format to embed the views
This normally works only once after caches are cleared. After the first page load, the slideshow images would appear but the cycle would not work.
Reason:
The block system uses cached values of the content from filter module (even through blocks may not be cached), the filter content is always cached and this can't be disabled. The php input_filter evaluates the code and caches the result. Now when the code is evaluated, as a side effect, the slideshow module adds the appropriate required js files.
Subsequent page loads would not emit the required js files, but only the static html from the embed_view. If the view did not rely on additional js files, this would have worked. But in the case of slideshow plugin (or a similar plugin that adds its own extra js/css files) would break.
Work around:
Instead of building a custom block, configure the view as a block and then use display output theme override in view to add any customizations and use the views block. The views block is not cached the way filters are cached. So, this would always work.
Scenario:
Drupal 7
Views and Views Slideshow module
Custom blocks with PHP_CODE input format to embed the views
This normally works only once after caches are cleared. After the first page load, the slideshow images would appear but the cycle would not work.
Reason:
The block system uses cached values of the content from filter module (even through blocks may not be cached), the filter content is always cached and this can't be disabled. The php input_filter evaluates the code and caches the result. Now when the code is evaluated, as a side effect, the slideshow module adds the appropriate required js files.
Subsequent page loads would not emit the required js files, but only the static html from the embed_view. If the view did not rely on additional js files, this would have worked. But in the case of slideshow plugin (or a similar plugin that adds its own extra js/css files) would break.
Work around:
Instead of building a custom block, configure the view as a block and then use display output theme override in view to add any customizations and use the views block. The views block is not cached the way filters are cached. So, this would always work.