José Miguel

Hello @willstockstech,

Already implemented, in the next version you will have access to this information on the stats page.

I’m working on a plugin, which will remove posts by ID in the “WP super cache” in multisite.

It was just to confirm, the problem is in my plugin.

Thanks for the time spent, and for your plugin too.

• This reply was modified 5 years, 11 months ago by José Miguel.

Thank you! @tomdupuis

Yes, these lines of code solve the problem.

Hello Will Stocks @willstockstech,

I really appreciate your interest in the plugin as I told you.

But to be more objective in the issues is better to open a new topic per issue.

As for the date and time for example:

You configure ‘Refresh Gravatar cache every 1 day’ whenever WP Cron runs the task of the plugin that is configured with the option ‘Check for outdated Gravatars every 5 minutes’ the number of users that you configure in the’ Number of users to check simultaneously 10 users’.

Of course if you set the ‘Number of users to check simultaneously’ option with a number greater than the number of (users that your site has as well as commentators), they will all be updated at once, and in this way it was possible know when the next task “Gravatar Cache Refresh” would happen.

But the idea is to give control to the user to control these variables to fit your site / resources.

WP Cron is not very precise when it runs the tasks. If your site has visits every second is acceptable, otherwise it does not always run the tasks at the desired time: https://developer.www.ads-software.com/plugins/cron/

If you want something more accurate it is better to configure the tasks to run through the system cron: https://easyengine.io/tutorials/wordpress/wp-cron-crontab/

Technically in terms of implementing day or hours is basically the same thing.

But I decided days at the beginning of the project, based on the analysis I made of both my users and users on other sites.

Unfortunately many people do not create an account in Gravatar and the ones they create do not change their profile image every day. The most normal is to change from months to months.

This is the reason I chose days.

I will have to analyze the Hummingbird later and I will notice what it cleans, but in principle it only cleans the files it creates.

It seems to me well to support CLoudflare as another option.
I’ll have to look at the API.

How do you clear Cloudflare’s cache manually, through some plugin or in your cloudflare account?

Do you share the ‘uploads’ directory with Cloudflare’s?

I am currently developing what I need to:
When users clear the OGC cache – clear the WP Super Cache cache;
When a gravatar is updated in OGC – Clear WP Super Cache posts containing comments and / or membership of the updated gravatar user.

For now I will only support WP Super Cache until it is functional, then I will try to support as many cache plugins as possible.

In the next version the button that allows to clear the cache is always active. The process of deactivating and re-enabling the cache will be done internally during processing.

Hello @willstockstech,

The button is disabled so it is mandatory to disable the cache first. In this way other requests that may arise do not obtain gravatars that do not exist or worse still get a gravatar from another person.

The cached gravatar ids are not the same as the ids of the wordpress users. The ids are assigned in order of resolution of the gravatars. This is to prevent users from joining through an ID, for security, and to make the image anonymous.

Hello @willstockstech,

Very well, in the afternoon I will be able to do some test if need be, from Lisbon.

Hello @willstockstech,

Yes it is true, expires is no longer sent.

But I continue to receive the corrupt image:
https://willstocks.co.uk/wp-content/uploads/optimum-gravatar-cache/avatar/2.png

So something is serving this image that no longer exists.