Ari Stathopoulos

Actually the filter works fine and it is correct. The empty value it passes is correct, by default there is no fallback image (no image = empty string)/
The fallback image will only be used if for some reason the gravatar image can’t be locally downloaded.
But I’d suggest you try with a non-SVG image ??

@jasonsahli The Neve theme has a class called Pagination. Inside that class, they have a method called register_endpoints. Inside the Pagination->register_endpoints() method they are calling the register_rest_route function, and in the arguments they pass to it they don’t include a permission_callback as the error you’re getting mentions.
Judging from their code, the callback they are performing doesn’t get any private data so they can simply add this line in their arguments to make it work properly:
'permission_callback' => '__return_true',
So the end code on that method would look like this:

public function register_endpoints() {
	register_rest_route(
		'nv/v1/posts',
		'/page/(?P<page_number>\d+)/',
		array(
			'methods'             => \WP_REST_Server::CREATABLE,
			'callback'            => array( $this, 'get_posts' ),
			'permission_callback' => '__return_true'
		)
	);
}

You can contact your theme theme-author with that information so they can fix it. ??

Thank you for the feedback!

1. Is the “purchase offset” a one time transaction? (getting an error message here if I try to purchase. I have entered the correct Cloverly Public API

Yes, it’s one-time transactions. Good point, I’ll need to add extra descriptions.

2. Carbon Footprint Settings: what unit do I enter here? grams, kilograms?

Grams.

3. It would be a really neat feature to display a badge on the website to show visitors that I am offsetting carbon footprint with my website

Great idea!

I’ll start working on these and release an update as soon as possible. ??

@ygirod I’m afraid I can’t replicate the issue…
I just released v1.0.4 which has a potential fix for this.
If that doesn’t fix your issue, could you please tell me what PHP version your site uses? It might be related to that so if I have more information I may be able to reproduce the issue and fix it ASAP.

Hello @sebfck

The @font-face calls may include all languages, but they also include unicode-ranges.
As a result, only the characters used by your website are loaded. Even though the styles contain references to files for all languages, the browser only loads the ones it actually needs.
That is because we have carefully chosen the user-agent we use (you can see it here: https://github.com/kirki-framework/kirki/blob/0e0a09cdae56971d1dacdb778b109343594c92f0/modules/webfonts/class-kirki-fonts-downloader.php#L184) so it’s the only user-agent that supports unicode-ranges (to improve performance) and woff files (for IE11 compatibility).
Removing references to other languages will not save you any data.

I hope that helps!

Yes, it is.
I always forget to update the “Tested up to” plugin header…
Thanks for the update, I’ll pass it on to the right person ??

I suspect you will have to contact your theme author.

Kirki outputs the styles defined by your theme, and they styles it outputs by default are valid. If your theme does something to invalidate them by using a filter or other means then you should contact their support.

The new solution is a lot faster and there is no way to go back to the previous method, unless of course you just use an old version of the plugin.
It may look a bit uglier when you view the source of the page, but it actually generates a lot less CSS, it’s a lot more private since fonts are on your own server instead of google. It’s faster for your server to compute, it’s faster for clients to render. Why would you ever want to go back to an older and far worse method?

Fixed in v3.1.2, will be available in a few minutes.

Thank you for reporting this, I would have missed it otherwise ??

This was actually a false-positive from the Envato Theme-Check.
However, a fix to accomodate it was just pushed in v3.1.1.

@drorbek I justchecked that site and fonts get loaded just fine, I don’t see any 404s there.
Is the problem on a different page, or has it been resolved?

Version 3.1.0 was released just a few minutes ago, and the fonts downloader was completely refactored.
Please try updating to that version and let me know if that version fixes this… This should no longer be an issue.

Try updating to v3.1.0 (released just a few minutes ago). The fonts downloader was completely refactored, so this should no longer be an issue.

You can do that using the tooltip argument. ??

This is a server-configuration issue and not related directly to the plugin so I’ll go ahead and mark it as resolved.
If however you find that there’s something wrong in the plugin which causes this, please let me know ??