mvied

I know what it would take to implement, I just don’t want to add another checkbox if I don’t have to. I’ll think on it.

I can’t help you configure Cpanel, but the apache vhost needs to be pointed at the exact same folder, not a subfolder. Talk to your hosting provider to see if it’s possible.

So, do you have an issue?

It’s cool, I know what the issue is. I won’t go into to too much detail, but the subdomain check relies on a cURL request and if that fails for some reason, it won’t detect that the SSL Host is a subdomain of the regular host and set cookies appropriately. Some hosts have issues with the cURL request, although most don’t.

I’m working on a new version and this is one thing I’m going to be improving/fixing/removing. I’ll update the topic when I have something you can test.

@jpleas Yes, you have the right idea. Would you mind if I took a look at your setup? I see no reason that configuration shouldn’t work. You can email me at mike[at]mvied[dot]com, if so.

What happens when you just visit https://secure.mydomain.com/?

Is your network really large? My development version has code to try and help alleviate issues when activating on a big network. It’s not perfect yet, but it may help. Let me know.

I’m in the midst of a new version. Could you try the development version and let me know if the issue persists?

Enable debug mode and check the browser’s console. See if it says Subdomain: Yes or No. I could see this being an issue if that says ‘No’.

Look at the cookies being set and check the domain they’re being set on.

Many people want to be logged into both so that when they visited their public site over HTTP, they still had admin features.

You’re actually the first person to ask and like most things that I consider adding to the plugin, I wait until somebody asks for it.

Do you also use Force SSL Exclusively? Perhaps the cookies could be set to secure if both settings were enabled. I think that’s reasonable and I wouldn’t have to add another checkbox to the settings. I like simple. Let me know what you think.

Typically it’s because WordPress doesn’t know how to handle the URL. WordPress maps URLs to post/pages/categories/etc so when the URL is unusual, it can break pretty permalinks. I have code in place to add a URL rewrite rule to WordPress when the SSL Host has a folder path such as /~webviser/ here and it works on some hosts and not on others. I’m not sure why.

Try disabling pretty permalinks.

Alrighty, I’ll update this topic when I have a fix to try. I can’t reproduce it, so I’m just kind of shooting in the dark, haha. Thanks for trying it.

Getting stuck meaning you put in the correct password and nothing happens after the page reloads?

Right click and use Inspect Element on the form. Look at the action URL and see if it’s correct.

Can you check and see if you’re still having issues? I think this was my fault. My server was having some issues and the AJAX widgets pull from it. Just a theory. Let me know.

It’s hard telling. If you want, you can email me at mike[at]mvied[dot]com. I’m available for hire and I’m sure I could fix it in no time. It’s just one of those things that’s kind of hard to troubleshoot/advise from the outside.

First, install the plugin. Then, as it says on the front page: Read the Installation Guide. If after setting up the plugin you are experiencing issues, please check the FAQ. If you are still unable to resolve your issue, come talk to me.