CookingFat69
Forum Replies Created
-
Thanks again KTS915.
In my case, I’ve already previously sent out lots of emails with various “http” links to my website, so I felt that I needed a way to automatically redirect people.
For info, I’ve now used the first piece of code shown in my post above for a couple of days, and so far no members have reported any problems. The other option that I was tempted by (and might use in the future) is a WordPress plugin – for example, the above s2Member Knowledgebase article (link) mentions a couple of plugins, or alternatively the WordPress plugin “Really Simple SSL” (link) appears to have decent reviews.
Thanks again,
SteveHi KTS915,
Thanks very much for your really quick reply 🙂
I did try simply changing the two settings in WordPress (i.e. and not changing the “.htaccess” file), but it resulted in various problems. For example, although doing this changes all of the menu links to “https”, it doesn’t change any of the existing “http” links that I’ve inserted within the pages of the website, and it doesn’t redirect these links to “https”. In other words, it leaves the website in a state where some links (i.e. menu links) go to “https” whereas other links (i.e. existing links within pages) go to “http”. It also caused problems with the s2Member Pro Login Widget – e.g. sometimes this box would show me as not logged in even though I was logged in. Furthermore, when logging in using the “wp-login.php” page, it would then redirect me to the “Membership Options Page” (i.e. rather than to the “Login Welcome Page”). Similarly, when trying to download a restricted file, it would redirect me to the “Membership Options Page”.
For info, I then subsequently added the first piece of code shown in my post above to the “.htaccess” file, and now everything seems ok. For reference, this piece of code is set out by the following s2Member Knowledgebase article …
Implementing SSL (HTTPS) on an s2Member Site
… and appears to have been written by Jason as shown by the following Github page …
Implementing SSL (HTTPS) on an s2Member Site
As the above code appears to be working ok, I’m happy, although I’m still confused as to why the piece of code written by Jason appears to be different to the equivalent pieces of code that I’ve seen on other websites (as shown by the other two examples in my post above). Maybe they’re different ways of achieving the same thing, or maybe one of them is correct and the others are incorrect. Hopefully I’ve picked the “correct” one!
Thanks,
Steve