Cristián Lávaque

Hi Kim.

Is my code wrong?
Is it that I am using PayPal hosted buttons?
Any other ideas?

The code looked fine, the only difference I saw with the sample that comes in the documentation, was that you were using the HTML entity for the ampersand (&), instead of the symbol, but as far as I know, either one would be fine. In any case, you can try this:

<img src="https://shareasale.com/sale.cfm?amount=%%initial%%&tracking=%%subscr_id%%&transtype=SALE&merchantID=26763" width="1" height="1" border="0" />

It’s fine to use a PayPal created button, as long as you integrated it with s2Member. If you didn’t integrate it, that’d explain why the s2Member tracking API didn’t fire. Here’s an article on how to integrate the button with s2Member: Knowledge Base » Using PayPal created buttons.

I cannot switch to using the S2Member generated buttons because my theme inserts about four inches of blank space above the button and I have never been able to solve that problem.

That’d indicate that the theme or another plugin is messing with the content filtering, and adding a bunch of HTML paragraph and line break tags. Try the suggestions in this article, please, if possible it’d be best to use the shortcode for the button: Knowledge Base » Common Troubleshooting Tips

The signup one would only happen for a paid registration, while the payment one happens then and every recurring payment afterwards. If you only want to pay a commission on the first payment, the signup one would be best, while the payment notification will work if you want to pay a commission on the recurring payments too.

Hi Corey.

She wants ONE registration form (with multiple Custom Registration/Profile Fields).

That’s fine.

She wants 12 membership levels, each with a different price (although, from S2Member point-of-view, they’ll all function as Level 1.)

No, they wouldn’t. Levels are different, they give incremental access. That means that a Level 3 user would have access to Level 3 content while a Level 2 user wouldn’t. Since the access is incremental, the Level 3 user would also have access to the lower levels, e.g. 2, 1, 0 and public.

If you need the access to be specific to the level, then you’d have to use conditionals or instead sell custom capabilities.
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Simple/Shortcode Conditionals -> Example 3[/hilite]
Video » s2Member (Custom Capabilities)

Is there a way to put all this on the one ‘Membership Options Page’?? Or is there some other way to do this?

You can only use a single pro-form per page, so if you’re different things, you’ll need to either have the separate pro-forms in their own pages and link to the from the Membership Options page, or have the pro-form in the Membership Options page and refresh the page with a customized pro-form when the user selects one of the options. Knowledge Base » Using variables in a shortcode

s2Member doesn’t use those meta fields, only its own custom profile fields. [hilite path]Dashboard -› s2Member® -› General Options -› Registration/Profile Fields[/hilite]

If you need to integrate both, you’d have to create a customization to achieve it.

Erin, can you try another URL shortening service? [hilite path]Dashboard -› s2Member® -› General Options -› URL Shortening Service[/hilite]

s2Member can receive payments from a checking account if it’s a funding source in the PayPal account… Here’s a quote from a chat I had with Jason some time ago:

Jason said:

Auth.Net… no, no checks. They do have a service that allows for the acceptance of checks, called eCheck.net, but we don’t support it, and we never will. I’ve worked with it in the past, and there are MANY issues, so I don’t even want to make that option available.

PayPal allows for checks. Or, ACH debits really. A PayPal account can be connected to a checking account, so that payments via PayPal Buttons or through Pro Forms with Express Checkout are actually funded by a checking account.

Yes, this works with Pro Forms also, so long as PayPal Express Checkout is offered as the solution for any customer that wants to pay by check (i.e. please signup for a PayPal account and connect that to your checking account).

I hope that helps.

Hi Addison.

So you want to have the admin bar not shown to users? You can try a plugin for that. http://wordpress.org/extend/plugins/search.php?q=remove+bar

i have considered that my installation may be corrupted, because the server check tool notified me of this due to some version id number not matching, (?) so i might try a reinstall

Yeah, if the server check tool gave you a warning/error, it’d be good to fix it following the advice given there.

No problem. :)

Glad you found a thread that helps you. :)

