<![CDATA[ TinyMCE Doesn't Fully work while Forcing HTTPS - MODX Community Forums]]> https://forums.modx.com/thread/?thread=45815 <![CDATA[Re: TinyMCE Doesn't Fully work while Forcing HTTPS]]> https://forums.modx.com/thread/45815/tinymce-doesn-t-fully-work-while-forcing-https#dis-post-265238 Resource URL: definition in System Configuration > Interface & Features...I needed to add the HTTPS:// protocol

Which brings up a valid question:
How/Where is the Server type declaration ( HTTP or HTTPS radios ) used within MODx?]]>
pixelchutes Dec 15, 2006, 05:14 PM https://forums.modx.com/thread/45815/tinymce-doesn-t-fully-work-while-forcing-https#dis-post-265238
<![CDATA[TinyMCE Doesn't Fully work while Forcing HTTPS]]> https://forums.modx.com/thread/45815/tinymce-doesn-t-fully-work-while-forcing-https#dis-post-265237
	# Force HTTPS
	RewriteCond %{SERVER_PORT} 80
	RewriteRule ^(.*)$ https://www.%{SERVER_NAME}/$1 [R=301,L,QSA]

The problem?

Tiny MCE popups (such as HTML-mode) do not work or fully render. I’m betting that somewhere within TinyMCE it references hard-coded HTTP, or expects a certain response, etc. Unfortunately, I’m not sure.

1. Has anyone else ran into this issue before?

2. Is there a solution that works while still allowing to ensure HTTPS?

1. I am only forcing HTTPS on the root (/) level, not recursive through /manager/, etc
2. I may have been logged in to manager via HTTPS when the issue occurred.
3. I have tested both HTTP and HTTPS logins since, and this issue was not replicated, and appears to be working fine. How weird. I’ll leave this up for a little to see if anyone else has witnessed similar events.]]>
pixelchutes Dec 15, 2006, 04:16 PM https://forums.modx.com/thread/45815/tinymce-doesn-t-fully-work-while-forcing-https#dis-post-265237