skarck

@vmarko I can confirm this issue. The latest update broke multiple sites where the filter is used. Purging caches did not solve the issue, only disabling minification of CSS.

Thanks again @wfpeter !

I tried to debug this further with no luck. No errors show up in my error logs.

I also just recreated the setup in a simple php-apache based docker environment locally. Only plugins are the ones stated above + ACF 6.0.6. As soon as I activate the Wordfence plugin the queries start return with a 403.

Also tried to disable basically all Wordfence features and removed the “extended protection” but the problem persists.

Let me know if I can help you reproduce the issue!

@wfpeter Thank you for getting back!

I tried the steps you suggested and set the firewall into learning mode.
The interesting thing is that, watching the live traffic, both API calls with and without JWT header show up with a status code of 200 in the Wordfence UI. Meaning that there is no UI to add the calls to the allowlist.

However, in curl / axios / insomnia api client the calls with the JWT header come back with a status code of 403 (but with the correct body).

So it seems that one part of WF thinks the request is fine (handing the call to wp-graphql which return the body) but another part is flagging it as malicious and adding the 403 status code.

Again, disabling Wordfence completely solves the issue so it doesn’t seem to be an issue with the server env, cdn or proxy.

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

Hi @skibulk really good point! Did you find any hints on how to set a high value for page cache expiration time but short TTL for the browser cache?

Thanks, so you can confirm that it works like in my first assumption?

“new set of pages” === all URLs specified in the sitemap
&&
“new set of pages” != a batch of pages (set via ‘Pages per interval’)

thanks @mamunur34 ! but it only seems to prime the cache for the given post ID. Was more looking for a way to trigger the functionality defined in the W3TC settings including pages in the sitemaps etc… .

anyone else experiencing this problem?

Can confirm that!

Any news on a new version that fixes this?
Thanks!

I’m wondering how reliable this workaround is. How can we make sure the replaced part is the CPT slug of archives and single views and not – let’s say the slug of a subpage like /page/subpage/books/?

Thx!

Hmm, can’t get it to work. Here is what I tried:

• Setup a clean multisite environment with two sites.
• Enabled all the plugin settings, removed the post title “prefix”.
• Created a post, uploaded a few images to the post, but did not add them to the post content. The images show up in the “uploaded to this post” tab in the media modal which means that their post_parent is the post’s ID.
• Then I tell the plugin to duplicate the post to the second site.

The post is created but the media library of the site stays empty…:(
Am I doing something wrong?

I use the “add media” button to upload files in the edit post screen. This way files get automatically attached to the post (It basically means the post_parent of the file equals the ID of the post).

I only see the option to copy “content” images that are added to the editor. Let’s say I upload images (attached to the post) but do not add them to the post’s content because I display attachments in my theme. Is this supposed to work with the plugin?

thx!

Perfect! Thx!