Wildcards (not yet supported)

Hi,

I’m not sure if you were one of the users that asked for this a few months ago, but can you confirm that this wildcard feature is for the ignore list?

I’ve been fixing other bugs and adding some other more relevant features, but this will come soon enough, probably a couple weeks or so (or earlier if I find some time).

Hi,

First time I’ve raised it, but happy to hear others are eager to have the option too, and that it will be available in the near future.

Yes, the wildcard feature to exclude, by which I assume we will be able to add partial locations to the source, for example:

/wp-content/uploads/theme-name/cache/general-1a4b9c6.css

the file name of this file changes every time there is a change to the styles that are built using a proprietary template builder/layout editor.

Each time a change is made, it’s saved dynamically to the database, after which a new cached version of the static file is generated, and the string changes (bit more to it than this, but that’s the crux of it)..

So it might become:

/general-1234abcd.css

Normally this wouldn’t be an issue, but this theme actually produces a live view of any changes made before they are saved (inside an iFrame), so if the current version of the styles is being served from a combined version, then the changes made to the dynamic stylesheet breaks things on save because FV will slurp that in too and serve a mixed bag.

This means that we also have to flush and disable FV every time while working on the site, and re-renable it after all the pre-cached theme styles have been generated.

We can’t exclude the file generically because the file name is a randomly generated string, so we also lose half of the entire power of FV.

However if we could exclude the files with a wildcard, it would solve that problem (it’s a horrible theme, but it is what I have to work with)

I’m assuming that once the wildcard functionality is added, we will be able to add the address and partial file name so that FV will read up to the point until the wildcard char is reached, and will then give that file the cold shoulder because it is such fickle thing ??

Something like this:

/wp-content/uploads/theme-name/cache/general*

Thanks, sorry for the waffle, I got carried away..

makes sense… but that’s really bad practice from the theme developer.

I have to push an update withing the next couple of days, will try to add this to the next version if possible.

lol, don’t get me going on the nature of this theme, it’s the bane of my life!! ??

No real rush, but it’s definitely something I’m quite excited to try. Can’t tell you how many solutions we have tried over the years. The closest we have come is to use Cloudflare with page rules, but that has other consequences.

Thanks, something to look forward to!

Hi, this has been added today.
Please check the faqs to learn how to use it.

Great, thanks very much for letting me know. I’ll test it out and let you know how it goes