JetPack loads dashicons.css in frontend

Hi there,

The dashicons.min.css is a core WordPress file being loaded from the wp-includes folder. It’s not Jetpack loading it.

If you’re referring to something else or if I misunderstood your question please let me know more about it so I can further assist you.

Yes, I know it is a file from the core, but several modules of JetPack use it on the frontend. The problem is that from last update, it is loaded even if there are no active modules that need that file.

I’ve tried to deactivate JetPack entirely as we. If I deactivate JetPack, dashicons.min.css file is no loaded in the frontend. If activate JetPack again, dashicons.min.css appears again in the frontend.

• This reply was modified 6 years, 4 months ago by cybmeta.

@cybmeta

The problem is that from last update, it is loaded even if there are no active modules that need that file.

Can you provide the address of your site?

If you want to reply privately, you can do so here:

https://jetpack.me/contact-support/

Thank you.

Matt’s own site loads the file.

However archive of his page doesn’t show it. See: https://web.archive.org/web/20180430034250/https://ma.tt/

I think it’s because some file using dashicons as a dependency doesn’t get dequeued properly.

@superpoincare

When you reply with the address of your site, publicly or privately, let us know, and we will be glad to further assist you with this.

I’m trying to contact privately but https://jetpack.me/contact-support/ keeps displaying the message “You are not logged in” even after I correctly log in. After login, I can access to any private part of jetpack.me except to the support’s form. Not sure what happens, I’ve used the support form several times before. Do you have any problem in your sie? The username is the same ad here (cybmeta).

• This reply was modified 6 years, 4 months ago by cybmeta.

Finally I manage to use the support contact form vía https://jetpack.com/contact-support/
The address you posted is not working (https://jetpack.me/contact-support/).

@cybmeta

We’ve received your private inquiry and you should hear from us soon.

Thank you for your patience.

pmciano,

Sorry about that but I have dequeued the script so I didn’t know how to show that. I’ll try to set a dummy site maybe. But if this issue raised by cybmeta is addressed, please let us know.

@ramanan – We will and please let us know if you come up with anything during your testing.

@cybmeta @superpoincare

We were able to get clarification from our developers on the behavior @cybmeta identified and an issue has been opened, which you can track here:

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

This should be addressed in a future update.

@cybmeta Thank you for bringing this to our attention!

Think I have identified where it comes from:

https://github.com/Automattic/jetpack/issues/9913#issuecomment-404958728

It’s possible and now that our developers know this issue, they will release a fix in a future update.

Hi,
when this issue will be solved?