mvied

That error is generated by your SSL Certificate. It’s not an issue with the plugin.

The FAQ serves as documentation. If it is not sufficient, start a support topic.

Start a new topic and describe your issue in detail. What’s occurring, what you’ve tried, what you’re trying to do, what settings you enabled, what steps you took, etc.

I can not, but it’s not too terribly complicated. HTTPS stands for HTTP + SSL. It’s identical to HTTP; the only exception being that the data transferred between the server and the client is encrypted. With a standard HTTP connection, the packets could potentially be sniffed for sensitive information. HTTPS is a tiny bit slower than standard HTTP due to the encryption/decryption process that has to take place, but is more secure.

In order to use HTTPS, you have to buy an SSL certificate. SSL certificates have an encryption strength, such as 256-bit, which determines how strong the encryption is. The stronger the encryption, the more secure it is. An SSL certificate is issued by a Certificate Authority. The certificate contains information about the website and server the certificate is for. The primary purpose of the certificate is to verify that the domain specified in the browser’s address bar is securely connecting to the correct server. This prevents hackers from hijacking DNS records and directing the domain name to another server, among other things.

I may be able to answer your questions, but that’s a basic overview of what’s going on.

I don’t see any reason that the plugin should be using that much memory just to set settings on multiple blogs. The code I’m using is pretty straight forward, so I’m not sure what’s going on. I’ll set up some tests on my site and see what I can figure out. Thanks for the feedback.

I fixed the issue in 3.2.3. I had other users that reported the same issue.

And what if you go to https://mysite.com/test1 without the plugin enabled?

You probably enabled the reset and never commented it back out again.