1. Home
  2. Development
  3. editor MIME Type error

editor MIME Type error

Hany Bonyadi, modified 7 Years ago.
editor MIME Type error
New Member Posts: 13 Join Date: 8/20/12 Recent Posts
Hi,

in Liferay 7 CE GA6, wysiwyg editor (ckeditor or alloyeditor) works fine when user default language is English ,but when i change default language of portal instance and default language of user for example to Persian(fa_IR) , sign out then login, editor not loaded completely. ckeditor remain in visibility hidden and without css also alloyeditor not show plus icon and inline toolbar.
In Chrome browser console error:
[indent]- Refused to apply style from ''http://x.x.x.x/o/frontend-editor-ckeditor-web/ckeditor/skins/moono-lisa/editor.css?t=HA3N'' because its MIME type ('') is not a supported stylesheet MIME type, and strict MIME checking is enabled.[/indent]

and in Firefox no console error but in network tab of inspector:
[indent]- file 'http://x.x.x.x/o/frontend-editor-ckeditor-web/ckeditor/skins/moono-lisa/editor_gecko.css?t=HA3N' have Type:'application/x-unknown-content-type' and not transferred[/indent]

if i add /en in beginning of url in firefox it show editor but in chrome at all.

any help would be appreciated
thumbnail
Nader Jafari, modified 6 Years ago.
RE: editor MIME Type error
Junior Member Posts: 84 Join Date: 8/24/11 Recent Posts
Hi guys

i have same issue in liferay 7.1.2 GA3 when i choose persian langauge and CKeditor as my editor in knowlagebase portlet , bellow message appears in firefox/chrome console :

Refused to apply style from 'http://localhost:8080/o/frontend-editor-ckeditor-web/ckeditor/skins/moono-lisa/editor.css?t=IAH0' because its MIME type ('') is not a supported stylesheet MIME type, and strict MIME checking is enabled.
thumbnail
Nader Jafari, modified 6 Years ago.
RE: editor MIME Type error
Junior Member Posts: 84 Join Date: 8/24/11 Recent Posts
I created an issue for this in jira : LPS-94439
thumbnail
Nader Jafari, modified 6 Years ago.
RE: editor MIME Type error
Junior Member Posts: 84 Join Date: 8/24/11 Recent Posts
we temporary resolved this issue by adding bellow line in portal-ext.properties :
http.header.secure.x.content.type.options.urls.excludes=/o/frontend-editor-ckeditor-web/ckeditor/