Cristián Lávaque

s2Member makes it possible to get some data through shortcodes. Please check these: [hilite path]Dashboard -› s2Member® -› API / Scripting -› PHP/API Constants[/hilite].

For the username, you’d use

[[s2Get constant="S2MEMBER_CURRENT_USER_LOGIN" /]]

If you need other variables not available there, you can always install a PHP execution plugin and use PHP in your content.

I hope that helps. :)

Hi Paul.

It’s probably a plugin or the theme adding a redirection on login, which overrides s2Member’s setting for it.

Please watch this video: Video » s2Member (Login Welcome Page Conflicts?)

I hope that helps. :)

Hi Marko.

Could you please enable logging, do a new test, and tell me what the MailChimp log says about it? [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging[/hilite] (Logging is general, even if you enable it from the PayPal options page.)

Thanks!

Hi John.

I can think of these possibilities:

– Deactivation Safeguards was disabled (is enabled by default), and you updated s2Member (WordPress deactivates the plugin to update it). [hilite path]Dashboard -› s2Member® -› General Options -› Deactivation Safeguards[/hilite]

– You restored a backup of your s2Member Options that didn’t have settings you added after creating it. [hilite path]Dashboard -› s2Member® -› Import/Export -› s2Member® Options[/hilite]

– You restored a backup of your site that was missing those settings you see gone now.

– Or maybe your server went back to an older copy of the site for some reason. Very unlikely, but would be a way to explain what you said.

I’m inclined to thing it’s the first one, unless you didn’t lose everything, only part of your settings, in which case it’d be something else, because when the safeguards are disabled and you deactivate s2Member, all data’s removed (like a full uninstall).

Checked the rDNS and it’s point to the domain name – The test site is in a sub domain – would this cause a problem?

I’m not sure… You should contact AWeber support about it. And to ask them if they can say what the problem is, after all the email parser is good, you tested it out fine, and the email s2Member is sending is the same one that works for other site owners. I hope their support guy can help figure out what is causing this problem.

Thanks.

I’ll ask Jason about the difference in the parser, he just added the text version a few days ago and I had not noticed that.

So you tried the BCC hack and you got that email? Did you test forwarding it to Aweber?

About the rDNS, is it giving back the exact domain name? http://www.s2member.com/forums/topic/aweber-custom-email-parser-not-working/#post-11723

Did you test with a different email address to avoid the 12-hour rule they have?

Hi Mike.

You can use the initial term for this (also called trial term when you don’t charge for it). Charge the setup and first month together in the initial term. [hilite path]Dashboard -› s2Member® -› PayPal® Buttons -› Shortcode Attributes -> ta, tp, tt[/hilite]

ta="0.00" Trial Amount. Only valid w/ Membership Level Access. Must be 0 when rt="L" or when rr="BN".
tp="0" Trial Period. Only valid w/ Membership Level Access. Must be 0 when rt="L" or when rr="BN".
tt="D" Trial Term. Only valid w/ Membership Level Access. Possible values: D = Days, W = Weeks, M = Months, Y = Years.

I hope that helps!

Also out of curiosity I see possibilities about multiple subscription capability in the next release? Is this true and when might it be out?

Not the next release, the next major release, it’s a full rewrite of s2Member and still under development, although now close to beta. No date for it yet, we’ll make the announcement when it’s ready. :)

Regarding the hack, I asked Jason to check if any other places needed to be edited, and he replied this:

That section of code should be commented out (as part of this hack), in the following places:

/s2member/classes/includes/auto-eots.inc.php at line #149
/s2member/classes/includes/paypal-notify-in-subscr-or-rp-eots-w-level.inc.php at line #116

I agree. This is part of what’ll change once we make multiple subscriptions and EOTs possible too.

Hi Victor.

s2Member’s profile fields can be integrated into BuddyPress. [hilite path]Dashboard -› s2Member® -› General Options -› Registration/Profile Fields -> BuddyPress[/hilite]

The integration only goes s2Member to BuddyPress, but not BuddyPress to s2Member. So the BuddyPress fields won’t show in the s2Member forms.

s2Member doesn’t remove the BP fields. If you use the BuddyPress registration form, the BP fields will be there.

Does that help?

Hi Gustavo.

How can we do that? Through coupons? Is is possible to configure permanent and reusable coupons (no expiration) so we can just send them the right coupon for future renewals? They can be used more than once?

Right, you can have coupons that don’t expire. [hilite path]Dashboard -› s2Member® -› Pro Coupon Codes[/hilite]

I’d like to clarify something: coupons can only give a discount, either a percentage or a set amount off the regular price. You can’t specify the price, you need to calculate the discount required to get the amount you want to charge.

We have different content (forums, subforums, topics, posts and pages) for men and for women. Men are not supposed to find content for women. And women are not supposed to find content for men. So the s2Member Level system (which is hierarchical) does not help for this restriction by type.

How can we use custom capabilities to restrict new topics created in the women area, for example, without doing it one by one. Is it possible to do? Is there a sample code for that?

No, custom capabilities haven’t been used to protect content in bbPress yet. You could probably do it with some hacking, but I can’t help with that since I have no experience with bbPress.

What you could do, though, is use the levels, which do work to restrict access to bbPress, but customize them so they don’t give incremental access. You’d need to edit the s2Member Level roles to remove the capabilities that give access to lower levels.
http://wordpress.org/extend/plugins/user-role-editor/
Knowledge Base » Locking s2Member Roles/Capabilities

Hi Lopa.

In that case, you’d leave the posts unrestricted, so they can be opened and read, but would need to protect the comments block with a conditional in your template. Video » s2Member (Advanced Conditionals)

I hope that helps. :)