Magento 2.2 refused to apply stylesheet
On our Magento 2.2.2 based website we are setting up, we are getting the below 2 error messages (in google console).
I have seen only one other post on the site about this issue and based on what I have read made sure the .htaccess file is in the pub/static folder I also changed the file ownership and also. The file permissions to 777 recursively.
However, still getting the same error?
Any suggestions?
Refused to apply style from '/pub/static/frontend/Smartwave/porto_child/en_US/css/styles-l.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from '/pub/static/frontend/Smartwave/porto_child/en_US/css/styles-m.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
magento2.2
edited 8 mins ago
magefms
1,9271425
asked May 8 '18 at 16:04
JayreisJayreis
338832
add a comment |
On our Magento 2.2.2 based website we are setting up, we are getting the below 2 error messages (in google console).
I have seen only one other post on the site about this issue and based on what I have read made sure the .htaccess file is in the pub/static folder I also changed the file ownership and also. The file permissions to 777 recursively.
However, still getting the same error?
Any suggestions?
Refused to apply style from '/pub/static/frontend/Smartwave/porto_child/en_US/css/styles-l.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from '/pub/static/frontend/Smartwave/porto_child/en_US/css/styles-m.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
magento2.2
edited 8 mins ago
magefms
1,9271425
asked May 8 '18 at 16:04
JayreisJayreis
338832
add a comment |
On our Magento 2.2.2 based website we are setting up, we are getting the below 2 error messages (in google console).
I have seen only one other post on the site about this issue and based on what I have read made sure the .htaccess file is in the pub/static folder I also changed the file ownership and also. The file permissions to 777 recursively.
However, still getting the same error?
Any suggestions?
Refused to apply style from '/pub/static/frontend/Smartwave/porto_child/en_US/css/styles-l.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from '/pub/static/frontend/Smartwave/porto_child/en_US/css/styles-m.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
magento2.2
edited 8 mins ago
magefms
1,9271425
asked May 8 '18 at 16:04
JayreisJayreis
338832
On our Magento 2.2.2 based website we are setting up, we are getting the below 2 error messages (in google console).
I have seen only one other post on the site about this issue and based on what I have read made sure the .htaccess file is in the pub/static folder I also changed the file ownership and also. The file permissions to 777 recursively.
However, still getting the same error?
Any suggestions?
Refused to apply style from '/pub/static/frontend/Smartwave/porto_child/en_US/css/styles-l.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
Refused to apply style from '/pub/static/frontend/Smartwave/porto_child/en_US/css/styles-m.css' because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
magento2.2
magento2.2
edited 8 mins ago
magefms
1,9271425
asked May 8 '18 at 16:04
JayreisJayreis
338832
edited 8 mins ago
magefms
1,9271425
asked May 8 '18 at 16:04
JayreisJayreis
338832
edited 8 mins ago
magefms
1,9271425
edited 8 mins ago
magefms
1,9271425
edited 8 mins ago
magefms
1,9271425
1,9271425
asked May 8 '18 at 16:04
JayreisJayreis
338832
asked May 8 '18 at 16:04
JayreisJayreis
338832
asked May 8 '18 at 16:04
JayreisJayreis
338832
338832
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It seems that your css hasn't been deployed.
its MIME type ('text/html')
indicates that it's (probably) a 404. Have you run setup:static-content:deploy?
answered May 8 '18 at 16:33
Cold FridgeCold Fridge
1337
The site is in developer mode so deploy is not needed?? However you are right I don't see the files at the above path. Maybe i should just download them and upload them to the above path?
– Jayreis
May 8 '18 at 16:38
You can't download the files, they have to be deployed. Since your path indicates it's a third-party time, you'd be better served with doing a force deploy (setup:static-content:deploy -f) so that the CSS files are generated.
– Cold Fridge
May 8 '18 at 22:34
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f225195%2fmagento-2-2-refused-to-apply-stylesheet%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It seems that your css hasn't been deployed.
its MIME type ('text/html')
indicates that it's (probably) a 404. Have you run setup:static-content:deploy?
answered May 8 '18 at 16:33
Cold FridgeCold Fridge
1337
The site is in developer mode so deploy is not needed?? However you are right I don't see the files at the above path. Maybe i should just download them and upload them to the above path?
– Jayreis
May 8 '18 at 16:38
You can't download the files, they have to be deployed. Since your path indicates it's a third-party time, you'd be better served with doing a force deploy (setup:static-content:deploy -f) so that the CSS files are generated.
– Cold Fridge
May 8 '18 at 22:34
add a comment |
It seems that your css hasn't been deployed.
its MIME type ('text/html')
indicates that it's (probably) a 404. Have you run setup:static-content:deploy?
answered May 8 '18 at 16:33
Cold FridgeCold Fridge
1337
The site is in developer mode so deploy is not needed?? However you are right I don't see the files at the above path. Maybe i should just download them and upload them to the above path?
– Jayreis
May 8 '18 at 16:38
You can't download the files, they have to be deployed. Since your path indicates it's a third-party time, you'd be better served with doing a force deploy (setup:static-content:deploy -f) so that the CSS files are generated.
– Cold Fridge
May 8 '18 at 22:34
add a comment |
It seems that your css hasn't been deployed.
its MIME type ('text/html')
indicates that it's (probably) a 404. Have you run setup:static-content:deploy?
answered May 8 '18 at 16:33
Cold FridgeCold Fridge
1337
It seems that your css hasn't been deployed.
its MIME type ('text/html')
indicates that it's (probably) a 404. Have you run setup:static-content:deploy?
answered May 8 '18 at 16:33
Cold FridgeCold Fridge
1337
answered May 8 '18 at 16:33
Cold FridgeCold Fridge
1337
answered May 8 '18 at 16:33
Cold FridgeCold Fridge
1337
answered May 8 '18 at 16:33
Cold FridgeCold Fridge
1337
1337
The site is in developer mode so deploy is not needed?? However you are right I don't see the files at the above path. Maybe i should just download them and upload them to the above path?
– Jayreis
May 8 '18 at 16:38
You can't download the files, they have to be deployed. Since your path indicates it's a third-party time, you'd be better served with doing a force deploy (setup:static-content:deploy -f) so that the CSS files are generated.
– Cold Fridge
May 8 '18 at 22:34
add a comment |
The site is in developer mode so deploy is not needed?? However you are right I don't see the files at the above path. Maybe i should just download them and upload them to the above path?
– Jayreis
May 8 '18 at 16:38
You can't download the files, they have to be deployed. Since your path indicates it's a third-party time, you'd be better served with doing a force deploy (setup:static-content:deploy -f) so that the CSS files are generated.
– Cold Fridge
May 8 '18 at 22:34
The site is in developer mode so deploy is not needed?? However you are right I don't see the files at the above path. Maybe i should just download them and upload them to the above path?
– Jayreis
May 8 '18 at 16:38
The site is in developer mode so deploy is not needed?? However you are right I don't see the files at the above path. Maybe i should just download them and upload them to the above path?
– Jayreis
May 8 '18 at 16:38
You can't download the files, they have to be deployed. Since your path indicates it's a third-party time, you'd be better served with doing a force deploy (setup:static-content:deploy -f) so that the CSS files are generated.
– Cold Fridge
May 8 '18 at 22:34
You can't download the files, they have to be deployed. Since your path indicates it's a third-party time, you'd be better served with doing a force deploy (setup:static-content:deploy -f) so that the CSS files are generated.
– Cold Fridge
May 8 '18 at 22:34
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f225195%2fmagento-2-2-refused-to-apply-stylesheet%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
