What to put in JS Excludes to make plugin work

I think LS Cache supports wildcards, doesn’t it? If so, I’d do something like *caos*.

I tried adding caos and *caos* but neither worked.

This is what the LS cache documentation says:

JS Excludes

If you enabled minification, combination or push for JavaScript in the JS Settings tab, you may exclude some JS here. Use this space to list any JS files (one per line) you would like excluded from the optimization functions. You may enter full URLs or a partial string. There’s no need to use wildcards in partial strings.

The default exlusions in the JS exludes list are java-script files, ending with .js.

• This reply was modified 1 year, 11 months ago by krha86.

Did you flush LS Cache’s cache afterwards?

Just to verify that LS Cache is actually the issue, when you disable LS Cache, does CAOS’ tracking code appear?

Yes, I flushed all cache. And yes, when I disable LS Cache, the tracking code appear.

By default, CAOS stores all of its generated files in the /uploads/caos directory. So, just adding caos to the list of exclusions should do the trick!

Did you change the Cache Directory (under Advanced Settings) by any chance? If so, try adding (a part of) that path to the list of exclusions.

If that doesn’t work, I suggest you contact the LS Cache support, because CAOS doesn’t seem to be the issue here.

I didn’t change the path, no. To clarify, are you suggesting adding caos or *caos*? It would be helpful with a guide on how to make the plugin work with the most common caching plugins. After all, most sites use them.

I don’t know the technicalities of how your plugin works, nor does LS Cache support, so asking them for support in this issue would be shooting in the dark.

Well, you could try both. Did you? Either one should work.

This issue really isn’t about CAOS, since CAOS does what it should do — generate the files in the uploads/caos directory and add the tracking code. And all that seems to work. The thing that seems to be malfunctioning (maybe) is LS Cache’s exclusion setting, because it keeps grabbing the files and tracking code and combining it into one JS file, even though you added CAOS’ uploads directory to its list of exclusions.

I’m sorry, but I wouldn’t know how to help you further. CAOS doesn’t seem to be the issue here.

I agree the issue is not with CAOS. The issue is knowing how to set up LS Cache properly to work with CAOS.

I believe it would benefit your plugin if you provided instructions on how to make it work with caching plugins like LS Cache. E.g., which files and directories to exclude and how to do so, known compatibility issues, etc. I hardly believe the LS Cache JS Exludes feature is malfunctioning, but I’ll reach out to them to ask.

Great! Adding caos or *caos* to the list of exclusions should both work (and has worked in the past):

You may enter full URLs or a partial string. There’s no need to use wildcards in partial strings.

That’s why it’s weird that it’s not working.

Anyway, I hope they come up with something.

• This reply was modified 1 year, 11 months ago by DaanvandenBergh.