Cristián Lávaque

Well, that hack won’t automatically protect that directory from any access, the .htaccess rules would be needed to take care of that. So this won’t be protected: [hilite mono]/wp-content/uploads/2013/06/photo.jpg[/hilite].

What you’re doing with the hack is tell s2Member to pick the file from that directory when you go through s2Member, like [hilite mono]/?s2member_file_download=photo.jpg[/hilite].

If you want to protect the custom directory with .htaccess, you could try the original .htaccess from s2member-files, which will probably need customization too.

Every level has access to content at its level and below, so s2Member Level 3 has access to level3, level2, level1 and leve0. Any user at Level 0 or higher will have access to level0. This is explained in the documentation, I recommend that you study it: [hilite path]Dashboard -› s2Member® -› API / Scripting -› Conditionals[/hilite]

Your code can be rewritten like this:

[hilite pre_code]
ID == 2448 && current_user_can("access_s2member_level0")) { ?>

';

[/hilite]

See:
http://www.php.net/manual/en/language.operators.logical.php
http://reference.sitepoint.com/css/selectorgrouping

Now, that conditional will include Level 4 users or higher too (and your code does), but if what you want is that it’s only true for Level 3 users or lower, you could do it like this:

[hilite pre_code]
ID == 2448 && !current_user_can("access_s2member_level4")) { ?>

';

[/hilite]

Exclamation mark before the check means “false” so in this case “it’s false that the user can access level4” or “user can’t access level4”. http://www.phpreferencebook.com/samples/equal-sign-operators/

And it WAS working using the standard wordpress media uploading before installing NextGEN

What is the file link that you’re expecting to work with the URI restriction? Could you show me the URL?

That code doesn’t do anything at all, it doesn’t protect anything

That’s all that needs to be done, as far as I know. What directory did you choose? And what URL are you using for the protected file?

Cool. :)

It looks from the log entry that the wp_mail didn’t return any errors when sending it, and all the info is there, so s2Member seems to be doing all it should be doing.

I’d first make sure that the email didn’t go to the Spam folder. If it isn’t there or the Inbox, then there may be a problem with your WP sending emails. Do new registrations get an email from WordPress with the username and password?

Have you tried all these? Knowledge Base » Troubleshooting Email Delivery Problems

You should also try all these: Knowledge Base » Common Troubleshooting Tips

You could try the [hilite mono]storage[/hilite] attribute for the shortcode, or [hilite mono]s2member-file-storage[/hilite] variable for the URLs.

See:
[hilite path]Dashboard -› s2Member® -› Download Options -› Shortcode Attributes -> storage[/hilite]
[hilite path]Dashboard -› s2Member® -› Download Options -› Advanced Mod-Rewrite Linkage[/hilite]

I hope that helps!

That’s information that s2Member passes to PayPal, although it’s not part of the [hilite mono]desc[/hilite] attribute of the button shortcode. You can see the button’s fields in the template here: s2member\includes\templates\buttons\paypal-checkout-button.php

You can try a button created over at paypal.com, integrated with s2Member, and see if you get the same description in the PayPal checkout page. Knowledge Base » Using Buttons Generated @ PayPal.com

(That button created over at paypal.com will only work well for new signups, not for upgrades of existing users.)

Please try these:

– Enable logging during tests. [hilite path]Dashboard -› s2Member® -› Log Files (Debug) -› Logging Configuration[/hilite]
– Verify that your PayPal integration is complete and correct. [hilite path]Dashboard -› s2Member® -› PayPal® Options[/hilite]
– Knowledge Base » Troubleshooting Email Delivery Problems
– Knowledge Base » Common Troubleshooting Tips

You can do your tests with live 1 cent transactions.

Great! Thanks for the update. :)

Maybe the change in the email configuration just needed some time to complete. Just keep an eye on it, test it often, to see if you still get the emails.

I’m glad you solved it. Thanks for the update. :)

Here’s the documentation for the s2Member-bbPress integration: [hilite path]Dashboard -› s2Member® -› Other Integrations -› bbPress®[/hilite]

Regarding s2Member’s Post Level Access Restrictions with bbPress®. Before you decide to use Post Level Access Restrictions, please take a look at: [hilite path]s2Member -› Restriction Options -› URI Access Restrictions[/hilite] and consider the following limitations in the current release of s2Member. It is currently NOT possible to protect a Forum, and have all Topics inside that Forum protected automatically. In order to accomplish that, you’ll need to use s2Member’s URI Access Restrictions. Also, s2Member is currently NOT capable of protecting Topic Tags; but you can use URI Restrictions for these also.

You may be able to use the URI restriction for all threads in a forum, if you manage to add a slug for the forum in the thread permalinks. Not sure if bbPress lets you do that, though, you’ll need to find out.

s2Member doesn’t have member activation. I know BuddyPress adds that, do you have that it active in your site? If so, I’d ask the BP guys about this. I imagine there must a way for the admin to make the user active. http://buddypress.org

Another option is to just generate a new registration link for her, so she can register a new account at the paid level, then delete the previous account. See: [hilite path]Dashboard -› s2Member® -› PayPal® Buttons -› Registration Access Links[/hilite]