Cristián Lávaque

Great! Thanks for the update. :)

Thanks for the info.

After getting fixing the warning in the server scanner, did you try a test purchase to see if you still have the problem?

Have you verify that all the credentials for Authorize.Net are correct? [hilite path]Dashboard -› s2Member® -› Authorize.Net® Options[/hilite]

Have you tried these? Knowledge Base » Common Troubleshooting Tips

Maybe the payment failed too many times? Not sure what else could have happened.

Did you check your logs for entries related to the subscription to see what it says about how it ended? [hilite path]Dashboard -› s2Member® -› Log Files (Debug) -› s2Member® Log Viewer[/hilite]

Did you just have it with this user or is it the way it’s behaving with everyone that cancels?

Thanks, got the email.

I see, your “year” field is multioption with checkboxes. That’d give you an array, not a string. Would someone select more than one year? If not, you may prefer to use a dropdown.

Anyway, you can see the format of your array doing:

outputs

Array
(
	[0] => year11
)

So your condition would go like something this:

http://php.net/in_array

You may need to add some extra checks in the condition, for those that didn’t select a year.

I hope that helps.

It’s as if you had an incomplete s2member-pro installation.

Try this please: Knowledge Base » s2Member® Server Scanner

If that doesn’t help, try these: Knowledge Base » Common Troubleshooting Tips

Thanks for the info.

Did you verify with PayPal if your client’s PayPal Pro account is PayFlow Edition or not? Also, verify with them if DPRP is enabled. Knowledge Base » PayPal Pro, PayFlow, DPRP, Express Checkout

I know you said it’s PayFlow Edition with recurring payments, but what you described afterwards seems to indicate something else. It’d be best to verify these with PayPal.

Paypal tells us this is a problem with the API integration.

s2Member itself doesn’t have a problem with this, so it’d be the values entered when you configure the integration. The PayFlow Edition name comes from using the PayFlow API, so make sure you have this correct.

I do have logging turned on and can send log details.

Sure, you can submit the login info, I’ll take a look at the log in your dashboard (don’t attach the log files). Please let us know when you sent the email. s2Member® » Private Contact Form

0 => 'Unable to verify POST vars. This is most likely related to an invalid Authorize.Net® configuration. Please check: s2Member -› Authorize.Net® Options.',
1 => 'If you\'re absolutely SURE that your Authorize.Net® configuration is valid, you may want to run some tests on your server, just to be sure $_POST variables are populated, and that your server is able to connect to Authorize.Net® over an HTTPS connection.',
2 => 's2Member uses the WP_Http class for remote connections; which will try to use cURL first, and then fall back on the FOPEN method when cURL is not available. On a Windows® server, you may have to disable your cURL extension. Instead, set allow_url_fopen = yes in your php.ini file. The cURL extension (usually) does NOT support SSL connections on a Windows® server.',

Could you please try this and see if it finds any problems? Knowledge Base » s2Member® Server Scanner

Also, sometimes the post starts talking about Authorize .Net and finalize talking about PayPal.

You mean in the log? That’s okay. The last part of the processing is done with code that was originally to process just PayPal. Actually, the logs that say “paypal” in the file name are also relevant to you because of this.

I don’t have any experience with event management plugins, but I have seen Event Espresso mentioned a few times in the past.

I’ll let others reply if they see this, but if you have their plugin, you may want to start testing with it.

So we need integration points of: make sure someone is a member so they can get the discount and possibly make them a member when they sign up for the conference (I know this might have to be manual though).

To check if the user is a member, you could use conditionals, and modify the price based on that. [hilite path]Dashboard -› s2Member® -› API / Scripting[/hilite]

No, the EOT would be immediate for refunds or reversals.

A cancellation would not trigger an immediate EOT, the time for it would be set at the end of the paid term plus a day.

You can see the documentation and settings for it here: [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior[/hilite]

Thanks for the updates/reports, guys. I’m forwarding this to Jason.

The drip won’t cause a redirection, just shows the content or not based on the conditional.

A restricted page with a level access restrictions or custom capability would cause a redirection to the Membership Options page.
[hilite path]Dashboard -› s2Member® -› Restriction Options[/hilite]
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Custom Capabilities[/hilite]

To customize the Membership Options page, you can use the variables that are provided. You can read the documentation for them here: [hilite path]Dashboard -› s2Member® -› API / Scripting -› Membership Options Page Variables (MOP Vars)[/hilite]

Sorry … I’ve been in the admin area messing with the General settings to get the main site URL to land on my Squeeze page URL. I’ll stop and wait for you to post.

Yeah, I noticed, but I edited the address back to the domain name. That setting you were changing to the landing page, is going to affect every URL that the setting is used for. Even the preview and every other page had the squeeze page’s slug prefixed, even the paid member ones.

If you want to send people to the squeeze page when they don’t have the access to the s2Member protected content, you may want to set it as your Membership Options page. [hilite path]Dashboard -› s2Member® -› General Options -› Membership Options Page[/hilite]

By the way, my last two posts happened almost at the same time you posted. You may want to go back up a bit and check if you had missed them because of that.

I didn’t want you freaking out for too long. With the info you had sent I managed to get to your database and fixed one of the addresses for you. Then was able to login to the dashboard and fixed the other one. :)

I’ll look at the PHP thing now.