This plugin is awesome, and one issue holding us back from using it more is that at least with shared SSL situations (ex: bluehost, hostgator), one has to turn off pretty permalinks and instead use the default (ex: yoursite.com/?p=224).
So far the only hunch is to add to your .htaccess:
ErrorDocument 404 /index.php
But this doesn’t seem to work for me, at least not with a blog installed into a subdirectory. As I understand it, WP isn’t processing the permalink structure because it’s not the default installation URL. The ? modifier seems to get around this.
Interestingly, if I use my shared ssl URL structure and only keep it the root directory of the blog, (ex: https://secure.bluehost.com/~username/dev/cms/ ) the page template loads but with a wordpress-processed 404 error message.
If I try to go one level further (https://secure.bluehost.com/~username/dev/cms/apage) then I get a real server 404
Anyway, I figure there are hundreds of us who are effected by this and it would be great for us to solve this problem collectively so we can all benefit from not having to turn on global default permalinks to get it to work with shared SSL.
Would really appreciate hearing from others who are trying to work around this. Thanks!
- The topic ‘[Plugin: WordPress HTTPS (SSL)] Shared SSL & non-default Permalinks: Let's solve this!’ is closed to new replies.