Everything is working fine when i run the site in debug mode.
But when I turn of debug the TinyMCE editor stops working. The reason is that the TinyMCE scripts for themes and plugins are now loaded from a different path.
In debug mode they load from: /umbraco/lib/tinymce/themes/modern/theme.min.js
But in release they load from: /sb/themes/modern/theme.js
which results in 404 since it doesn't exists.
If I understand things correctly it seems like Smidge is causing this. But I cannot understand how this works or why this happens. Or how I can stop Smidge from interfering.
I've read that you can specify bundling options in the manifest file for the plugin but it doesn't seem to work for me.
Problem with Custom TinyMCE editor and Smidge in production
Problem with Custom TinyMCE editor and Smidge in production
Hi,
I have created a custom property editor with a TinyMCE editor.
Everything is working fine when i run the site in debug mode. But when I turn of debug the TinyMCE editor stops working. The reason is that the TinyMCE scripts for themes and plugins are now loaded from a different path.
In debug mode they load from: /umbraco/lib/tinymce/themes/modern/theme.min.js
But in release they load from: /sb/themes/modern/theme.js which results in 404 since it doesn't exists.
If I understand things correctly it seems like Smidge is causing this. But I cannot understand how this works or why this happens. Or how I can stop Smidge from interfering.
I've read that you can specify bundling options in the manifest file for the plugin but it doesn't seem to work for me.
Anyone else experienced this problem?
hey andreas,
in production i would not suggest using "bundleOptions": "None" in my angular projects i used to show RTE like
I'm still having problems with this. Is there some way to resolve script paths in a custom property editor?
is working on a reply...