"Bug" in Jetpack (subscription widget)

We’ve made some changes to Jetpack in one of the last versions, Jetpack 3.2, and that file is not added to your site anymore. I would consequently suggest that you update to the most recent version of Jetpack, and flush your site’s cache.

I hope this helps.

Hi Jeremy, thanks for the answer.

Problem is still there.
Along with WP SuperCache I use a plugin called “Better WordPress Minify” that, along with some optimizations (as suggested by w3c rules), moves some link files at the end of the page, to optimize the loading times.

So the plugin moves the file “io/wp-content/plugins/jetpack/modules/subscriptions/subscriptions.css” at the end.

But since the new format is:

<link rel=’stylesheet’ id=’jetpack-subscriptions-group-css’ href=”wp-content/plugins/bwp-minify/min/?f=io/wp-content/plugins/jetpack/modules/subscriptions/subscriptions.css” type=’text/css’ media=’all’/>

I guess it could be the plugin that doesn’t add the correct property?

Disabling the widget or the plugin everything works again.

Have a nice day,
Lock

The problem is that Jetpack doesn’t add this file to your site anymore, not since Jetpack 3.2. Instead it includes one single concatenated file named jetpack.css.

If you’re running the latest version of Jetpack (3.3), could you check your Better WordPress Minify settings and make sure the plugin is up to date with all the different stylesheets loaded on your site?

Let me know if it helps.

I’m sorry if I can’t explain it clearly, I’m not a WP plugin expert and english is not my main language. Here’s what I see:

Everything (WP, Jetpack and Better WP Minify) is up to date.

I deleted all caches (from WP Super Cache and Better WP Minify). The former one (Better WP Minify) automatically detects .JS and .CSS files as you navigate the website pages and, while I see the jetpack.css file you mentioned, I also see the subscriptions.css one (and, too bad, w3c Validator sees it too). ??

It only appears if I drag the “subscriptions (Jetpack): subscribe to blog” (I translated it from italian, I think it sounds more or less like that) widget to the widget (secondary) area. If I disable it then there’s only jetpack.css file and everything is ok.

If I browse Jetpack directory structure I see that a subcriptions.css file do exists in:

“plugins/jetpack/modules/subscriptions” and it’s registered in line 597 of subcripitions.php (that is located one dir level above):

// Enqueue the form’s CSS
wp_register_style( ‘jetpack-subscriptions’, plugins_url( ‘subscriptions/subscriptions.css’, __FILE__ ) );
wp_enqueue_style( ‘jetpack-subscriptions’ );

So it seems there’s still a sort of link between files, and I think that is the problem.

Not being good in understanding WP processes I’ve no idea if this is invoked only in particular cases that are somehow triggered by Better WP Minify.

If you want to check it a bit better you can see the page (in italian language) at:

https://www.lemonskin.net/io/

I’ve left Better WP Minify on and the subscription widget as last one in the right column of the index page.

Many thanks for your help, have a nice day.
Lock

If I browse Jetpack directory structure I see that a subcriptions.css file do exists in:

“plugins/jetpack/modules/subscriptions” and it’s registered in line 597 of subcripitions.php (that is located one dir level above):

Yep, that’s correct. However, that file is then dequeued, and replaced by a concatenated version of your Jetpack CSS here:
https://github.com/Automattic/jetpack/blob/3.3/class.jetpack.php#L5034

That seems to happen properly on your site; the jetpack.css is there, and is handled by Better WP Minify:
https://i.wpne.ws/ZQDU

Better WP Minify, however, seems to add the file again in your footer here:
https://i.wpne.ws/ZPSZ

Could you go to Better WP Minify > Enqueued Files in your dashboard, and make sure the subscriptions.css file is not enqueued there?

Let me know how that goes.

Yes, sure. I excluded it from being processed and the error disappeared.
I didn’t do it earlier because I was thinking that file was added anyway but after your clear explanation I understood Better WP Minify gets confused and mistakenly thinks it’s needed and processes it.

Many thanks, Jeremy. ??

Have a nice day,
Lock