Daniel

Hi there,

There are known issues with the Minify engine in some caching plugins like WP Fastest Cache and many other plugins, including Jetpack.

That said, note that the Jetpack CSS file you referenced, https://c0.wp.com/p/jetpack/10.5.1/css/jetpack.css is already being served from our CDN as a static minified file. In other words, it’s not demanding resources from your server and it’s already been compressed into a lightweight CSS file (by removing extra whitespace and the like). I don’t see how else it can benefit from extra CSS compression.

If you plan to keep using the CSS minification/compression feature of WP Fastest Cache, I’d suggest you exclude that file. You can also ask their support for help doing that.

Regards.

• This reply was modified 2 years, 10 months ago by Daniel.

Hi there,

I was also not able to replicate the error on my computer using both Chrome and Firefox but I found a related forum thread on the Mozilla website:

https://support.mozilla.org/en-US/questions/913498

Here’s the relevant part of the answer there:

You get this error if you run out of memory when loading the fontfile or if there is something wrong with the layout (contents) of the fontfile. This is a protection against bad or malicious font files.

This might be a memory issue with your particular computer that’s affecting Firefox.

Hi there,

You can increase the number of related posts by using the jetpack_relatedposts_filter_options filter.

You can add the following to your theme’s functions.php file:

<?php 

function jetpackme_more_related_posts( $options ) {
    $options['size'] = 6; 
    return $options;
}
add_filter( 'jetpack_relatedposts_filter_options', 'jetpackme_more_related_posts' )

Note that the maximum of related posts that Jetpack can display is 6.

Regards.

• This reply was modified 2 years, 10 months ago by Daniel.

Hi there,

That’s a tracking pixel that Jetpack adds to your site via JavaScript for the purpose of tracking visits to your site. The majority of tracking of your site visitors is done in order to provide you with core services like site stats and if you are part of the Jetpack Ads program, ads.

In essence, it’s not currently possible via any option of the plugin to simply disable the addition of those tracking pixels to your site save for deactivating the Site Stats module and any other modules you don’t need that may require tracking (I don’t know of any other additional features apart from stats and ads).

Kind regards.

• This reply was modified 2 years, 10 months ago by Daniel.

Hi there,

Thanks for writing in about this. I know you already said you disabled Akismet and the problem still persists. However, I’m still curious to know what your Akismet strictness option is currently set to. There are two options:

1. Silently discard the worst and most pervasive spam so I never see it.
2. Always put spam in the Spam folder for review.

As the names imply, the first option aggressively trashes spam comments, contact form messages, and so on, while the second option (which is the default) sends spam to the “Spam” section of the Comments or Feedback screen for further review.

What you describe is possible under the first condition. Do you also know if ZeroSpam has the same or a similar setting?

Jetpack shouldn’t interfere with contact form submissions in this manner, so I’d recommend contacting Akismet support about the issue before we completely rule it out as a possible cause:

https://akismet.com/contact/

Kind regards.

Hi there,

I understand your hesitation to deactivate your site’s plugins especially when it’s live. I’ve just looked into that error you’re seeing again and it looks like the server error is on the Facebook side, which Jetpack doesn’t have any control over. I’d recommend trying again maybe from a different browser for good measure.

Let us know how that goes.

Hi there,

Thanks for catching that and sharing your workaround. Note that this is the sort of thing that would be great to post on the public GitHub repository while referencing the relevant line/file:

https://github.com/Automattic/jetpack/issues

I’m marking this thread as resolved in any case.

Kind regards.

Hi there,

I’ve taken some time to look into this and I found that while your site loads at https://www.rehwolution.it, it doesn’t load at https://rehwolution.it. In other words, your site is accessible at the www subdomain but not at the root domain. I suppose this is what is confusing Jetpack.

You may need to check that your DNS is configured properly. Also, under Settings > General, confirm that your Site URL and Home URL are filled in correctly and match. Once those are resolved, try reconnecting Jetpack again.

Let us know how that goes.

Thanks for reconnecting Jetpack. I’ve run the debugger and I see a working connection.

