All add-ons currently require PHP 7.4 or greater.

On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.

Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Clear cache

Status	Resolved
Add-on / Version	Speedy 1.8.1
Severity
EE Version	7.3.12

Harold Kuiper

Dec 13, 2023

Hi Brian,
On my end the clearing of cache doesn’t really work.
I use

{exp:speedy:clear items="local/{channel_short_name}s/{url_title}/" tags="{snp_cache_tags}|{channel_short_name}-container"}

The items is not clearing while the tags is. I add a tag to all entries now and by clearing the tag the cached item is being cleared.
But I would like to clear items as well, but that doesn’t work.
Like local/articles/asia-week-ahead-inflation-from-china-and-india-a-bsp-pause-and-australian-unemployment
This doesn’t clear the item. But when I add the tag ({url_title}) it clears the entry.
I use Redis.
Don’t know why it is not working.
And… when clearing it through tags: in this manner I create an enormous list of tags, maybe that one turns out to be slowing down everything (at least the clearing).
Best regards,
Harold

BoldMinded (Brian)

Did you try it without the variables? E.g. hard code the parameter values:

{exp:speedy:clear items="local/my_channel_name/some_entry/" tags="something|channel_name-container"}

Simplify it and hard-code it how you expect it to work, and see if it works or not.

BoldMinded (Brian)

I’m going to mark this as resolved for now b/c of no responses. Once you’ve tested it with hard-coded values in the tag parameters and if you’re still experiencing the issue feel free to re-open the issue.