Well, it’s supposed to, yes. 🙂
Where your files are and where your WordPress is installed have no bearing on if the plugin works or not.
When you say Shared SSL, do you mean a wildcard SSL that is usable for any subdomains, or a Shared SSL that is provided by your hosting company, or some third party?
If you’re using a wildcard SSL and your site is accessed simply by going to https://demo.invalid.com/ then you shouldn’t have to do anything special for it to work.
On the other hand, if you’re using Shared SSL from a third party, you have to configure the Shared SSL option in the WordPress HTTPS settings. If you’ve already done that, then the plugin may not be accurately detecting HTTPS, and therefore not redirecting your pages.
Sometimes detecting HTTPS with a Shared SSL can be tricky to identify due to the proxying and such that generally goes on with those. The plugin will detect most Shared SSL certs, but I obviously haven’t tested it everywhere.
Let me know and I’m sure we can get it working for you.
Thanks,
Mike
Thread Starter
elfin
(@elfin)
Shared hosting, shared SSL ie. normal site is http://edemo.invalid.com
but the SSL is totally unrelated: https://secure.somewhereelse.com/~USERNAME/
When I get chance I will try from root ie. http://invalid.com
If I get it working for me I can suggest others use it with my plugin 😉
Really the only way I can help is if you give me FTP access to test some other methods of detecting the Shared SSL cert. It would be greatly appreciated. 🙂
If you’d like, you can send me the FTP credentials at mike[at]mvied[dot]com.
hmm i have the same problem…
i have wordpress to a subdomain and https is not working
Rich ‘elfin’ Pedley did you solve this?
Thread Starter
elfin
(@elfin)
No but it was more an issue with my particular set up and requirements.
