This module has an awesome feature that allows you to render the current page's node in multiple blocks using whatever view mode you want. The issue is that the cache context and cache tags for the block do not reflect the need to have access to the current route's node, so once the block has been rendered once it will cache itself and be used even if the route changes.

I would suggest adding getCacheTags() and getCacheContexts() to the NodeBlock class.

Comments

jpschroeder created an issue. See original summary.

jpschroeder’s picture

Issue summary: View changes
StatusFileSize
new913 bytes
jpschroeder’s picture

StatusFileSize
new1.1 KB

Needed a use statement which has been added in this patch.

jacobbell84’s picture

Status: Needs review » Reviewed & tested by the community

I was having the same issue on a recent project and the above patch solved the problem.

  • tanc committed 8f8f5b3 on 8.x-1.x authored by jpschroeder
    Issue #3044455 by jpschroeder: No cache context or cache tags causing...
tanc’s picture

Version: 8.x-1.0-alpha1 » 8.x-1.x-dev
Status: Reviewed & tested by the community » Fixed

Thanks for the patch and for testing. Committed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.