Cristián Lávaque

What Raam said. The upgrade won’t affect your users.

That said, it’s always good to do backups regularly and before you make changes. :)

I see you went out of PHP and then back again after a couple of new lines. That shouldn’t be in that file.

Also, there’s a similar hook for the BuddyPress integration.

Try this:

Cool. :)

Hi Sebastian.

You should keep a backup of your translation so you don’t lose it during the udpate. After the update you can apply the translation again.

You can do a diff between the previous and latest pot files in s2Member and see if you need to update anything in your translated one.
http://www.prestosoft.com/edp_examdiff.asp

I hope that helps. :)

Yes, there is, that’s why I said you’d have to modify the conditionals. A simple [hilite mono]OR is_admin()[/hilite] added to each should do the trick.
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Simple/Shortcode Conditionals[/hilite]

s2Member supports ALL Conditional Tags in WordPress®

I hope that helps. :)

Nola, now that you gave some more info on how you want to do it, here’s what I suggest:

Have everyone register with the same form, which’d give them Level 0, and then your client reviews each new user and upgrades their profiles with the access he wants to give them.

This would work as an approval process and also give him control over the access they get. The content should all be protected above Level 0 so they can’t see it when they first register.

The confirmation email is sent to those that paid, but the New User email is sent to all new registrations. The latter can be edited from [hilite path]Dashboard -› s2Member® -› General Options -› Email Configuration[/hilite].

I hope that helps. :)

Maybe around a month. We’re trying for that, but is not in stone yet.

Hi Joshua.

s2Member Pro is an add-on to the s2Member Framework plugin, but is not a WP plugin itself, just an add-on. Here you can read the installation instructions for Pro:
s2Member® » Pro » Install/Upgrade Instructions

I hope that helps. :)

Sorry, just noticed it’s in the Pro Customers forum and you don’t have access to it yet.

Basically the idea is that instead of sharing a single account, each person would have his account and the one with the paid access could share it with other accounts he picked.

Hello Mark.

Yeah, it’s very possible.
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Simple/Shortcode Conditionals -> Example #3[/hilite]

It’d be something like this:

[[s2If current_user_is(s2member_level0)]
Some content for Free members.
[/s2If]]

[[s2If !current_user_can(access_s2member_level0)]
Some public content.
[/s2If]]
[/hilite]

I hope that helps. :)

Hi Joe.

Could you please enable logging, try a new transaction and then quote here all the log entries related to that test? Please x-out any private info (e.g. email address).
[hilite path]Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging[/hilite]

Thanks!

Hi Terry.

Philly’s suggestion would work to use the AWeber integration, which only deals with levels so far, not custom capabilities.

You’ll be giving them a level for the purpose of having them related to separate AWeber lists, but you’d protect the content with custom capabilities instead of levels, which will keep each user to the content he paid for and not the rest.

The coming major release of s2Member will give you way more control over the AWeber integration to add them to lists based on the access you’re selling them without having to create workarounds like the above.

Another thing I wanted to mention, just in case it’s a problem for you, is that the current s2Member only supports one subscription per user. That is, only one recurring payment subscription, so a user that is paying monthly for Access 1 won’t be able to also pay monthly for Access 2.

That isn’t a problem if they are one-time payments for lifetime access, though. He can pay one time for each of the accesses you sell and they wouldn’t have an issue.

Multiple subscriptions per user and separate times for each access is another thing we’re working on to make possible in the coming major release.

I hope it helps.

• This reply was modified 4 years, 9 months ago by  Cristián Lávaque.

But, that hook is after the page was excluded from the Specific Page restriction.

Did you try something like this with the hook I mentioned before?

function special_access($excluded, $vars) {
if (current_user_can('access_s2member_ccap_student')) {
$excluded = true;
return $excluded;
}
[/hilite]

or even

function special_access($excluded, $vars) {
return (current_user_can('access_s2member_ccap_student') ? true : $excluded);
}
[/hilite]

• This reply was modified 4 years, 10 months ago by  Cristián Lávaque.
• This reply was modified 4 years, 9 months ago by  Cristián Lávaque.
• This reply was modified 4 years, 9 months ago by  Cristián Lávaque.