Cristián Lávaque

Hello Gary.

The integration allows you to protect any kind of file you’re hosting with Amazon S3/CloudFront. This protection lets you require the user to have a certain access. The file is protected from being downloaded by someone that isn’t logged in to an account with enough access.

The Amazon S3 integration is currently available in the s2Member Framework, which is free. I suggest that you install it and try it to see if it does all you need it to. There you’ll find extensive documentation on the integration. [hilite path]WP Admin -> s2Member -> Downloads Options -> Amazon[/hilite]

I hope that helps. :)

Hi Angela.

Well, the error may be coming from WP itself if trying to create a user with an empty username.

Now, why is it empty if you’re entering one, I don’t know, I guess it could be because it’s in Chinese?

Could you test with user login “testuser” and see if that gives you the error too?

If you create a user with its username in Chinese using the registration form, does it work fine?

I see, you mean you restricted access to the post in the blog, right? Well, it may be showing in the blog list of posts, but if you try to open the post itself it takes one to the Membership Options page.

This video may help understand that behavior: http://www.s2member.com/videos/F267E93C7B467D64/

I hope it helps. :)

Hello Mathew.

I’m sorry you had that problem. Of you course you wouldn’t want it to happen again.

Would you happen to have logging enabled? If so, please post the log entries related to those users, x’ing out any private info. If it isn’t enabled, it’d be a good idea to do it so you get more info to work with in cases like this. [hilite path]WP Admin -> s2Member -> PayPal Options -> Account Details -> Enable Logging[/hilite]

You can restore access to the user editing his profile and manually adding the ccaps back to it. [hilite path]WP Admin -> Users -> All User -> Edit user -> Custom Capabilities[/hilite]

If they purchased lifetime access, then no EOT should have been set for the users. If they also had a subscription going, separate from the ccap access, and the subscription ended for some reason, that’d set an EOT for the account, affecting the ccaps also. Do you sell a subscription too, or some other access that isn’t lifetime?

Could you review the profile of other users the purchased access the same way those users with the problem did? There’s a field for EOT, it should be blank.

Hi Bendix.

Could you double check that you copied your CloudFront Key Pair ID and Private Key exactly? And did you enable Auto-Configure? [hilite path]WP Admin -> s2Member -> Downloads Options -> Amazon S3/CloudFront[/hilite]

Remember to click the “Save All Changes” button at the bottom after any changes for them to be applied.

Hi Rodger.

You can delete the user from your admin area. Go to [hilite path]WP Admin -> Users -> All Users[/hilite], check the box next to the user’s name and then from the “Bulk Action” drop-down, select “Delete” and click the “Apply” button.

Right now there isn’t a banning feature that’d prevent the user from registering again. You’d need to monitor new registrations to spot the user and remove him again. Even if you banned by email address or IP, there are ways around that, so in the end it still comes down to reviewing new users.

I hope that helps.

Got ya, thanks.

Well, the Page restriction won’t do anything to the blog, because that doesn’t use pages. You can use the Post, Category, Tag restrictions, even the URI restriction depending on your permalink structure. [hilite path]WP Admin -> s2Member -> Restriction Options[/hilite]

Does that help?

Thanks Angela.

Hmm… Could you try deactivating that Formidable Pro plugin for the test too? I know it seems to be key in your setup, but I’d like to identify if it’s the cause of the notification problem.

If that doesn’t identify the problem, please send an email via the contact form: http://www.s2member.com/contact/

I see. Hmm… I remember another user having a similar problem and it was the caching plugin. Could you try using Quick Cache instead of that one? http://wordpress.org/extend/plugins/quick-cache/

About the database repair, I suggest you create a backup before doing it. In Google you’ll find plenty of info on how you can do the repair: http://google.com/search?q=repairing+a+mysql+database

I hope that helps. :)

Hi Mike.

You may find this thread helpful: http://www.primothemes.com/forums/viewtopic.php?f=36&t=14806 :)

Hi Thomas!

Let me see if I understand, the blog is part of the same WP installation that you have installed s2Member in, is that right? Or do you have the blog in a separate WP installation? Are you using multisite?

Hi Karen! Yes, I remember the conversation. :)

– To answer your question, the link to the page he was able to access and shouldn’t have is: http://www.aimcenters.com/login-welcome-page/.

I see, you’re trying to prevent the user from viewing the Login Welcome Page. This is a problem, because that page, since it’s the one show to users when they login, has to be viewable to all logged in users, which includes free ones at s2 Level 0.

The Login Welcome Page is automatically restricted at Level 0, so only logged in users can view it, so it is out of reach for non-logged in visitors, but will always be visible to logged in ones.

– s2Member is demoting subscribers from ‘Studio Level 1″ to Membership Level Free at the end of their term. Is it possible to not allow them, once demoted to ‘Free’ access to level 1+ pages?

If someone gets demoted to Level 0 by the Auto EOT Behavior, then all content protected at Level 1 or higher will be out of his reach.

– I’m wondering if the “Fixed-Term Extensions ( auto-extend )?” needs to be changed from ‘Yes’ to ‘No’?

This affects one-time payments, not recurring payments. That settings makes it possible to extend existing access time.

So, if someone paid for a month of access and a couple of days later pays again for a month, if the auto-extend setting is “yes”, then the new month will be added to the already paid month, resulting in 2 months of access.

If the setting were “no”, then the previous paid month gets dropped and the new one starts immediately, resulting in the a total access of 2 days from the first purchase and another month from the second one.

I hope that helps!

Thanks a lot.

No, that’s not on PayPal’s side. I searched the source files and found where the problem is. I just notified the Lead Developer about it.

In the meantime, you may want to change it manually so you don’t need to wait for an update. [hilite mono]/wp-content/plugins/s2member-pro/includes/iso-3166-1.txt[/hilite]