Ray

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

Hi Justin,

AH!!! I see. When I read those instructions, I thought it should be interpreted as, “If you have a newer version of WordPress, use FORCE_SSL_ADMIN. Don’t bother looking below this line.” So, I thought my only option was to keep trying to get FORCE_SSL_ADMIN working (and it isn’t for me…I don’t know why).

I’ll try a plugin option or .htaccess, then and give up on FORCE_SSL_ADMIN.

Thanks a lot for clarifying the instructions on that web page!

Ray

Thank you very much, vizwa, for your suggestions!

I’ve solved my problem! It wasn’t a problem with any of the items on your check list, but it did lead me towards what I should and shouldn’t be looking at.

As it turns out, I was missing “AllowOverride FileInfo” in my web server configuration. Yes, I know it is required in order to make use of .htaccess. So, it was a silly mistake that I only realized after going through the check list here.

The funny thing is, while I was trying to solve my problem yesterday, this line was missing but sometimes, permalinks did work. Also, I have another WordPress instance that is slightly older (4.4) and it seems to be working without this directive. Based on my understanding, it should never work without this in the server configuration.

So, I’m a bit confused… But, with my problem solved, I will have to convince myself that maybe I was day dreaming before or something.

Thank you for your help!