Originally Posted by
stitchnkitty
TY so much for your advise... The subsite(windflowergrove ) is an essential site to support a craft business but does not generate much income to move to its own account, So I placed it in with the stitchnframe account. the hopeful plan is to continue to accept orders on the subsite where it is at, this is where it has been and where I would like to keep it. In the past it has had a https but with this upgrade, I have somehow lost it- maybe my codeing is not correct somewhere.. host is bluehost.
Ahha, so perhaps what you had before was something like this in your includes/configure.php:
Code:
define(HTTP_SERVER, 'http://windflowergrove.com');
define(HTTPS_SERVER, 'https://www.stitchnkitty.com/windflowergrove');
This way, the single ssl certificate which was good for the main site, would be used because the "secondary" site is located in the structure of the primary site with the primary site having a valid ssl. Does sort of look "fishy" possibly because there is a sort of redirect/url change, but that also depends on the visitor paying that much attention when transitioning though returning to a non-https page via link on the page leads to a consistent operation. (ie. Not receiving broken links and navigational links are consistently generated and the pages that ought to be provided via encryption are done so...
There is a slight alternative to the above defines, but seems that the consensus has been to use the sub-directory in the HTTPS_SERVER part if it doesn't "exist" in the HTTP_SERVER side to basically prevent software issues of incorrectly written plugins.
Bookmarks