With Jetpack, your stats and other information are connected to a unique blog ID. Sometimes, if a site owner was using a development/staging site or a different address when they set up Jetpack, disconnecting or cloning may create a new blog ID. When this happens, it may appear that your stats were lost.

That’s what happened on your site; it previously used a different staging URL and at some point was involved in this kind of “identity crisis”. I have fixed the issue, and you should now be able to see your historical site stats again.

You can learn more about identity crises as well as proper actions to take when you come across our safe mode notice whenever you clone your site for development or testing purposes from our support page.

Hi there,

Thanks for this report. I’ve logged it internally and we’ll take a look.

Let us know if there’s anything else we can help with.

Hi there,

Thanks for contacting Jetpack support.

I’ve checked internally for https://cafelove.org and I see you have subscriptions enabled on Jetpack. However, the form I’m seeing on that page https://cafelove.org/?p=109 is a regular Jetpack contact form rather than a subscription form. That’s why you’re just getting name and email submissions to your email and on the “Feedback” section of your WordPress dashboard.

To correctly add a subscription form to your site, head over to the Appearance → Widgets section of your WP-Admin dashboard and search for the Subscription Form block. When you add that block/widget to your sidebar, you should see a smaller form with just an Email Address field and a Subscribe button. Note that you can also add the form from Appearance → Customize.

Hi there,

Thanks for sharing that error log along with your report. It’s very useful. The first thing to notice is that nowhere in the log is Jetpack mentioned.

The first line there is the most informative:

Uncaught ValueError: Unknown format specifier “C” in /var/www/html/wp-includes/nav-menu-template.php:277

That ValueError was introduced in PHP 8.0 and “is thrown when a value encountered is of correct type, but it cannot be used to continue the operation.”

The line referenced is line 277 of the core WordPress file nav-menu-template.php. On that line, WordPress adds items to the navigation menu using the PHP sprintf function and other plugins can programmatically extend this functionality to add more items to the menu or display it differently.

It appears you’re using this ElementsKit plugin to improve your menu and it’s hooking into the core menu builder using a wrong format specifier. The error in your log mentions “C” which is not one of the format specifiers that can be used with the sprint function (“c” is though).

TL;DR: Going by the log you shared, the ElementsKit plugin is responsible for the error.

I suggest you open a new thread on the plugin support forum and link to this thread in your forum post so that they can assist with this issue. Here’s a link to their support forum for your convenience:

https://www.ads-software.com/support/plugin/elementskit-lite/

Best,

• This reply was modified 2 years, 10 months ago by Daniel.

Hi there,

What scanners did you use to scan your site? I’ve just done a quick scan with Sucuri’s free site check and I found no malware. It’s not an exhaustive scan though but it should have detected any suspicious JavaScript code.

I can say that jetpack-whatsapp is indeed a kind of identifier for our WhatsApp sharing service, so we can take a closer look at this if you contact us via this contact form while mentioning this thread.

Thanks.

Hi there,

Thanks for contacting Jetpack support.

I suppose you’re referring to the WooCommerce PAYCOMET Module. I can’t quite see how Jetpack is interfering and causing that error without having more information.

As a first step, can you please try a wider test for a plugin conflict? In other words, try temporarily deactivating all the site’s plugins except for Jetpack, WooCommerce, and the PAYCOMET module and clear your browser’s cache. Then try finalizing orders again.

If it works, then we’ll know that another plugin is conflicting here. You can re-enable your plugins one by one while trying to finalize orders in between until you find the one causing the conflict.

I’d also recommend reporting what you find after doing that test to the plugin developers on the corresponding support forum:

https://www.ads-software.com/support/plugin/paytpv-for-woocommerce/

Hi there,

Thanks for contacting us. You’re likely seeing that error because the pre-flight connection process to WordPress.com which we use to power many of our services doesn’t finish successfully.

In order to use Jetpack Boost on your site, you need a publicly accessible WordPress site, so there should be no password protection or Coming Soon or Maintenance Mode plugin in use. You also need a publicly accessible XML-RPC file.

You can learn more from our support page focusing on where we answer the question, “What do I need in order to run Jetpack Boost on my site?”.

If you need more help, please let us know your site URL so we can take a closer look.