Hello,

I configured the plugin with a Fastly token and service ID. When I click Test connection, it says “Record not found”. Hoping to get more information than that, as I’m not sure how to proceed.

Please could you provide some more information on why this plugin has been closed? Should we be looking to remove this from our sites?

After hitting the Update VCL button, the loader is shown and then disappears, leaving the Confirm VCL Update popup. I can then save changes or cancel. When trying to save changes again, it does the same thing. Test connection states that connection is successful.

When using PHP 8.1 on WordPress 6.2 we get an error when trying to update pages – ‘response is not a valid JSON response’ and a fatal error in the error log:

PHP message: PHP Fatal error:? Uncaught TypeError: handle_logging(): Argument #1 ($response) must be of type Requests_Response, WpOrg\Requests\Response given, called in /var/www/***/htdocs/wp-content/plugins/fastly/src/classes/purge-request.php on line 72 and defined in /var/www/****htdocs/wp-content/plugins/fastly/src/utils.php:261

How does the Fastly Cache Tags work?

I can enable it then I see under posts the Fastly Cache Tags then I can creat the tag but how do I assign it to a post? I see no option to assing it to a post so confused, what to do?

Hello,

I’ve enabled Fastly Cache Tags under Advanced.

In wordpress I see where I can create tags under:
– Posts
— Fastly Cache Tags

So I can create them but how do I assign them to a post? I tried while editing a post under the default tags field but could not find the tag I created and there is no new field/area to assign Fastly Cache Tags.

I also cannot find the answer anywhere online so any help will be appreciated.

Thank you.

The only odd behaviour with wordpress cache plugins and fastly is that fastly surrogate control & other headers disappear.

If you take the top 3-4 plugins there should be compatibility with Fastly so that we can still do CMS & Server side caching and control all the headers including surrogate.

As example an option to override WP Rocket, W3 Total Cache, Litespeed or WP Super Cache so if enabled it will use the Fastly plugin cache headers opposed to any from the cache plugins.

• This topic was modified 4 years, 4 months ago by tripledm.

The surrogate control defaults to the post default/general default opposed to value set.

Surrogate-Control: max-age=604800

instead of

Surrogate-Control: max-age=120

and it is set for the categories. The home page works no problem and others just categories not responding to value set, eg 120.

(it is actually ignoring all of the custom TTL templates accept for the home page)

• This topic was modified 4 years, 5 months ago by tripledm.

Hi,
When creating a scheduled post, the purge requests occur when you click “Publish”.
But when the post changes from “scheduled” to “published”, no purges are sent (confirmed by logging purge requests to the error-log option). Therefore, if it is cached, old content is served.

According to the changelog, version 1.2.9 included an “added fix for scheduled posts transition to published” but I am using the last version, 1.2.12 and this doesn’t seem to be solved.

Could you check that this is actually a bug and hopefully solved in future versions?
Thanks

Hey folks,

A client of mine changed a post from public to private, but site visitors were still able to access it. Once I purged that URL on the Fastly end, it presented properly as private.

Can you think of a situation where the plugin may not send a purge request when swapping from public to private?

Does the plugin cache the WordPress Rest API and purge intelligently – if not, could you add that feature?

Hello,

I’m trying to use purgely_pre_send_keys hook to send my own keys.. but with not success.

I’ve tried:

add_action('purgely_pre_send_keys', 'custom_surrogate_keys');
function custom_surrogate_keys($my_keys) {
  $my_keys->add_keys(array('email'));
}

But its not working…
Can I get example how to use this function ?

Thanks,
Shani

I upgraded and the new version first ‘closed’ itself because the main plugin file was renamed and then, when I went to activate it manually, I got this error.

Fatal error: Can’t use method return value in write context in /wp-content/plugins/fastly/src/classes/vcl-handler.php on line 88

Is there a way to have this plugin purge the root of the domain “/” when it purges a page/post?

And/or a way to manually enter a URL to purge from WP admin instead of having to go to Fastly to purge.

Thanks!

Hi,

Just wondering would this integrate with multi site in a domain mapping setup ?

We have a large multi site install and have avoided CDN use as we would need to manually configure it for every users site.

Could you provide any insight on if your plugin was developed with multi site in mind and how it might interact with domain mapping ?

Thanks