mvied

No worries. There will be a corresponding error in your Apache error log. I’ll need to know what that error is to move forward.

I don’t understand why you’d alter your permalinks like that. If you want to use /blog/, then put /blog/ on your Site URL. I doubt I’ll have this fixed anytime soon unless someone can convince me that changing your permalink structure in this manner is a good idea.

You’re assuming my plugin is to blame. It’s more likely you’re just hitting PHP’s memory limit and you need to talk to your hosting provider about increasing it. I can’t really say since you didn’t give any detail.

This should be fixed in the development version. Could you try and let me know?

Your site is behind a coming soon page. Are you asking about securing that page or another page? The plugin does not appear to even be enabled as far as I can tell.

The plugin’s primary goal is to fix insecure elements. Changing your Site URL is completely unnecessary. There is no reason that would fix more elements unless you’re using a poorly written plugin. If that’s the case, it’s more worthwhile to remove or replace that plugin rather than securing the whole site. HTTPS makes your site slower due to the encryption/decryption process. If you don’t need the whole site to be secure, don’t do it.

Well, that doesn’t make any sense. Lol.

If the element is hosted locally and you’re on a secure page, they should always be changed to HTTPS, no exceptions. The folder it’s in doesn’t matter.

Are you saying that your login page is showing up with insecure items? The intent of the plugin is to fix them, but you have to manually fix what it can’t fix.

Sure, I could add it. Nobody’s asked is really the only reason it’s not there.

Upon further inspection, FORCE_SSL_ADMIN is the only option that conflicts with the plugin anyway. I’ll just remove the warning for FORCE_SSL_LOGIN.