Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow CMS pages to not be banned in Varnish when products are updated #23

Closed
wants to merge 5 commits into from

Conversation

glennslaven
Copy link
Contributor

Adds a new option to the Full Page Cache configuration section in Stores
configuration "Include CMS Pages in product purges". If set to No, CMS
pages will not be purged when a product is updated, even if that product
is displayed on the page. CMS pages will still be purged if their content
is updated.

Adds a new option to the Full Page Cache configuration section in Stores
configuration "Include CMS Pages in product purges".  If set to No, CMS
pages will not be purged when a product is updated, even if that product
is displayed on the page. CMS pages will still be purged if their content
is updated.
]);

$info = $this->aperture->executeAuthRequest($uri, 'POST', [], self::BAN_TIMEOUT_SECONDS);
if ($info['http_code'] != 200) {
$this->logger->execute('Error executing purge: ' . $tagsPattern.', Error: ' . $info['body_content']);
return false;
}
$this->logger->execute(compact('server', 'tagsPattern'));
//$this->logger->execute(compact('server', 'tagsPattern'));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove dead code.

Copy link
Contributor

@calvinbrewer calvinbrewer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified working on www.cjb.io

@glennslaven glennslaven closed this Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants