José Miguel

As for the table in the database I will analyze.

Try to create a topic for each question. It is difficult for me to respond to several things at once.

@willstockstech,

If the plugin can not apply the permissions to files in principle is because the id of the owner of the file is different from the id that runs the web server.

@willstockstech,

Does your theme not use 160×160 in the get_avatar_url function?

<?php echo esc_url( get_avatar_url(‘[email protected]’, array(‘width’=>’160’, ‘height’=>’160’))); ?>

Hello @willstockstech,

Where is OGC showing a 160×160 image where it should be showing 120×120? In the sidebar of your theme?

Hello @geleosan,

Basically by inconsistency:
.Not always the gravatars have srcset.
. At other times, if the default gravatar is of type SVG, src and serset will be the same.
. Because the lazy load does not yet handle with srcset.
.Among others.

I plan to add an add serset option, but it has to be concise with the whole plugin.

I hope to add in version 2 of the plugin.

Hello @willstockstech

To be clear, a lot will change in version 2.

.Support for multisite.
.the names of the gravatars will be hashs representing the content. This way, when you change the content, it automatically changes the name. This will no longer need to invalidate url in CDNs, Cloudflare, etc.

So the support for w3 CDN is only up to version 2.

Hello @willstockstech,

I’ll have to analyze.

However w3tc_cdn_purge_files should work with most of the w3’s CDNs or all.

It must be a way that works for any CDN configured in w3.

Hello @willstockstech,

I have released version 1.4.3 that already supports “get_avatar_url”.

Your profile image in your sidebar will already be resolved from the cache.

As you know that the plugin does not support W3TC and the problem presented is due to something unsupported, this topic is resolved. Right?

Open a new Non-support topic and submit your request to add support for the W3TC.

I will stop the development of version 2 and support W3TC in version 1.4.4.

Describe your system environment!

Hello @willstockstech,

You need to clear the posts and also invalidate the gravatar on the CDN. Both are necessary.

In the afternoon I put here the code to deal with get_avatar_url.

In the future I intend to support w3tc.

However I’m too busy rewriting the entire plugin to split it into multiple files, to give a simple way to add cache plugin / optimization etc. A lot of work and little time. I will not be able to support w3tc now.

Hello @willstockstech,

As for the sizes you use in the images I already realized, it is to simulate the srcset for retina.

The modifications you made to support the “w3-total-cache” if it works seems to me good.

However I think the problem is in the CDN.

Cache image:
https://willstocks.co.uk/wp-content/uploads/optimum-gravatar-cache/avatar/3.jpg?d=thb95k

Image on CDN:
https://cdn.willstocks.com/wp-content/uploads/optimum-gravatar-cache/avatar/3.jpg?d=thb95k

There seems to be some sync problem.

Single posts are showing the old image, true.

Are the images 2.jpg, 3.jpg, 4jpg in the cache the same?

Just out of curiosity, what’s the point of using 160×160 images and then resizing them in CSS? Is there an advantage?

I removed get_avatar_url from the plugin I no longer know in which version. Because, it made the gravatars evaluated by the plugin several times.

I also do not understand why not just use get_avatar when we want an image with HTML. And just use get_avatar_url when we want a url to use in javascript for example.

Either way the sidebar gravatar is not local is from gravatar.com.

I will add get_avatar_url again in the plugin!

You can post the whole image tag <img />

• This reply was modified 6 years, 1 month ago by José Miguel.

Hello Will,

I see the same picture everywhere.