Recent updated to 7x.1.8, node update seems not longer trigger varnish to purge if it has 'varnish_flush_cron' disabled.

This seems to related to:
https://www.drupal.org/project/varnish/issues/2920579.

Looking at: https://cgit.drupalcode.org/varnish/tree/varnish.cache.inc?id=c0eb2ec902..., !variable_get('varnish_flush_cron', 0)

if varnish_flush_cron is disabled, nothing will send to varnish even 'varnish_cache_clear' set to 1.

I'd like propose a patch, so that when 'varnish_cache_clear' is set to 1, it should be able to tell varnish to purge.

CommentFileSizeAuthor
#8 varnish-2944565-8.patch655 bytesmisc
#2 varnish-2944565-issue.patch795 bytesphuang07

Comments

ph53 created an issue. See original summary.

phuang07’s picture

StatusFileSize
new795 bytes

Just found out I have the variable name described incorrectly in the issue summary above..

I mean to say this:

Recent updated to 7x.1.8, node update seems not longer trigger varnish to purge if it has 'varnish_flush_cron' is disabled.

This seems to related to:
https://www.drupal.org/project/varnish/issues/2920579.

Looking at: https://cgit.drupalcode.org/varnish/tree/varnish.cache.inc?id=c0eb2ec902..., !variable_get('varnish_flush_cron', 0)

if varnish_flush_cron is disabled, nothing will send to varnish even 'varnish_cache_clear' set to 1.

phuang07’s picture

Issue summary: View changes
misc’s picture

Status: Active » Needs review
punch’s picture

+1

drilauri’s picture

Same issue as well. When I update a node, it's still serving the cached version. I'm manually restarting varnish on every time-sensitive update to the site.

jozzhart’s picture

+1

misc’s picture

StatusFileSize
new655 bytes

Updated patch.

  • MiSc committed 0f6ea9a on 7.x-1.x authored by ph53
    Issue #2944565 by ph53, MiSc: Node update not clear varnish cache
    
misc’s picture

Status: Needs review » Fixed

Committed to dev, and will be out in the next release today.

Status: Fixed » Closed (fixed)

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