Problem/Motivation

Recently, an entity operations field was introduced for search api based views.

The views row caching doesn't take the URL into account. That means, the operations link including the destination query parameter, is generated just once.
So if you are using facets, for example, to drill down the search results and then using an entity operation you come back to another page from where you left the view.

Proposed resolution

Add the url as cache context.

CommentFileSizeAuthor
#2 3032916.patch543 byteschr.fritsch

Comments

chr.fritsch created an issue. See original summary.

chr.fritsch’s picture

Status: Active » Needs review
StatusFileSize
new543 bytes

Here is a patch.

borisson_’s picture

Status: Needs review » Reviewed & tested by the community
drunken monkey’s picture

Status: Reviewed & tested by the community » Fixed

Thanks a lot for reporting, and already providing the patch to fix this!
Ideally, I think, the redirect.destination service should provide the proper cache metadata itself, as 'url' will not always be the 100% correct cache context. But as we don’t have that, the current patch looks good enough, too – wouldn’t know what else to do.
So: committed.
Thanks a lot again! (Also to Joris for reviewing, of course!)

drunken monkey’s picture

Status: Fixed » Closed (fixed)

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