Issue: Stripe Pro-Forms (both Signup and Modification) fail to recognize logged-in users or load Stripe fields on Windows 7, specifically when the cycle is set to Monthly ( rt="M" , rp="1" ).
The Paradox:
- Quarterly/Yearly forms: Work perfectly on the same machines/browsers.
- Monthly forms: Act as if the user is logged out (no pre-filled data) and Stripe fields fail.
The Fix: The issue is resolved only by adding the custom field s2member_force_ssl = yes to the specific page.
Conclusion: There seems to be a discrepancy in how s2Member handles session cookies/headers for Monthly terms compared to longer terms. On legacy systems like Windows 7, this prevents the session from being passed to the Stripe form unless SSL is strictly forced via s2Member’s internal settings.
Please investigate why term length affects session recognition/cookie security.
