Cristián Lávaque

This is what he told me:

Jason said:

This has come up in the past and it continues to be a problem of sorts.

Unfortunately, ccBill does not provide any immediate response to s2Member after checkout. There is no Auto-Return functionality provided by ccBill. The only way s2Member can accurately verify the transaction is to await the IPN communication from ccBill which occurs behind-the-scene (e.g. ccBill® Background Post Integration).

A possible solution to this problem where Open Registration is enabled, is to use a custom Thank-You page to state clearly what the customer should do. s2Member does this by default already, but if he’s having problems, he could use a custom Thank-You page with ccBill and elaborate further to help prevent customers from taking the wrong route to registration.

The default Thank-You page (i.e. ccBill® Approval URL) looks like this:
http://www.example.com/?s2member_pro_ccbill_return=1

But you can use whatever URL you prefer instead. So if you setup a custom Thank-You page of your own, you can swap out the default s2Member handler with your own. Siince this URL does nothing after checkout (other than display a message to the customer), there is no harm in changing it to whatever you like best.

See also: [hilite path]s2Member -› ccBill Options -› ccBill® Approval/Denial URLs[/hilite]

Another thing that you may try, that I just thought, is only sell the paid membership to those already logged in to their free account. This way the purchase will upgrade the existing account and you’ll avoid the issue you’re having.

Please make sure that only the .htaccess file is left in the /wp-content/plugins/s2member-logs/ directory. Any log file or archive of them, will cause the badge to not validate.

Jason reviewed your site and he agrees that you have a problem with mod-rewrite in that directory. This is what he said:

Yes, Mod-Rewrite on this site is broken in some way. It appears to be a compatibility problem. I am investigating that. However, you are correct. A standard link with a query string will suffice if rewrite is broken.

It appears that his web server has disabled Mod-Rewrite in this directory for some reason. I don’t see this as an s2Member compatibility issue really, more of a web hosting compatibility issue in my opinion.

It appears that one of the following could be causing the issue with Mod-Rewrite.

His Apache configuration does not FollowSymLinks
This line inside /s2member-files/.htaccess is failing for some reason:

Options +FollowSymLinks -MultiViews -Indexes

See also: http://httpd.apache.org/docs/2.2/mod/core.html#options

The underlying problem is not that s2Member’s .htaccess file is not working, it’s that his web server is not even reading that file. It pretends like it’s not even there. Which also means that any files in that directory (/s2member-files/) are NOT being protected in any way.

He should stick with query string format for his links, and stick with S3 as his storage engine for s2Member.

Or contact the hosting company to resolve this issue with s2Member’s .htaccess file not working.

Or switch hosting providers.

---

/wp-content/plugins/s2member-files/s2member-file-remote/s2member-file-inline/

That uses the mod-rewrite rules, so it won’t work for you until its resolved. You can use the normal querystring format, though:

http://yoursite.com/?s2member_file_inline=yes&s2member_file_remote=yes&s2member_file_download=pg-20130321.mp3

I see. Well, this is our refund policy: s2Member® » Terms » Refund Policy.

The login is handled by WordPress, so if you can get your app to log the user into WordPress, that should be enough for his access his account has to the content.

Other than that, there are these articles that you may find interesting:
Knowledge Base » Remote User Status (Custom API)
Video » s2Member® File Downloads (Remote Auth/Podcasting)

Oh, thanks so much! I fixed the code in that post. :)

You could have just one Login Welcome page with a conditional that checks that custom profile field and shows a different message based on its value.

[hilite path]Dashboard -› s2Member® -› API / Scripting -› Advanced PHP Conditionals[/hilite]
[hilite path]Dashboard -› s2Member® -› API / Scripting -› PHP/API Constants -> S2MEMBER_CURRENT_USER_FIELDS[/hilite]
http://www.s2member.com/codex/stable/s2member/api_functions/package-functions/#src_doc_get_user_field%28%29

If you protected the content at Level 1, then General Staff users should be given the s2Member Level 1 role for them to access those pages. Same for Level 2 Managers.

You can edit each user individually from their profile pages, or change their role in bulk from the Users list.

You mean you created the custom profile field and want to add a description that says that? Have you tried using the “Field Label/Desc”? [hilite path]Dashboard -› s2Member® -› General Options -› Registration/Profile Fields[/hilite]

If you can acknowledge this, and tell me what you need from me: site login, Clickbank login, Clickbank Master login, and ftp login, and where I can send this to you securely, I’ll pass it over.

You can submit all those using our secure contact form, please: s2Member® » Private Contact Form.

Also make sure you have logging enabled, as the logs will help debug this. [hilite path]Dashboard -› s2Member® -› Log Files (Debug) -› Logging Configuration[/hilite]

Do you get any emails from WordPress? If you register a free account, does the New User email get sent? If not, please read this: Knowledge Base » Troubleshooting Email Delivery Problems

as it doesnt work in my ie either

What IE version and OS are you using?

Have you tried these? Knowledge Base » Common Troubleshooting Tips

If you protect the page at Level 0, the user will be required to be logged in. If he isn’t, he won’t have Level 0 access and will be redirected to the Membership Options Page, where you can ask him to login/register.

[hilite path]Dashboard -› s2Member® -› Restriction Options -› Page Access Restrictions[/hilite]
[hilite path]Dashboard -› s2Member® -› General Options -› Membership Options Page[/hilite]

You could probably just hide it with CSS. Try

[hilite pre_code]
div.ws-plugin--s2member-pro-login-widget-remember-me {display: none !important;}
[/hilite]

Other than that, you’d have to edit the PHP file for the pro login widget. If you do, work on a copy in the must-use plugins directory so it doesn’t get replaced when you update s2Member. /wp-content/mu-plugins/

I hope that helps.