Resource interpreted as Stylesheet but transferred with MIME type text/html

Also, where in your code do you add the rel=”stylesheet” attribute? That’s a required field as it specifies the relationship between the current document and the linked document.

Thanks!

@demaier – We have no other reports of a problem with the implementation of Font Awesome you are describing. As to the rel=”stylesheet”, for what file are you noting this as an issue as this is generated via the enqueue operations when adding stylesheets to a site in WordPress.

Thanks!

– Cais.

@imagely I believe everything is ok with the rel="stylesheet" I just checked the source code of my website and the line for what NextGEN gallery has added we have rel="stylesheet". However, we are still receiving the warning when editing anything on our WordPress.

Resource interpreted as Stylesheet but transferred with MIME type text/html: "https://ourdomain.org/?ngg_serve_fontawesome_css=1&wp-mce-4603-20170530".
k @ wp-tinymce.php?c=1&ver=4603-20170530:5
(anonymous) @ wp-tinymce.php?c=1&ver=4603-20170530:5
e @ wp-tinymce.php?c=1&ver=4603-20170530:4
(anonymous) @ wp-tinymce.php?c=1&ver=4603-20170530:4
l @ wp-tinymce.php?c=1&ver=4603-20170530:4
(anonymous) @ wp-tinymce.php?c=1&ver=4603-20170530:4
e @ wp-tinymce.php?c=1&ver=4603-20170530:4
q @ wp-tinymce.php?c=1&ver=4603-20170530:5
y @ wp-tinymce.php?c=1&ver=4603-20170530:14
q @ wp-tinymce.php?c=1&ver=4603-20170530:14
(anonymous) @ wp-tinymce.php?c=1&ver=4603-20170530:14
(anonymous) @ wp-tinymce.php?c=1&ver=4603-20170530:5
b @ wp-tinymce.php?c=1&ver=4603-20170530:3
r @ wp-tinymce.php?c=1&ver=4603-20170530:5
l.(anonymous function).l.(anonymous function).l.(anonymous function).l.(anonymous function) @ wp-tinymce.php?c=1&ver=4603-20170530:5
f @ wp-tinymce.php?c=1&ver=4603-20170530:5

I also see the following included in the enqueue:

<link rel='stylesheet' id='fontawesome-css' href='https://ourdomain.org/?ngg_serve_fontawesome_css=1&ver=4.6.1' media='all' />

However, the following URL: https://ourdomain.org/?ngg_serve_fontawesome_css=1&ver=4.6.1 doesn’t seem to load anything. I’m also not sure how Imagely wrote that portion that loads Font Awesome in the admin area. (https://github.com/crowdfavorite-mirrors/wp-nextgen-gallery/blob/master/products/photocrati_nextgen/modules/nextgen_gallery_display/module.nextgen_gallery_display.php)

Shouldn’t this URL take you to a CSS file for Font Awesome?

Thanks.

@demaier – My apologies for not noticing this earlier, our official development repository is here: https://bitbucket.org/photocrati/nextgen-gallery

If you are using the version from the repository you are referencing then I would recommend you use the current release of NextGEN Gallery versus what appears to be an outdated copy to see if the issue you are seeing persists.

Thanks!

– Cais.

Hi there,

It seems the section that I mentioned for the module.nextgen_gallery_display.php file is the same on the old and new repositories.

I still have that issue and I have no clue what is causing it.

This is the file on the new repository (line 197):

https://bitbucket.org/photocrati/nextgen-gallery/src/106b3b3689185bd72da5d853a3512b39c08aa790/products/photocrati_nextgen/modules/nextgen_gallery_display/module.nextgen_gallery_display.php?at=default&fileviewer=file-view-default

Any assistance is appreciated. Thank you.

@demaier – Have you tried deactivating all of your plugins, clearing your browser cache (and site caches if you are using a caching plugin), then reactivating the NextGEN plugin?

If this fixes the problem then it was likely one of the deactivated plugins that was causing an issue. Now, retrace your steps activating each plugin and re-checking to see if the problem returns. If it does then that last activated plugin was probably the one. Keep reactivating and in most cases it is also best to keep checking after each plugin, sometimes there may be more than one plugin on a site that will create an issue. If you do find one (or more) plugins causing this problem we would greatly appreciate your feedback on them so the developers may address them as soon as they can.

Also to note, in rare cases it may be the theme itself that is causing a conflict so while you have just the NextGEN plugin activated you might consider temporarily switching to one of the default WordPress Twenty series themes and see if this corrects the issue as well.

If the problem still persists after all of this we would still want to know, even more so, as we will still want to sort out the issue and may need additional details.

Thanks!

– Cais.