Refused to apply style from 'https://abc.outsystemsenterprise.com/Test/css/Online_TH.OnlineTheme.extra.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Hi Sugosh,
I suppose this is an error message you encountered, but it is unclear to me what you did, where this shows, or even what question you want us to answer. Please give more details.
I am creating reactive application. While creating an application I have created custom theme say "demo1", however there are many major changes in the "Demo1" theme so I have designed new theme with name as "demo2". Then I have remove the dependency from "Demo1" and added dependency of "Demo2". After theme change I am experiencing this issue. facing this error post change in theme dependency.
Try the URL ("https://abc.outsystemsenterprise.com/Test/css/Online_TH.OnlineTheme.extra.css ") in the browser. I bet you get a 404 error.
That said, to fix it make sure all producers are properly published. Refresh references in the consumers, and publish them. Check your browser's developer tools to see what CSS it tries to load.
Hi,
Like Kilian wrote, we need more details.
In a quick search, I found out that it seems to be an error that you obtain in browser DevTools, and it's somehow related with your CSS libraries/files (I'm guessing by the content of the solutions that I found in the Internet).
I can let you here the links for you to take a look, but the best is to give us more context and details about what you're doing (the links aren't Outsystems related, so, maybe not so easy to match with your problem).
https://stackoverflow.com/questions/49406057/refused-to-apply-style-from-because-its-mime-type-text-html-is-not-a-supp
https://stackoverflow.com/questions/48248832/stylesheet-not-loaded-because-of-mime-type
Hope this can help.
Best regards,
Ricardo Pereira
Ah, yes, probably a 404 error page is returned. Makes sense.
I had a similar issue when reshuffling modules/themes to common modules and it seems that if my Theme is referencing a font via URL it cannot be cached and that is causing the issue.
Once I downloaded the font, added it as a resource, referenced it from the deployed location, republished, and updated all consumers, the issue is resolved.
Just wanted to pop in here and note that I was able to solve the issue by upgrading OutSystems UI and then using a solution to do a full recompile of the app I was having trouble with.