Hi Todd,
Thank you for using Paid Memberships Pro, I’m really sorry for the issue you are facing with this.
We are currently investigating this issue and I will revert as soon as I have some feedback from our dev team.
Thank you for your patience and understanding.
Hi Todd,
Would you mind telling me what Paid Memberships Pro add ons you are using on your multisite?
As I have tested this solely with Paid Memberships Pro (core) and when I manually created a subsite, it first loaded with HTTPS but did not force HTTPS and I simply removed it from the URL when browsing the site.
I did notice that when I clicked ‘Visit’ from the WordPress dashboard it prepended HTTPS but as mentioned I simply removed it from the URL and it wasn’t forced to rewrite to HTTPS – this didn’t happen when PMPro was activated.
-
This reply was modified 8 years, 9 months ago by
Andrew Lima.
-
This reply was modified 8 years, 9 months ago by
Andrew Lima.
-
This reply was modified 8 years, 9 months ago by
Andrew Lima.
With Paid Memberships Pro activated, go to the Network Admin -> Sites -> Add New
via a secure (https) URL and create a site.
After the site is created, click to Edit the site.
Go to the Settings screen. Check the “Home” URL.
In my tests, with PMPro (core) activated, the “Home” URL has https as the beginning, but the “Siteurl” URL has http. This is not default behavior for WordPress. The Home URL should not be affected by the URL the site was created from.
In testing the same process, but with PMPro deactivated, everything is http, which is default WP behavior and the desired result.
I could get into all the reasons why this is creating problems and why changing the URL in the address bar isn’t a sufficient solution (and how it has cost me weeks of time, lots of unnecessary customer support, and lost sales), but I don’t want to distract from the issue, which is that the plugin is changing the default WP behavior in this regard and should not be, so something is wrong and needs to be addressed.
I’m using quite a few add-ons, but as I mentioned, I tested with all of those deactivated and only the Paid Memberships Pro (core) plugin activated and the problem still occurs. So it’s not related to add-ons, but the core plugin. If you need the list of add-ons I can provide it, but again, the problem happens with those all deactivated, so I don’t think it’s relevant and I don’t want to distract from the real issue.
Thanks,
Todd
Hi, it’s been a month. Any update on this?
I have asked Jason, lead developer of Paid Memberships Pro, to work with through this.
I’m really sorry for the delayed response regarding this @toddheitner.
Please feel free to open an issue on our GitHub repo – https://github.com/strangerstudios/paid-memberships-pro/issues
OK, I’d really appreciate the help.
I just posted the issue on GitHub:
https://github.com/strangerstudios/paid-memberships-pro/issues/535
Thanks,
Todd
Thanks for this Todd, we will continue to discuss this issue on the GitHub issue.