Cristián Lávaque

Hi Robert.

s2Member can integrate its custom profile fields with BuddyPress, not not the other way around, i.e. BuddyPress profile field into an s2Member pro-form. [hilite path]Dashboard -› s2Member® -› General Options -› Registration/Profile Fields -> BuddyPress[/hilite]

For the BP field to show in the pro-form, you’d have to hack the pro-form’s code.

and this works – but I had a thank-you page set up for levels above 0 (since they are paid subscribers via paypal pro forms) and this is now ignored – all subscribers go to the same page (once-only download, subscriber-only content) after registering.

I would like the paid subscribers (level 1 & 2) to go to the thank-you page (which has a link to once-only download content) after they purchase/register. Is this possible?

Well, you’re bypassing the success URL when you log the person in and send him to the Login Welcome page.

Now, you could use the login Welcome Page to show the message you want, even customizing it based on the user’s level using conditionals. [hilite path]Dashboard -› s2Member® -› API / Scripting -› Simple/Shortcode Conditionals[/hilite]

And if you want to show the message on just the first login, you can use this: [hilite path]Dashboard -› s2Member® -› General Options -› One-Time Offers (Upon Login)[/hilite]

2) Is it possible to disable the registration email alltogether? There is no need for the user to return to the site after initial registration as subscription content will be emailed…

No, s2Member lets you customize the New User email, but I don’t see a setting to not send it. If the person is registering an account, I think it’s good to send him his login info and a welcome. You can change the message to what works best for your site. [hilite path]Dashboard -› s2Member® -› General Options -› Email Configuration -> New User[/hilite]

3) Small bug – If i try to register an existing email address, I get returned to the registration form, but there is some html leakage out of the email address field on the form – perhaps you forgot to escape the content?

I couldn’t reproduce this. I just get a warning “That Email Address is already in use. Please try again” and the form prepopulated with what I submitted.

Did you customize the pro-form in some way?

It could also be another plugin or the theme affecting yours? As a test, try with the default TwentyEleven theme. Or deactivate other plugins one by one, checking after each if the problem continues.

4) I have installed s2member server-wide on a multi-site worpress installation with domain mapping. This does lead to a lot of wrong URLs appearing (after registration, login etc.) – they show the parent domain not the one mapped to this blog. Would s2member handle this better if I installed it on only the blog that I am using it with (I don’t have a multi-site licence)? Or are these problems caused by WordPress?

That reminds me of this: http://www.s2member.com/forums/topic/login-widget-on-multisite/#post-19982

Maybe you have a variation of that happening? [hilite mono]network_site_url[/hilite] instead of [hilite mono]site_url[/hilite] being used.

---

I hope that helps. :)

Andrew said:
I sent the log files a few days ago. Did you have the chance to look at them? I’ve had successful transactions happen in the meantime, but there are those 2 that never worked. I would like to assure this doesn’t happen anymore.

Very sorry about the delay. I wasn’t aware that you had sent them until I read your post now. I found your email caught in the spam folder for some odd reason.

I reviewed the logs and your s2Member settings. I noticed that you’re missing the PDT Identity Token in your settings. Not sure if this is causing the problem you had, but it may cause problems not having it configured. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› PayPal® PDT Integration[/hilite]

Could you complete that and monitor if you still have the problem happen? Thanks!

marc-andre benard said:
I have the same problem, many times I have this problem, sometime all work fines but 1 transaction on 3 have this error.

Could you please send your login info via the contact form to take a look at your installation? Thanks!

Hi Sara.

So you have a folder with files inside the s2member-files directory? I imagine your file is trying to load others in the same folder. The thing is that all of the them will now be protected by s2Member, so you’ll need to modify the links to them in to include a download key. [hilite path]Dashboard -› s2Member® -› Download Options -› Advanced Download Restrictions[/hilite]

If you can’t do that, then you’ll need to use another player for your video file. We’ve found JW Player to work quite well so far. [hilite path]Dashboard -› s2Member® -› Download Options -› JW Player® & RTMP Protocol Examples[/hilite]

I hope that helps. :)

Yeah, we’re looking at how to make something like this possible in the new s2Member.

Yes, we are very much closer, but still not at release stage. You’ll be one of the first I’ll let know about it. ;)

Okay. Please let me know when you hear back from them. I hope it’s easy to fix. :)

I see. No, I don’t know what else could be causing it.

Do you have logging enabled? If not, please do and log at least one customer that has this problem, please. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Account Details -› Logging[/hilite]

Please send the logs using the contact form, so I can take a look. s2Member® » Private Contact Form

Thanks!

You can create a test user. If you have custom profile fields, fill them all out for this test user so they’re not empty. Then export the users from here: [hilite path]Dashboard -› s2Member® -› Import/Export -› User/Member Exportation[/hilite]

Open the CSV file in a text editor and you’ll see the proper format. You can open it in Excel to edit it and add new rows for the rest of the users, and then import them here: [hilite path]Dashboard -› s2Member® -› Import/Export -› User/Member Importation[/hilite]

You can post here, inside code tags, the CSV file you export with this test user if you have any questions about it. I’ll take a look at it and help as I can explaining what you don’t understand.

I hope that helps. :)

Hi Diva.

The CSV file you linked to is wrong. The headers have triple double-quotes, and the custom fields wouldn’t be in that row. And the following rows are all empty with just commas.

[hilite pre_code]
"""ID""","""User Name""","""Password""","""First Name""","""Last Name""","""Display Name""","""Email""","""website""","""Level[0-9]+ or Role ID""","""Registration Date ( mm/dd/yyyy )""",Auto-EOT Date ( mm/dd/yyyy ),"""Paid Subscr. ID""","""Paid Subscr. Gateway""","""street_ address""","""street_address value""","""city""","""city value""","""state""","""state value""",zip code,home phone,work phone,date of birth
,,,,,,,,,,,,,,,,,,,,,,
[/hilite]

Could you post inside code tags the CSV you got when exporting the test user you created with all the custom fields filled out, please? Thanks!

Hi Mary.

I’m not sure why the log file is not being updated. Did you change something 3 days ago in your site? Maybe added/updated a plugin that caused this? As a quick test, if you deactivate the other plugins and to a test transaction, does the log now have the new entry for it?

Hi Antonio.

Remember that the user has to be logged in to his account for the upgrade to happen, otherwise he’ll be creating a new account.

If I’m not mistaken, when the user starts a new subscription, the previous one will be ended by s2Member. At least that’s how it works for the PayPal integration, so I’m assuming it’ll be that way for Authorize.Net.

I’m emailing Jason to ask him to confirm this. He may take a few days to reply, because he isn’t checking his inbox as often now, and he just did yesterday, but I’ll let you know as soon as I hear back from him.

Or you could do a couple test live 1 cent transactions to see how it behaves. :)

Thanks for the kudos, Dean! And yeah, Philly is a great guy and super kind giving good help. :)

Yes, plugin conflicts are more than I would have thought before I started giving support. There are certain areas very prone to collissions in one way or another. In the new s2Member we’re avoiding as many as we can, in order to reduce the number of trouble the combination with other plugins causes. We may not completely remove them, but they should be less.

No problem. :)