Hi Richard,
Dylan here from the development team, my apologies for the delay.
Thank you for reaching out, we are eager to work through this issue with you.
Yes, that is correct, we do send a shared WP REST nonce with all requests. In some cases, we take additional measures to allow editing of certain data.
With that said, we do pass this shared nonce on the public endpoints as well, which I believe is the reason they aren’t being cached.
Our team is looking into some alternatives on our side to add compatibility back into our core while accounting for the fact that you no longer cache calls which contain a nonce.
Hi @rockfire,
A quick update from our side, we have worked on this issue further within our core to support the integration moving forward.
You mentioned WP REST Cache no longer caches requests which contain a nonce. Within our core, these nonces were added to all marker data requests automatically, regardless of whether or not the request originated from the frontend of the site.
We have gone ahead and reworked this to exclude the nonce, as it is not required for the public marker data when the request is performed from the frontend.
This will be included in out 8.1.0 release which is scheduled to be released within the next few weeks as it is currently undergoing beta testing by the community. Once released, I will update this thread.
Thank you for your time on this, it was a tremendous help!