Richard Korthuis

Hi @mdxclr

Thank you for using our plugin and for bringing this to our attention.

We were using a different collation on our test environment, which didn’t throw this error. I now changed it and was able to reproduce your error. We will fix this in our upcoming release.

For now, if you don’t want to wait until our next release you could change the file /wp-content/plugins/wp-rest-cache/includes/caching/class-caching.php and on lines 1186 and 1187 change the VARCHAR(xxx) to VARCHAR(191).

Hi @nicolauria

I see what you mean. It looks to me that some other plugin or code is adding content to the yoast_meta. It seems a complete post object has been inserted in the yoast_meta > content, because as you can see there is a new yoast_meta block within the content. That is not something our plugin does.
Are you able to deactivate the other plugins (maybe one at a time) to see if the problem disappears?

Hi @nicolauria

Thank you for using our plugin!

Unfortunately I am unable to view your screenshot (ERR_CONNECTION_TIMED_OUT), would you be able to upload it somewhere else and add a new link in this topic?

Hi @adorei

Thank you for using our plugin! And thank you for bringing this to our attention! You are absolutely right, this is indeed a bug which we will fix in our next version.

This is really strange. I tried to reproduce your error, but when I deliberately change the mu-plugin so it cannot find the plugin files anymore I do not get the “You do not have sufficient permissions” error. Instead I get: “There has been a critical error on your website. Please check your site admin email inbox for instructions.”. Which is what you might expect, since the fatal error is thrown.

May I ask which other plugins you have installed? It almost seems as if there is a conflict.

Hi @tntrush

Thank you for using our plugin!

The short answer to your question is: No.

All we ever intended to accomplish with our plugin is to offer an enpoint to RETRIEVE the Yoast Meta as it is generated by the Yoast SEO plugin. So a one-way retrieval of data. Unfortunately implementing an endpoint to alter this data is a lot harder and is not something we are currently planning to develop.

Hi @hansgv

Thank you for using our plugin!

I am sorry to hear you are experiencing this error. I hav had a look at your error log and what I notice is the following line:
PHP message: PHP Warning: include_once(/var/www/vhosts/mysite.com/wp-content/plugins/wp-rest-cache/wp-rest-cache.php): failed to open stream: No such file or directory in /var/www/vhosts/mysite.com/wp-content/mu-plugins/wp-rest-cache.php on line 25
What it tells me is that the mu-plugin was successfully installed (in /var/www/vhosts/mysite.com/wp-content/mu-plugins/), but that it seems that the main plugin was not installed in /var/www/vhosts/mysite.com/wp-content/plugins/wp-rest-cache/. How did you install our plugin? And what did you do with it afterwards? Did you rename the plugin folder? And is your plugins folder indeed situated in /var/www/vhosts/mysite.com/wp-content/plugins/?

Somehow the mu-plugin is there, WordPress is telling it that the wp-rest-cache plugin is in fact activated. But it cannot find the plugin files in the correct location.

Hi @marcosfreitas

Thank you for using our plugin!

You are responding to an already resolved issue, in the future please open a new issue, because your question might otherwise be missed.

In your example code I am missing the function wprc_add_acf_posts_endpoint. Since you are using that function name, I am assuming you already found our FAQ about adding your own endpoint for caching. That FAQ should be enough to get you started.

Hi @jamiewarb

I have investigated this and Yoast alters the <title> using the wp_title filter. Using our plugin I do not want to alter anything from the default WP REST API, so we will be adding this title in a new yoast_title field next to the yoast_meta and yoast_json_ld. I will let you know once we have implemented and release this.

Hi @mdxclr

Thank you for using our plugin.

We just released a new version of our plugin which should solve this problem.

Hi @djibs13

Thank you for using our plugin.

We just released a new version of our plugin which should solve this problem. Please let us know if it indeed was solved for you.

Wow, you have proven your point ??

I will add it to our todo list, to make it optional to delete inactive entries automatically.

Hi @workforpizza

No there isn’t a cron deleting invalidated cache entries, the entries in the wp_wrc_caches table are preserved in order to keep the statistics (nr of cache hits) alive. The cache itself and the relations (in the wp_wrc_relations table) are deleted.

Since you are asking: can I ask how big your wp_wrc_caches table had become? Maybe we should reconsider deleting more data…

Yes if you first click “Clear REST cache” and then fully clear both tables you are indeed back to a fresh start.

Hi @waffl

Thank you for using our plugin!

Yes you can allow non-admin users to clear the cache. In the latest version of our plugin we added a filter for this. See this FAQ-item on how to use it.

By the way: Our editors would like to see changes reflected immediately. > They should see the changes immediately if we are talking about default WordPress endpoints. In that case the plugin will flush the related caches once you edit/add a post/page/taxonomy/… Only if you have created your own custom endpoint the caches will not be flushed automatically.

• This reply was modified 5 years, 3 months ago by Richard Korthuis.