So from:
https://forums.modx.com/thread/97694/support-comments-for-tinymcewrapper?page=45#dis-post-553723
I had this note in there (which, as it appears, is very serious!!!)
content_css: "css/style.css", // must exist/be accurate/contain said classes/ and, preferably local CSS file [
The reason is, I quote:
It can't import cross domain on some browsers. So the URL needs to be local.
And https and http, and www and non-www means yuugge non-same difference (apparently!)
If your MODX config is forced to use
https and no
www you access your manager from:
www.example.com/manager
content_css : "/css/styles.user2.css", // translates to https://example.com/css/styles.user2.css
content_css : "https://www.example.com/css/styles.user2.css",
content_css : "[[++base_url]]css/styles.user2.css", // translates to /en/css/styles.user2.css (forced to https)
All the above will fail.
use this instead
content_css : "http://www.example.com/css/styles.user2.css",
Basically, if your MODX spits out
https://example.com/ for
[[++site_url]]
then make sure your htaccess prevents any kind of access to www.example, http:// ... etc
#Force non-www:
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.example\.com [NC]
RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]
This www and non-www used to affect SEO rating, as per duplication fears or something like that.
And yes, as BobRay said, session is not carried over, and you will run into this same problem on another more ruinous level in future.
Cure that htaccess issue right away!
Your site should not be allowed http.example or
http://www.example or www.example