problem with JS wordfence

To fix this please go to the WordPress admin dashboard > Settings > Cache Enabler > Cache Exclusions > Query Strings. Once here update this setting to be /^wordfence.+/.

if i have another string? how i can add this as well? i have the old string against fgclid, if i want both of them together? when i do it is not let me:
/^wordfence.+/
/^fbclid|utm_(source|medium|campaign|term|content)$/|/^wordfence.+/

is not working… you can help me how i can keep both?

The Query String setting is new in version 1.5. It will exclude query strings from the cache that match the regular expression added. What you have above is not required as I would assume you’re not trying to bypass the cache for query strings that contain fbclid (our old default behavior would include these query strings in the cache).

Is not, was a lot of problems with the last update, i was needed the add that and do an advance configuration to actually activate everything properly.
https://www.keycdn.com/support/wordpress-cache-enabler-plugin#advanced-configuration

please if you can provide both in one string and i will add it. i need to add a couple
of more things like NOCACHE and more plugin strings.

??? please how i can put multiple strings and not one? i have nginx as well (Engintron)
need to bypass a couple of things.

hello? please how i can add both? this impossible? please answer. site is very slow
without the fcgclid code, how you bypass that in cache enabler page speed go up 5 points.

I SEE YOU UPDATE THAT RIGHT NOW… THANK YOU.

This is fixed in 1.5.3.

this didn’t fix and this because of the expires in your plugin.
the string is not good as well you cant bypass gclid and “ga/ka”.
you have a great plugin but you destroy him with this new thing you did with him.

i recommended you look here:
https://github.com/engintron/engintron/tree/master/nginx

this is very familiar… this is Nginx with an interface for c-panel…
Most of the people and the host use it.
(this is certified Nginx from C-panel/ Eazy Apache 4

you expire don’t have MIME/TYPE and you cant actually set expire in your plugin.
especially if you use a mod expires inside your htacsses.

the string… the string you must change, please look on the link i sent you.
you must adjust yourself to this Nginx, and generally for nginx dynamic caching:
nginx.com/blog/compiling-dynamic-modules-nginx-plus/

you are a third party. need to be adjusted for dynamic cache, what you don’t have in your plugin.