Aweber Problems Since Upgrade to 111017 and BuddyPress 1.51

[godrob]

Hi Cristian, Jason and anybody else who can help me here...

I seem to be having a problem with registrations no longer being passed through to Aweber. This all worked fine until I upgraded to BuddyPress 1.51 and S2Member Pro 111017 New members still receive their login details via email and can login to the site without issues.

I have checked my listid in Aweber and confirm that it is setup fine in S2Member. I have also tried changing the email parser from 'PayPal' to 'Custom' (using the custom code provided in the forum), but still no joy...

No information is being passed to Aweber since the upgrade.

Just to confirm, I am offering a free 14 day trial on my BuddyPress site and using the pro form to bring registrations into S2member at level 1.

Help someone please? I need Aweber to function correctly as most of my sales come via email marketing.

Thanks
Rob.

[godrob]

I've created the Aweber debug file and added it to the muplugins directory. The information below is what is received back when a member registers with my site:

* I've manually changed sensitive information and preceded it with an *, hopefully this should still make sense? Also, just to confirm that listid@aweber.com matches the listid name setup in s2member and Aweber

Debug Email

Code: Select all

s2Member Subscription Request
s2Member w/ PayPal Email ID
Ad Tracking: s2Member-www.*domain.com
EMail Address: support@*emaildomian.com
Buyer: Rob Smith
Full Name: Rob Smith
First Name: Rob
Last Name: Smith
*IP Address: xx.xx.xx.xx
User ID: 2826
Login: robtest5000
Role: s2member_level1
Level: 1
CCaps:
- end.

Email Headers:

Code: Select all

X-MSK: CML=1.301000
Return-path: <*uname@*websitename.*domain.com>
Envelope-to: support@domain.com
Delivery-date: Fri, 21 Oct 2011 06:24:49 -0500
Received: from *uname by *websitename.*domain.com with local (Exim 4.69)
   (envelope-from <*uname@*websitename.*domain.com>)
   id 1RHDDV-0002g7-MP; Fri, 21 Oct 2011 06:24:49 -0500
To: *listid@aweber.com
Subject: s2Member Subscription Request
Date: Fri, 21 Oct 2011 11:24:49 +0000
From: Website Name <noreply@www.*domain.com>
Message-ID: <4a2cabf1cf9703aa5fbdae7b0aefcecf@www.*domain.com>
X-Priority: 3
X-Mailer: PHPMailer 5.1 (phpmailer.sourceforge.net)
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="utf-8"

[godrob]

I'm such an idiot. Please ignore this post, I've fixed my problem

It turns out there was a typo in my Aweber Custom Email Parser. Instead of:

s2Member Subscription Request

I had

S2Member Subscription Request

If anybody else is having similar issues, make sure you check and double-check your Parser. That said, it still doesn't explain why the PayPal Parser stopped working....

Rob.

[Eduan]

Well, glad you could solve your problem.

[Jason Caldwell]

If anybody else is having similar issues, make sure you check and double-check your Parser. That said, it still doesn't explain why the PayPal Parser stopped working....
Rob.

Regarding the PayPal Parser. The reason we've started asking site owners to use the new s2Member Email Parser, is because some plugins for WordPress modify the From: address used in emails sent by your installation of WordPress. This can break the PayPal Email Parser, which relies heavily on that email header. Please see this post: viewtopic.php?f=36&t=15496#p45312

For the benefit of other readers, please see this post regarding s2Member's Email Parser for AWeber:
viewtopic.php?f=36&t=15496

[godrob]

Thanks Jason!