Cristián Lávaque

Glad you got it working.

Yeah, roles are lowercase, just had that issue with another customer who sorted it out today as well.

About the arguments, you can see them in the page I linked to.

:)

Yeah, very glad you got it working. :)

Sorry I capitalized the role name, I thought that was the way you created when you wrote it like that earlier. I should have asked you to check that.

You’re welcome. :)

I figured out a way to do it – un-patient as I am – but I am still going to try your method. Trying to keep it as code-clean as possible.

If you know PHP, you can also write conditionals using [hilite mono]S2MEMBER_CURRENT_USER_ACCESS_LEVEL[/hilite].
[hilite path]Dashboard -› s2Member® -› API / Scripting -› PHP/API Constants[/hilite]

How is it with e-mails? Just got a few sign-ups through our website but for some reason the return sign-up e-mails get stuck in the spam folder for the recipients.

The problem is that your emails are, for some reason, being considered spam by the customer’s filters. There are many things that spam filters look at. I’m guessing that the problem may be with the IP your server has, if it’s shared, maybe another person in that same server has not been careful with his email practices.

This article may help:
Knowledge Base » Troubleshooting Email Delivery Problems

Another question – while I have you accessible – how do I create a simple login for individuals on a frontpage of the site without using the s2member widget?

You can Google that, there should be tutorials to do that with WordPress. Now, you can use the widget inside the page, not just in widget areas.
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Pro Login Widget (via PHP)[/hilite]

Hi Bret.

What I replied in your other thread may help.
http://www.s2member.com/forums/topic/give-specific-postpage-access-with-php/#post-8096

Hi Brett.

I researched this for a bit and found a hook you can try: [hilite mono]"ws_plugin__s2member_sp_access_excluded"[/hilite].

http://www.s2member.com/codex/stable/source/s2member/includes/classes/sp-access.inc.php/#src_doc_line_103

Notice it has 3 arguments, which is important when you use add_filter.
http://codex.wordpress.org/Function_Reference/add_filter

I hope it helps. :)

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

Actually, if you’re not comfortable with using PHP like that, you could do it with shortcode conditionals.
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Simple/Shortcode Conditionals[/hilite]

[[s2If current_user_is_not(Banned)]
Oh, please buy.
[/s2If]]
[/hilite]

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

You could have a conditional in your Membership Options Page for that. E.g.

http://www.s2member.com/codex/stable/s2member/api_functions/package-functions/#src_doc_current_user_is%28%29

Does that help?

I’m afraid that the post protected with Spec Page access won’t be accessible with the right link, unless you created a hack to bypass this, which I don’t know how to do.

One thing you could do is to clone that page for the ones you’re selling the custom capability to.

Would that work for you?

Zoe, you can do that with Custom Capabilities, but there isn’t yet an interface to let the user pick them.

This article may be useful:
http://www.primothemes.com/forums/viewtopic.php?f=36&t=1604

I hope it helps. :)

so there is no way to use s2member without this security badge showing?
in other words, s2member does not have a 100% branding free option period?

You don’t have to use the badge if you don’t want to, that’s just an extra that s2Member makes possible if you choose to use it to generate more trust with your visitor. It’s a free alternative to trust seals that have to be paid for. Totally optional.

If you can remove the comments, it’d be because you’re using the full HTML for the button instead of the shortcode. This is not ideal cause someone could edit your HTML to enter a different amount or length of access, for example.

It’s better if you encrypt your buttons, and for that you’d use the shortcode so s2Member can encrypt it for you.
[hilite path]Dashboard -› s2Member® -› PayPal® Options -› Account Details -> Enable Button Encryption[/hilite]

The comments were causing trouble because of the parsing problem I mentioned is most probably there. To spot what’s causing the incorrect parsing, I suggest doing the tests I mentioned above.

To change the theme in a single page for this test, you can try this plugin:
http://wordpress.org/extend/plugins/page-theme/

To change the plugins in a single page for this test, you can try this plugin:
http://wordpress.org/extend/plugins/plugin-organizer/

If you prefer not to use the shortcode because you didn’t find what’s causing you trouble with the content parsing, then using a button generated over at PayPal will also work and be encrypted.
Knowledge Base » Using PayPal created buttons

I hope that helps. :)

Great! :)