Cristián Lávaque

Nice, Cassel. :)

What Aweber said was that the requests coming in were not following their rules. Otherwise they would have been placed on the list.

So the email going to Aweber is formatted incorrectly, at least according to them.

I see, but were they guessing this or did they see the requests?

When I suggested the article on solving AWeber problems, did you try the carbon-copy hack to get a the email that s2Member sends to AWeber? Knowledge Base » Debugging the AWeber integration

/wp-content/mu-plugins/s2hacks.php
[hilite pre_code]

[/hilite]

Did you get the email copy? Did you see the format?

What happens when you copy it and paste it in the test box for the email parser? What happens when you send it from that email address to the AWeber one?

One site owner tried that, emailing that copy he got to AWeber, and the user got added, although the one sent from the server didn’t (because of the RDNS setting).

Yes, I turned on the ‘reverse DNS’ on my account as well.

Got it that you activated the reverse DNS. Did you verify that it matches your domain name? http://www.s2member.com/forums/topic/aweber-custom-email-parser-not-working/#post-11723

Yeah, I know what you mean! I’ve had that happen to me too. :P

I’m glad you sorted it out. :)

No problem! Glad I could help. :)

Hi Corrado.

1- It’s possible customize the language for the customer? I’d like use the italian language. Free o Pro version?

Yes, you can translate it to Italian. Pre Sale FAQs » Can s2Member® be translated into other languages?

http://www.s2member.com/forums/forum/community/translations/

2- I’ve tryed the “Specific Post/Page Access Restrictions”, i’ve generated the button buy now and is ok.
But the post is yet visible for all in my template home page. I must set the private post o a password for hide it? Pro version?

Please make sure you aren’t also protecting the same page with a Level based restriction. [hilite path]Dashboard -› s2Member® -› Restriction Options[/hilite]

Also make sure you set a Membership Options page, or the restrictions won’t be applied.

You may also need to configure the Alternative Views restriction so the post is not shown in the home or archives. [hilite path]Dashboard -› s2Member® -› Restriction Options -› Alternative View Protection[/hilite]

I hope that helps! :)

Hi Robb.

You may want to use the users export/import tools. [hilite path]Dashboard -› s2Member® -› Import/Export -› User[/hilite]

I hope it helps. :)

Hi Max.

For that you’d have to set up your WordPress multisite network and then configure s2Member for it. [hilite path]Dashboard -› s2Member® -› Multisite (Config)[/hilite]

I hope that helps. :)

Cool! I’ll be looking forward to your update. :)

Hi Randy.

If you update your Authorize.Net pro-form with the new price, that’ll affect new sales. Existing subscriptions aren’t modified by s2Member, those you need to manage from Authorize.Net itself, which is the one that handles them. You should contact their support rep. to find out how you can do it.

I hope that helps. :)

Thanks, got it.

I created a test user and went to the profile page. In the custom fields section I noticed the error:

Warning: Invalid argument supplied for foreach() in /home/content/25/8474825/html/americanmusclehunks/wp-content/plugins/s2member/includes/classes/custom-reg-fields.inc.php on line 294

And then when saving the profile got the blank page with the errors:

Warning: Invalid argument supplied for foreach() in /home/content/25/8474825/html/americanmusclehunks/wp-content/plugins/s2member/includes/classes/users-list-in.inc.php on line 458

Warning: Cannot modify header information - headers already sent by (output started at /home/content/25/8474825/html/americanmusclehunks/wp-content/plugins/s2member/includes/classes/users-list-in.inc.php:458) in /home/content/25/8474825/html/americanmusclehunks/wp-includes/pluggable.php on line 881

The problem was when saving the changes, not the EOT field in particular, even if you don’t change anything, I got that.

I looked in both files mentioned, and noticed the same foreach for [hilite mono]$GLOBALS["WS_PLUGIN__"]["s2member"]["o"]["custom_reg_fields"][/hilite]. I think the problem is not with the code itself, but with one of the fields in the array.

So I went to look at the fields you created, and the interface to create/edit them is missing from your admin panel. [hilite path]Dashboard -› s2Member® -› General Options -› Registration/Profile Fields[/hilite]

There’s definitely something wrong there.

First I’d like to make sure it’s not the theme or a plugin causing that to be missing, so could you test deactivating the other plugins and changing the theme to the deafult one for a moment and refresh the page to see if you now see the custom fields interface?

If not, since you don’t have the interface, you’ll need to edit them in the database… Go to your phpMyAdmin and browse the options table to find the s2Member fields. If your users don’t have these populated, then you can just delete them, but if your users already filled them out, you may want to try fixing them.

I hope that helps!

Ah, thanks for the update and the input regarding the instructions. I’m glad you sorted it out. :)

Thanks for the screeshot. I look forward to the update regarding the EOT of the log entry’s user.

Since this is about the EOT behavior not happening, I’m suspecting your problem to be related to wp-cron. You can either find what’s causing it or instead use a cronjob outside of WordPress. [hilite path]Dashboard -› s2Member® -› PayPal® Options -› Automatic EOT Behavior -> Enable System[/hilite]

To find if there’s a plugin causing wp-cron to fail, try deactivating them one by one, testing after each a EOT time in the past to trigger the EOT behavior. Or deactivate all plugins except s2Member, test the EOT behavior to confirm it works, and then add the other plugins one at a time.

Please let me know how it goes. :)

Yeah, users with frequently changing IPs can be a problem in this regard.

The unique IP restriction will still be there in the new s2Member being developed, but we’re looking at the possibility of being able to set custom limits for certain users that require it.

Thanks for your input. :)