I have views paths such as
http://example.com/en/view/path1
http://example.com/en/view/path1
...

Which need to be expired when a node of a particular content type gets updated. So I set all the checkboxes for Cache Expiration on for the content type that goes into those views, and under "Enter custom URLs" I put:
view|wildcard

The problem is that the above views did not get expired from cache when a node was updated.

I then changed the custom URLs to:
view/path1

... and the given view did get expired from cache.

So I think that the wildcard system does not work (at least for view paths).

Comments

Spleshka’s picture

Spleshka
he/him
Primary language English
Location UAE
CreditAttribution: Spleshka commented

Hm, that is very interesting issue, I haven't even seen something like this. Do you have any other specific modules for cache, like varnish, purge and others?

lunazoid’s picture

lunazoid CreditAttribution: lunazoid as a volunteer commented

@Vacilando,

Did you ever resolve this? It appears as though we are experiencing a similar issue, where a view path with filters isn't clearing with the |wildcard option. The bare path, without any filtering, clears as expected (the bare path is also added to the list of paths to expire, though) however when filters are applied, it will not clear (which is getting the clients super upset.)

The expiration paths list includes:

course-search/face-to-face
course-search/face-to-face|wildcard

As mentioned, course-search/face-to-face clears, but any filtered version will not. If I do a manual purge on a filtered path, that works, but we can't add all possible combinations of filtered views to the expiration list.

Using expire 7.x-2.0-rc4 and acquia_purge 1.3.