Cristián Lávaque

Ah ok, yeah, that’d work too. :)

About the garbled export file, Jason has been informed and it’ll be fixed in a coming release.

Hi Sasha.

You should be shown the registration form after checkout, but if s2Member doesn’t get all the info it needs from PayPal soon enough, it’ll show that message and have the user wait for the email, which would be sent after getting PayPal’s info.

The logs would definitely help. If you could post the log entries related to the transaction with the problem, x’ing out any private info, it’d be great.

Have you double checked all the integration settings? [hilite path]Dashboard -› s2Member® -› PayPal® Options[/hilite]

Hi Evan.

No, s2Member doesn’t have this feature. That said, you could probably customize it using an affiliate management solution in combination with s2Member.

You may want to look at the Tracking and Notifications APIs. http://www.youtube.com/playlist?list=PLBF914EDFF37EC3E9

I hope that helps. :)

Hi.

The import panel has some documentation that may help you:
[hilite path]Dashboard -› s2Member® -› Import/Export -› User/Member Importation[/hilite]

If you already have some members, you can export them and look at the file you get as an example. If you don’t have any, you can create a couple test acccounts and then export.
[hilite path]Dashboard -› s2Member® -› Import/Export -› User/Member Exportation[/hilite]

I hope that helps. :)

You can’t control the custom fields with the template yet. :/

You’ll notice in the template that there’s a replacement code [hilite mono]%%custom_fields%%[/hilite], which is where the custom fields will be added, but you can’t edit them there.

We’re working on making this possible from the template.

Got ya.

I’ll email Jason asking him what he thinks could have caused that problem for you.

So you want a custom behavior for the EOT triggered by a refund, right? Instead of the demotion to Level 0 or deleting the account, you want to assign them a different role, is that it?

If that’s the case, then no, it’s not possible with s2Member as it is, although maybe Jason knows a hack for that, but it is something that we plan to have included in the next major release of s2Member.

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

Thanks for the update! Very glad you sorted it out. :)

What plugin was it?

I do remember seeing a guide on setting up download folders based on CCaps but can’t find it anywhere – are you able to help me there, please?

To use ccaps for download protection, here’s the documentation:
[hilite path]Dashboard -› s2Member® -› API / Scripting -› Custom Capability & Member Level Files[/hilite]

:)

I just heard back from Jason, I asked him what he thought the problem was, I guessed maybe an output compression issue and he agrees. This is what he told me:

Yea, that looks like the server is configured with some sort of PHP-based output compression, or is running on a server that’s unable to detect the MIME type served via PHP. This is the same issue that was affecting file downloads on some servers before we implemented the .htaccess exclusion recently. I should have included the exportation files in that .htaccess rule as well, just to avoid this issue.

Since I didn’t, we’ll have to deal with this on a case-by-case basis for now. In this case, I’d recommend that she make the following adjustment in s2Member.

[hilite mono]/s2member-pro/includes/classes/exports-in.inc.php[/hilite]
at line #239 find this:

header ("Content-Encoding:");

Change that to:

header ("Content-Encoding: none");

That’s actually invalid, but seems to work as a quick hack in many cases. The better solution is the .htaccess rewrite rule, but it’s not possible to do that with export files just yet. I’ll take care of that asap. If that doesn’t work, we’ll need to know more about the hosting environment (i.e. running Apache? if so, is GZIP enabled? if so, how exactly, mod_deflate?).

Could you provide that info? Also, try that hack and see if it fixes the issue.

I hope that helps.

OK, then it’s not s2Member’s handling of that what’s failiing, since the WP default fails too.

Have you already tried deactivating other plugins? There may be one affecting the New User email part of WordPress.

For a quick test to find if that’s the source of the problem, deactivate them all and register a new account, see if the email gets sent. Then re-activate them one by one, registering a new account after each, and see if you get the emails, until you get the problem back and will know what plugin you activated last. You could register the accounts using names that describe the last plugin you activated, so you know when you get the email, which ones worked.

You can create a copy of the website to test this, if you don’t want to do it in the copy you have, but either way I suggest you create a backup first, just in case.

I hope that helps.