guymon13

Thanks for the reply (and my apologies for my double post, not sure what happened there)…

I have considered hiring outside help for this, but besides being a freelancer working on a strict budget, it strikes me as an issue that shouldn’t be shrouded in mystery to everyone else having these types of problems out there. I really hope this isn’t a thing where specialists out there are reading over these types of posts and withholding basic answers that could greatly help the open source community. Seems like I’ve found answers on more complex issues than this before, and this doesn’t strike me as an issue that would warrant some kind of proprietary industry secrets.

Is there any possibility that you could share an example version of the htaccess code(s) that you ended up with? If not, can I hire your nephew? lol

Has anyone actually resolved this issue? I see these posts (and others much like it) are almost a year old now, and I’m not finding proper answers anywhere across the web.

Is this something specific to Bluehost? For some reason I wouldn’t think so… But the code they themselves provide, as others here have described, simply does not work. Adding the other bit of code that actually mentions HTTPS doesn’t appear to fix it either.

Wordpress automatically adds a chunk of <IfModule mod_rewrite.c> code to the htaccess file by default. Do these other pieces of code need to replace that, or be placed within that, or placed separately in a certain order? Is there one set of code to use on the top level htaccess and perhaps something different to use for the subdomain htaccess?…

Can anyone provide a proper, complete sample .htaccess code that will implement our Positive Wildcard SSL on the top level domain, as well as our subdomains?

Many questions with nothing but vague answers anywhere I’ve looked so far. I would venture to guess that most of us using WordPress are more focused on frontend site design and development, and less familiar with the finer details of SSL and htaccess code. It would be great to begin seeing these types of questions actually getting solid answers, and not just lingering on support forums like this for months and years.

Thanks in advance to anyone who can shed some light on this topic.
(edit: reposted because this disappeared for some reason, edited for better detail)

Has anyone actually resolved this issue? I see these posts (and others much like it) are almost a year old now, and I’m not finding proper answers anywhere across the web.

Is this something specific to Bluehost? For some reason I wouldn’t think so… But the code they themselves provide, as others here have described, simply does not work. Adding the other bit of code that actually mentions HTTPS doesn’t appear to fix it either.

Wordpress automatically adds a chunk of <IfModule mod_rewrite.c> code to the htaccess file by default. Do these other pieces of code need to replace that, or be placed within that, or placed separately in a certain order? Is there one set of code to use on the top level htaccess and perhaps something different to use for the subdomain htaccess?…

Can anyone provide a proper, complete sample .htaccess code that will implement our Positive Wildcard SSL on the top level domain, as well as our subdomains?

Many questions with nothing but vague answers anywhere I’ve looked so far. I would venture to guess that most of us using WordPress are more focused on frontend site design and development, and less familiar with the finer details of SSL and htaccess code. It would be great to begin seeing these types of questions actually getting solid answers, and not just lingering on support forums like this for months and years.

Thanks in advance to anyone who can shed some light on this topic.

• This reply was modified 7 years, 9 months ago by guymon13.