Popup Dialog for Link is broken with asset_host about tinymce-rails HOT 7 CLOSED

Unfortunately I don't think this problem is easily solvable, as the issue has to do with cross-domain JavaScript which of course isn't allowed. The TinyMCE docs has some info here: http://www.tinymce.com/wiki.php/How-to_load_TinyMCE_crossdomain

The only "solution" I can currently think of is to ensure that the issue is documented sufficiently. However I am definitely open to other ideas.

from tinymce-rails.

"This will enable the script to be loaded between two sub domains. For example www.mydomain.com can load TinyMCE from scripts.mydomain.com using the above method. We are currently working on a CDN version that will be able to load TinyMCE from any domain."

So from their side, they are working on a solution too. My current approach is set the base tinymce asset directory to my server instead of uploading to CDN. I will try the suggestion of setting document.domain

from tinymce-rails.

@dfguo did you solve this? I'm having the same problem now.

from tinymce-rails.

Just went through this issue and since TinyMCE has it's own initialization process I wouldn't recommend loading the editor off your CDN and instead rendering it out of public/assets.

If you look at the tinymce-assets.rake file, you'll see that the entire vendor directory of the gem is copied over to public/[assets-prefix]. When it goes to precompile it then just throws the digest versions on S3 so then you get load errors and all kinds of Javascript errors since it has trouble finding the files. TinyMCE internally looks for files like "source_editor.js" but on your CDN you'll only have "source_editor-digest.js".

Another issue is the domain and iframing as you've mentioned. For the app I'm working on everything is over https so we can't point to S3 over http(via a custom cname like assets.example.com) since Chrome and most browsers will block js/css because it has trouble verifying the SSL certificate.

To get this setup and so that the preinit.js file doesn't specify the base path as your CDN, create config/initializers/tinymce.rb with the following:

TinyMCE::Rails::Engine.config.tinymce.base = "/assets/tinymce"

And then instead of using <%= tinymce_assets %>(This will load over the asset pipeline), just throw a raw %script tag in your head tag:

<script src='/assets/tinymce.js' type='text/javascript'></script>

If there's an option to use javascript_include_tag without the asset pipeline for a particular asset, I'd love to know.

from tinymce-rails.

@spohlenz I noticed this was closed, does it means that this issue was solved?

from tinymce-rails.

@badosu It should be resolved now with TinyMCE 4. Please open a new issue if you encounter any problems. I haven't found any way to make it work with TinyMCE 3.x but will happily accept PRs if you can get it working.

from tinymce-rails.

@spohlenz Great! Thanks!

from tinymce-rails.