mini.css files seem to be 404

All of a sudden our nav and multiple theme modules aren’t working. We only have one custom module and I removed it but that didn’t help. I’ve checked the child theme’s CSS but no issues. We haven’t touched the backend in months so I’m a bit baffled.

It seems to me that many min.css files are 404 for some reason. The main theme in previewer looks fine.

@TSwisherTOC - this is a bit of a random guess. Based on a problem I had a while back, the ‘minifier’ or whatever it might be called can detect syntax issues in the CSS and refuse to generate a .min file. I coul donly find this issue by running my files through a 3rd party syntax checker.

Why this should happen spontaneously is of course a separate question!

Good luck!

Steve

Thank you for the reponse. I have run all my custom css through VS code I will check the theme but I doubt the theme is an issue since the theme preview looks fine. I will double check though and thanks again.

Thomas

Hi @TSwisherTOC,

Recheck each of your CSS files for any errors. If no errors, then re-publish the files for HubSpot to re-run their minifier.

Thanks. I only have but a few in my child theme. I tried that but it doesn’t seem to have any effect. Very frustrating.

Hi @TSwisherTOC,
Thank you for reaching out to the Community!
And thanks @SteveHTM and @GiantFocal for your help! :heart:
I am sorry to hear about your experience with the mini.css files @TSwisherTOC. I understand how this can be frustrating.
I’d love to put you in touch with other Community Champions to see if there are other options that you can try:
Hi @Anton, @stefen and @sylvain_tirreau do you have other suggestions to help @TSwisherTOC, please?
Have a great weekend and thanks so much!
Best,
Bérangère

Wanted to first say thanks for everyone that responded. I like both of the responses above the problem is the are modules in the theme so I can’t make changes. That got me thinking though how about moving them to the child theme make a change and save. Sure enough that fixed the issue. Funny thing though once and awhile on reload I get this in console log. This doesn’t seem to be affecting anything but it is annoying.