MIME type skin error about tinymce-angular

[vctormb]

I fixed it partly with tinymce-angular v5.0.3 by setting the skin_url of the editor and copying the files in the assets folder.

So my markup looks like this:

<editor class="u-spacer--small" id="answerEditor" [init]="{skin_url: 'assets/skins/ui/oxide'}" .

Now I still get this error because the silver theme still wants to load the 'skins/content/default/content.css' file ...

Try to put the content like this:
content_css: assets/skins/ui/oxide/content.min.css

I'm creating a library, so I'll need to document that the developer will need to navigate inside my node_modules, copy the skin and paste inside his public folder. That's not good but unfortunately I guess that's the only option.

[janvanuytrecht]

Great that worked, thanks! Yes, it seems in Angular the only way is to copy the files unfortunately.

…

On 2 Apr 2019, at 13:38, Victor Martins ***@***.***> wrote: I fixed it partly with tinymce-angular v5.0.3 by setting the skin_url of the editor and copying the files in the assets folder. So my markup looks like this: <editor class="u-spacer--small" id="answerEditor" [init]="{skin_url: 'assets/skins/ui/oxide'}" . Now I still get this error because the silver theme still wants to load the 'skins/content/default/content.css' file ... Try to put the content like this: content_css: assets/skins/ui/oxide/content.min.css I'm creating a library, so I'll need to document that the developer will need to navigate inside my node_modules, copy the skin and paste inside his public folder. That's not good but unfortunately I guess that's the only option. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#30 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABd0qoQ8-MF7DULGMeSpYcytgIe_mPRCks5vc0EbgaJpZM4WDehT>.

[janvanuytrecht]

I fixed it partly with tinymce-angular v5.0.3 by setting the skin_url of the editor and copying the files in the assets folder.

So my markup looks like this:

<editor class="u-spacer--small" id="answerEditor" [init]="{skin_url: 'assets/skins/ui/oxide'}" .

Now I still get this error because the silver theme still wants to load the 'skins/content/default/content.css' file ...

[fyrkant]

How are you loading the skin, using the skin_url property in the config?

[fyrkant]

Closing due to inactivity.

[Raiper34]

Exact same issue here, I defined skins in angular cli config under styles, same as for example plugins (but plugins are in scripts)...

[wouterda]

Same issue here. Only defining the skin in the "tinymce.init" method through "skin_url".
All other css is loading just fine.

[sasos90]

So whats the conclusion? Any solutions here?

[vctormb]

I'm facing this issue too.

I'm using React.. so I'm importing the css file inside my component because if I pass the skin_url inside the init object, it will not work. Btw, even if I import the css it still shows the 404 error to the css files, but the style works.

[92Arbiter]

If you use the following syntax, the copying is executed automatically:
{ "glob": "**/*", "input": "node_modules/tinymce", "output": "/tinymce/" }

You can find more info at the following link:
https://angular.io/guide/workspace-config#assets-configuration