About the content access, s2Member levels give incremental access, so the user will have access to content at his level and the levels below. A level 4 user would have access to content for levels 4, 3, 2, 1, 0 and public.

If you need to make the access specific to that level, then you’d have to use conditionals or custom capabilities.
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Simple/Shortcode Conditionals -> Example 3[/hilite]
Video » s2Member (Custom Capabilities)

I want buyers to have both options “pay in full for lifetime access” And the option to “pay in 3 payments for lifetime access”.

That’s fine, you’d just have to create a button for each payment option.

WHen you say, “deal manually with those who don’t finish paying” do you mean, for example, their credit card on files expires? I will have to followup for payment manually?

Right, if he picks up the 3 payments plan, pays only one but then cancels the subscription, he’d be left with access to the content although he didn’t finish paying, unless he’s demoted by you or you do something so he finishes paying.

The reason why I say you need to deactivate the auto-EOT behavior, is that after the recuring times are over, PayPal would tell s2Member that the subscription ended, and it’d trigger the EOT behavior. But if that happens when the user finished paying all the installments, then he shouldn’t be demoted, but if it happens when the user didn’t finish paying it’d be fine. So you’d need to handle those manually.

Will your suggestion work also for authorize.net payment method? (I notice there’s no authorize.net buttons, just pro forms).

Yes, Auth.Net pro-forms also have the [hilite mono]rrt[/hilite] attribute. [hilite path]Dashboard -› s2Member® -› Authorize.Net® Pro Forms -› Shortcode Attributes -> rrt[/hilite]

To clarify… this person that tried to unsubscribe (inside his MY ACCOUNT)… would have registered AFTER we launched with PayPal Pro in place…

I was told this person registered and paid with credit card… (I do not have confirmation of this, however)…
And wondered if there is a way to confirm one way or the other… inside S2, inside PP Pro or where.

Since he didn’t subscribe from his PayPal account, the subscription won’t be there for him to end it. If he subscribed from your site, paying with a card in your pro-form, then he’ll need the cancellation pro-form to end the subscription, or you can end it for him from your side of PayPal. [hilite path]Dashboard -› s2Member® -› PayPal® Pro Forms -› Billing Cancellation Forms[/hilite]

(our early BETA registrants DID go thru Standard PayPal… and those, I believe would be the ones that should have to unsubscribe on their own inside PayPal, right?…if it was working correctly).

Right, they need to create the PayPal Pro subscription and end the PayPal Standard one.

I’m not sure I quite understand “when” we will be needing to manually unsubscribe inside S2… in what instances… since I think you misunderstood me regarding what is in place now…

You mean the PayPal Standard subscriptions? What I meant was that if you wanted to keep those subscriptions, you’d need to manage them manually instead of leaving it to s2Member, because s2Member now has the PayPal Pro integration. So you’d need to remove the PayPal subscr. ID from those users so s2Member doesn’t check PayPal for them, but then you’d need to demote the users manually when the subscriptions end.

And finally… How do I test the other paypal pro form unsubscribe? Would I have to subscribe myself and then unsubscribe? (without doing the sandbox thing).

Yeah, you could test it like that.

As far as the other lady… this was a standard paypal registration, prior to us implementing PayPal Pro…
so, it was a subscription… and I’m not clear why it wouldn’t have attempted a re-charge of the account once she replaced her bank/credit card info with her new info. So, you are saying, he and/or she needs to contact PayPal in this situation?

Right, this is on PayPal’s side, since they are the ones managing the subscription.

Hi Kenn.

Yes, it’s possible. You’d use the [hilite mono]rrt[/hilite] attribute set to 3 and have the Auto-EOT Behavior disabled, so it doesn’t demote, but you’ll have to deal manually with those that don’t finish paying.

[hilite path]Dashboard -› s2Member® -› PayPal® Buttons -› Shortcode Attributes -> rrt[/hilite]
[hilite path]Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior[/hilite]

Hi Brian.

The custom profile fields are validated on the client’s side with JavaScript, so they can be bypassed disabling that.

Here’s a tip to add server-side validation: http://www.s2member.com/forums/topic/registering-without-required-fields/#post-10707