mvied

If something on the screen isn’t working correctly, there’s generally an error in your browser’s console that will give you some indication as to what’s going on. Post any errors you see there, here.

As for randomly logging you out, you’re going to have to post specific examples of the URL you were on and what URL you went to when you were logged out. WordPress is logging you out, not the plugin. There is probably a reason for it.

This is not a plugin specific problem, my plugin just uses a lot of memory, so it is often the plugin to push people over their limit. You have to increase your memory limit in PHP. Talk to your hosting provider.

2.0 consisted of one file that all the code was in. In 3.0, I rewrote the whole thing to better organize the code base. Your issue is that PHP is not autoloading the other, required files for some reason. The issue is either a problem with the server configuration, or another plugin is conflicting, causing the plugin not to function.

If you can, set up a duplicate test site with the same plugins and run some tests to see if the error occurs when only my plugin is active.

Upgrading from 2.0.4 can sometimes be bumpy. Uninstall 2.0.4 and install the latest version. You can easily secure your entire site by placing ‘/’ as a URL Filter in the current version.

I’m guessing if you look in wp-content/plugins/wordpress-https/lib/ you see WordPressHTTPS.php and inside it there’s code? Just to be sure, lol.

Well, as far as I know there are no problems with the plugin. Unless you actually report errors, they won’t be fixed.

This plugin is so dependenent on the configuration of the server and the WordPress site being used, it’s very hard to test and find bugs.

Force SSL Exclusively does exactly what it describes. Anything not forced to be HTTPS will be redirected to HTTP.

If your SSL Host does not match your Site URL, it will not be possible to log into both HTTPS and HTTP at the same time. That’s why I asked.