Steven Chuob

@tollmanz the problem here is that the user has 2 difference service with different origin (dynamic/static) not that best setup. But because of the fact that Purgely only supports a...

@tollmanz I feel this scenario is not fairly common and agree with you. Is there a way for me to expose the surrogate-key for the homepage on the wp-purge.php? Right...

@tollmanz thanks! I will tweak my purgely for that. I simplify it a bit by doing this: ``` $temp_service_id = Purgely_Settings::get_setting( 'fastly_service_id' ); if ( $temp_service_id != '' ) {...

@tollmanz I tweaked this a bit as I found that blog-style vs static homepage treat is_home() differently. `is_front_page()` seem to work will. `````` add_action( 'wp', function() { if ( !...

@tollmanz I agree, i've already put together an internal doc for edge-cases and how to address them. So far we've only ran into one but pretty sure we should see...

From the logs provided it looks like the CLI is making a purge all request to: https://api.fastly.com/service//purge/all Checked the purgely code base and it shows that it should have been:...

After further testing it looks like if you use `wp fastly purge all` even though the status says ok - if you curl against the object again the age has...