This may happen if some of the TinyMCE components are being loaded over http. Although testing it here all seem to be https. Can you look at the browser console for the URLs that are not https://? Then can try to figure out why.
-
This reply was modified 9 years, 4 months ago by
Andrew Ozz.
Thread Starter
Ray
(@rwanwork)
Hi Andrew,
Thanks a lot for taking the time to respond to me!
Can I get back to you in 2 weeks? The user of the site has an urgent deadline to meet and would prefer I not touch the site’s settings or do anything that could cause anything to go wrong until after the deadline has passed.
I’ll be sure to follow-up as I was stuck for some time.
Thank you!
Ray
Thread Starter
Ray
(@rwanwork)
Hi Andrew,
I figured out my problem! I wasn’t changing the baseurl from within WordPress but, instead, wanted to just protect the administrator’s page (using URL rewrite rules) with HTTPS. And so, I only added URL rewrite rules for the wp-admin and wp-login directories.
After turning on the browser console and playing around with the settings, I realised that there is content in wp-includes and wp-content that is also loaded. After adding these directories to the URL rewriting rules, the menu items worked again. (Note: I also upgraded my WordPress to 4.7 and TinyMCE to 4.4.3 .)
For what it’s worth, when I changed the baseurl to HTTPS, it took a long time to load. Long enough for users to notice. That’s why I was trying to be selective…but I didn’t realize that TinyMCE wasn’t self-contained within just the administrator’s directory.
In hindsight, I understand why it is this way. I guess that there are some parts of TinyMCE that is also for non-administrators. Thus, these files exist outside of wp-admin and wp-login.
Thank you for your help and sorry for the trouble!
Ray