piotrmerton

Hey @rockfire here’s the followup. I investigated a little bit further why the expired records still have “Active” flag and I narrowed it down to either 1) specific server configuration or 2) Redis Object Cache – because on localhost it works as intended, so it looks like issue is not with WP Rest Cache plugin itself.

• This reply was modified 2 years, 8 months ago by piotrmerton.

That is not correct. WordPress uses jQuery only on backend and forcing loading whole library in front, almost 100 KB of technically debt code, for just one AJAX request is very bad practice. Are you familiar with Core Web Vitals? Enqueing this amount of not usable code will drastically alter Time To First Byte metric, especially on mobile.

Regarding FontAwesome – it’s just pure madness. The CSS alone is 46 KB which is nuts (my whole site, which I consider rather complex is 50 KB). But ON TOP OF THAT it requires additional 15 files of webfonts which are well over 2 megabytes (!!!). All of this for just two icons is just lazy coding.

• This reply was modified 2 years, 8 months ago by piotrmerton.
• This reply was modified 2 years, 8 months ago by piotrmerton.

Thank you for your reply and thorough explanation.

For now could you try and delete the cache record (delete, not flush) and see if the problem will reappear? Just to check if it is reproducable on your installation.

After deleting records the problem still persisted and expired cache weren’t regenerated. It happened to all custom endpoints added to wp_rest_cache/allowed_endpoints hook. On both production and dev environment. I ended up disabling plugin for the time being.

If you are interested I can provide code to theme via private message, though I pretty much copied example from your “Can I register my own endpoint for caching?” FAQ question.