Acato
Forum Replies Created
-
Forum: Plugins
In reply to: [WP REST Cache] Question about custom endpointsHi @mighty_mt
It took some time, but we just released a new version of our plugin which fixes this issue. Please let us know if you have any more issues.
Forum: Plugins
In reply to: [WP REST Cache] Expiry cache does not display the correct time.Hi @djibs13
Thank you for your feedback, the displayed time was indeed incorrect. We just released a new version of our plugin which fixes this issue. But keep in mind: it will not be fixed for already cached items, but it is fixed for newly cached items. So if you want the times to be displayed correctly you have to flush the caches unfortunately.
Forum: Plugins
In reply to: [WP REST Cache] Cache flush does not work in some situationsHi @djibs13
I tested all your use cases on a local installation and it worked as it should (flushing the cache at the correct time).
Could you check Settings > “WP REST Cache” > Tab: “Endpoint API Caches” and search for the record with the comments cache (Request URI =
/wp-json/wp/v2/comments) and click Details. I am interested in the information under “Cache info” (so not the “Cache data”, since that contains the actual comments and might contain personal data). I am hoping it will tell me something about the cause for this strange caching behaviour.Forum: Plugins
In reply to: [WP REST Cache] Cache flush does not work in some situationsHi @djibs13
Thank you for using our plugin!
You say “in many situations there is no flush”, so there are situations where the cache is flushed? This question is just to be sure, because if there are situations with cache-flushing it might not be an issue with your configuration (for instance the memcache(d)-issue was always present).
I must say we generally don’t use comments on the sites we build, so the comment-caching part is probably tested the least (it is tested of course, but since we don’t use it ourselves….). So I will have to do some extra testing to see if I can reproduce the cases you describe (thanks for the description of the cases by the way).
Forum: Plugins
In reply to: [WP REST Cache] Cache gets flushed automatically and not getting regeneratedThis thread has been marked as resolved due to lack of activity.
You’re always welcome to open a new topic.
Thanks for understanding!
Forum: Plugins
In reply to: [WP REST Cache] Most of the endpoints are showing as expiredHi @metawise
No it should start caching without any extra configuration. There are however two situations (we know of) in which this might happen:
1. If your server is using FastCGI: This is a known bug, see https://wordpress.org/support/topic/question-about-custom-endpoints/#post-11711843 We are working on a fix, which I expect to be releasing this week.
2. If you are using Memcache(d) as external object cache. In this case you should see a message in wp-admin:
WP REST Cache: We have detected you are using external object caching. If you are using Memcache(d) as external object cache, please make sure you visit this plugin's settings page and check the Using Memcache(d) checkbox.Please follow the instructions from this message and it should be solved.Please let us know if any of these two situations applies to you.
Forum: Plugins
In reply to: [WP REST Cache] Custom Rest API End PointHi @sthubbins
Thank you for letting us know. However, I am very curious about that piece of code. Because the way we set up our plugin we wanted it to not have any impact on the normal output. If I understand you correctly a piece of code isn’t executed when our plugin is active, so I would like to investigate it and see if we can implement a fix for it.
Is it possible for you to share that piece of code?
Forum: Plugins
In reply to: [WP REST Cache] Custom Rest API End PointHi @sthubbins
Thank you for using our plugin!
Our plugin does not add any data to the output (like post_author or post_date). Basically what it does is:
Check if a cache is available
– Yes? > Return it.
– No? > Let WordPress process the request as it would do without our plugin and fetch the results to cache it.So the response should be the same in both cases.
Are you sure you aren’t doing different calls to the API when testing with or without our plugin activated?
Forum: Plugins
In reply to: [WP REST Cache] How to exclude specific itemsThis thread has been marked as resolved due to lack of activity.
You’re always welcome to open a new topic.
Thanks for understanding!
Forum: Plugins
In reply to: [WP REST Cache] JWT authentication compatibility?This thread has been marked as resolved due to lack of activity.
You’re always welcome to open a new topic.
Thanks for understanding!
Forum: Plugins
In reply to: [WP REST Cache] Response times not changedThis thread has been marked as resolved due to lack of activity.
You’re always welcome to open a new topic.
Thanks for understanding!
Forum: Plugins
In reply to: [WP REST Cache] WP Multilang cache issue PatchHi @hugomineiro
Thank you for using our plugin! And your kind words 🙂
We just released a new version of our plugin. For several reasons and the fact that the Item API Cache wasn’t adding a real performance boost (the real performance boost comes from the Endpoint API Cache), we have decided to remove it completely. So I would say that also solves your problem, right?
- This reply was modified 7 years, 1 month ago by Acato.
Forum: Plugins
In reply to: [WP REST Cache] Question about custom endpointsHi @mighty_mt
Good catch! But now how to solve it… We don’t like accessing the $_SERVER array without filtering, but will discuss this internally and see if we can come up with a different solution.
Forum: Plugins
In reply to: [WP REST Cache] How to exclude specific itemsHi @holaeffect
We just released a new version of our plugin, which includes the implementation of the caching based upon request headers. See this FAQ entry for more details.
Please let us kno if this solves your problem.
Forum: Plugins
In reply to: [WP REST Cache] Hide Clear REST Cache in Admin Bar MenuHi @testcouch
We just released a new version of our plugin, which adds a filter to hide the button. See this FAQ entry for the details.