latest stable versions: v150827 (changelog)

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

SSL preventing specific page/post purchases

Home Forums Community Forum SSL preventing specific page/post purchases

Tagged: ,

This topic contains 5 replies, has 2 voices. Last updated by  Cristián Lávaque 4 years, 7 months ago.

Topic Author Topic
Posted: Monday May 21st, 2012 at 6:15 pm #14108

I’m using the WP plugin: WP HTTPS (http://mvied.com/projects/wordpress-https/)

The plugin allows selective use https. When I force SSL on the page where specific post/page access is purchased, the payment goes through (to PayPal) but the user isn’t granted access to the post/page. Also, the automated email (with the special URL) doesn’t get sent. When I remove the HTTPS for that page, everything works.

Any tips on why this is happening? I’ve done some digging through the forum and I see this is a common problem. Is there a specific HTTPS plugin / configuration that you recommend?

Thanks!

List Of Topic Replies

Viewing 5 replies - 1 through 5 (of 5 total)
Author Replies
Author Replies
Posted: Tuesday May 22nd, 2012 at 9:07 pm #14224

Hi Brett.

Instead of using that plugin, could you try using the s2Member custom field to force SSL in a page? It’s explained here: Pre Sale FAQs » Is WordPress® compatible with SSL enabled?

I hope it helps. :)

Posted: Wednesday May 23rd, 2012 at 10:26 am #14329

Thanks Cristián,
I tried it using s2member_force_ssl instead of the plugin and it didn’t work. However, I want to make sure I did it correctly. Here’s how my set is (which doesn’t work):

My site url is http. I added s2member_force_ssl = true for the specific post/page that I’m selling. The checkout page appears with https (so far so good), but when I try to enter payment info into the form, it returns the error code listed above.

I also tried it by adding s2member_force_ssl = true to the checkout page (where the user is redirected to access the post they haven’t yet purchased. This didn’t work either.

Any more suggestions?
=e

Posted: Wednesday May 23rd, 2012 at 10:41 am #14332

UPDATE!
It worked once I removed the plugin!
Thanks!

Posted: Wednesday May 23rd, 2012 at 12:39 pm #14340

I have one remaining issue: on my local development installation I’m not using SSL at all and I’m getting the same error message. I’m not using the custom fields and my paypal credentials are sandbox. Should this work normally?

Posted: Thursday May 24th, 2012 at 4:30 am #14430

I don’t know, local and sandbox is not something I’ve tried.

I recommend you using the real PayPal service with 1 cent transactions to test the actual service. Live and sandbox have slight differences, and it’s not worth debugging the sandbox problems that your customer would not have anyway.

I hope that helps. :)

Viewing 5 replies - 1 through 5 (of 5 total)

This topic is closed to new replies. Topics with no replies for 2 weeks are closed automatically.

Old Forums (READ-ONLY): The community now lives at WP Sharks™. If you have an s2Member® Pro question, please use our new Support System.

Contacting s2Member: Please use our Support Center for bug reports, pre-sale questions & technical assistance.