Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate w/ Aweber API instead of via Email #303

Closed
clavaque opened this issue Aug 16, 2014 · 38 comments
Closed

Integrate w/ Aweber API instead of via Email #303

clavaque opened this issue Aug 16, 2014 · 38 comments

Comments

@clavaque
Copy link
Contributor

@jaswsinc

This customer reports that his email parser for s2 in AWeber stopped working, and their support told him that email parsers will be phased out. https://websharks.zendesk.com/agent/#/tickets/3496

This customer reports a similar problem: https://websharks.zendesk.com/agent/#/tickets/3356

What should I tell those customers? Maybe we should upgrade the integration using the API instead? https://labs.aweber.com/docs

@jaswrks jaswrks self-assigned this Aug 16, 2014
@jaswrks jaswrks added this to the Next Release milestone Aug 16, 2014
@jaswrks
Copy link
Contributor

jaswrks commented Aug 16, 2014

Yes, I agree. Moving this to the next release milestone.

@clavaque
Copy link
Contributor Author

This ticket may be having the same parsing problem, although he says only the Level 2 list isn't being added to, but Level 0 ones are: https://websharks.zendesk.com/agent/#/tickets/3594

@frosdick
Copy link

frosdick commented Sep 1, 2014

Not sure if this will help but Awber parser should still work if you use Non-Role based emails (EG don't use admin@ info@ webmaster@ etc)

@jaswrks
Copy link
Contributor

jaswrks commented Sep 1, 2014

Not sure if this will help but Awber parser should still work if you use Non-Role based emails (EG don't use admin@ info@ webmaster@ etc)

Thanks for the heads up!
Referencing: http://wordpress.org/support/topic/s2member-level-1-emails-not-being-parsed-to-aweber

@clavaque
Copy link
Contributor Author

clavaque commented Sep 5, 2014

@clavaque
Copy link
Contributor Author

clavaque commented Sep 5, 2014

@jaswsinc Could this parser integration problem be related to this other issue? #260

@clavaque
Copy link
Contributor Author

clavaque commented Sep 5, 2014

@korbal
Copy link

korbal commented Sep 8, 2014

@jaswsinc When is the next milestone due? Thank you!

@jaswrks jaswrks modified the milestones: Next Release, v140909 Sep 9, 2014
@jaswrks jaswrks modified the milestones: Next Release, v140921 Release Sep 21, 2014
@clavaque
Copy link
Contributor Author

@clavaque
Copy link
Contributor Author

clavaque commented Oct 2, 2014

@jaswrks jaswrks changed the title AWeber email parsers phased out Integrate w/ Aweber API instead of via Email Oct 4, 2014
@jaswrks jaswrks mentioned this issue Oct 4, 2014
@jaswrks
Copy link
Contributor

jaswrks commented Oct 4, 2014

TODO:

  • Reorganize list-servers.inc.php; i.e. refactor.
  • Pull AWeber out of list-servers.inc.php and into its own class.
  • Pull MailChimp out of list-servers.inc.php and into its own class.
  • Pull GetResponse out of list-servers.inc.php and into its own class.
  • Pull the latest release of the MailChimp API into the s2Member codebase.
  • Pull the latest release of the AWeber API into the s2Member codebase.
  • Integrate existing code from s2X where we integrated with AWeber's API, and make it conform to the current structure used by the current release of s2Member.
  • Upgrade to latest release of the MailChimp API.

@clavaque
Copy link
Contributor Author

clavaque commented Oct 4, 2014

👍 :)

jaswrks pushed a commit that referenced this issue Oct 4, 2014
jaswrks pushed a commit that referenced this issue Oct 4, 2014
jaswrks pushed a commit that referenced this issue Oct 4, 2014
jaswrks pushed a commit that referenced this issue Oct 4, 2014
jaswrks pushed a commit that referenced this issue Oct 4, 2014
jaswrks pushed a commit to wpsharks/s2member-pro that referenced this issue Oct 5, 2014
@jaswrks
Copy link
Contributor

jaswrks commented Oct 5, 2014

Next release changelog:

  • (s2Member/s2Member Pro) AWeber API Integration: This release of s2Member adds a new option for site owners using AWeber. It is now possible to integrate with the new s2Member App for AWeber; i.e. via the AWeber API instead of via email-based communication. For further details, please see: Dashboard ⥱ s2Member ⥱ API / List Servers ⥱ AWeber Integration. See also: this GitHub issue if you'd like additional details.

@jaswrks
Copy link
Contributor

jaswrks commented Oct 5, 2014

TODO:

  • Update s2Member's inline documentation regarding automatic list transitions. These are now compatible with the AWeber API integration too. In the past AWeber was an exception to the rules detailed there. We can remove mention of that limitation now, as it no longer exists.

jaswrks pushed a commit that referenced this issue Oct 5, 2014
@jaswrks
Copy link
Contributor

jaswrks commented Oct 5, 2014

Next release changelog:

  • (s2Member/s2Member Pro) MailChimp API Wrapper: This release of s2Member comes with an updated API wrapper class for MailChimp integration. No change in functionality, just a smoother, slightly faster, and more bug-free interaction with the MailChimp API. Please see this GitHub issue if you'd like further details regarding this improvement. See also: the official MailChimp API class; i.e. what s2Member has been updated to in this release.

@jaswrks jaswrks closed this as completed Oct 5, 2014
@jaswrks
Copy link
Contributor

jaswrks commented Oct 8, 2014

Reopening. Final testing shows a problem with list server processing.
MC and AWeber are not firing during a free registration.

@jaswrks jaswrks reopened this Oct 8, 2014
@clavaque
Copy link
Contributor Author

clavaque commented Oct 8, 2014

Good catch!

On this same topic, here's an update from this user: https://websharks.zendesk.com/agent/#/tickets/3701

He got some helpful insight from AWeber and it seems that they now have a rule regarding what addresses they accept. They won't add role based addresses anymore because of past trouble they had with those, so now they need to be personal.

I think you should add a note about that in the configuration panel for AWeber in the the List Server API, so the site owner forces personal emails. WP Admin -> s2Member -> General -> Registration/Profile Fields & Options

Otherwise, it's likely those addresses will be rejected even if submitted through their API.

@clavaque
Copy link
Contributor Author

clavaque commented Oct 8, 2014

At least a message is fine, but maybe we can even give a warning if the Force Personal Emails setting isn't configured when the AWeber integration is activated.

@jaswrks
Copy link
Contributor

jaswrks commented Oct 8, 2014

Next release changelog:

  • (s2Member/s2Member) AWeber Role-Based Emails: In this release we're adding a note in the s2Member UI regarding role-based email addresses being rejected by AWeber. AWeber does not allow role-based emails like: admin@ or webmaster@ to be subscribed. It is suggested that you enable s2Member's config. option: "Force Personal Emails" if you intend to integrate with AWeber. Please see: Dashboard ⥱ s2Member ⥱ General Options ⥱ Registration/Profile Fields; where you can tell s2Member for force personal email addresses when someone registers on-site. This will prevent a potential subscriber from entering something like admin@example.com as their email address.

@clavaque
Copy link
Contributor Author

clavaque commented Oct 8, 2014

:)

@jaswrks jaswrks closed this as completed Oct 8, 2014
@clavaque
Copy link
Contributor Author

clavaque commented Oct 8, 2014

I selected the API integration for AWeber and saved without entering the API Authorization Code, and I didn't get any warnings about it.

Also, not important but thought I'd mention it, the new setting to select the type of integration method says "Starting w/ s2Member™ v141005+" but it ended up being released as v141007.

@jaswrks
Copy link
Contributor

jaswrks commented Oct 8, 2014

Also, not important but thought I'd mention it, the new setting to select the type of integration method says "Starting w/ s2Member™ v141005+" but it ended up being released as v141007.

Thanks.

I selected the API integration for AWeber and saved without entering the API Authorization Code, and I didn't get any warnings about it.

Opening a separate issue for this. #359

@diannemclean
Copy link

When I spoke to Aweber yesterday, they did tell me that the parsing is old school and they were planning to do away with it. They tried to get me to do something solely with the Paypal app, which I questioned because of the complexity of s2 member Pro (which I have). So, glad you did an update. However - I did the update today, selected all the API options, copied the key, put my list ID's in the proper place, etc etc - but the issue I am having is that my free members (level 0) who upgrade to level 1, are not getting moved over to the level 1 list on Aweber. I tried it with a dummy account and it still didn't work. Is there a step that I missed??

edited comment - also, I didn't get an email from s2 member that the subscriber upgraded. I only get the paypal notification emails. And I'm not getting an EOT time in the user profile for any upgrades, only new level 1 members.

This has been happening since I upgraded from the free version of s2 to the pro version - I now have over 300 members who have upgraded due to an event that I hosted last month, and none of them got moved to the level 1 member list on Aweber. They are all still on the free list and therefore keep getting emails from me to upgrade, which they don't understand. I would really like to move them over to the upgraded list so they can be emailed in a more unique way!

@clavaque
Copy link
Contributor Author

clavaque commented Oct 8, 2014

Dianne, that sounds like a problem different from the one discussed here. If the user isn't being upgraded, that'd explain him not being moved from one list to the other in AWeber.

Please submit a ticket and I'll help you through the helpdesk. https://www.websharks-inc.com/support/?product=s2member&request_type=trouble_ticket

But to save some time, I'll ask you now to please make sure logging is enabled, to verify your PayPal integration is complete and correct, and to do all the common troubleshooting actions, in that order.

WP Admin -> s2Member -> Logging
http://www.youtube.com/watch?v=SvZxEQjezfY&list=PL8gPolqFnYqsPh9Y0TCjvwLkKuby29SYg
http://www.s2member.com/kb/common-troubleshooting-tips/

Please don't reply to this here, I'll wait for your ticket with the results from the above. Thanks!

@diannemclean
Copy link

I did not say that people were not being upgraded - they are able to
upgrade through s2Member Pro using paypal, etc. They can log in as level
1 members and access all the level 1 content after upgrading. The
PROBLEM is that they are not transitioning from one aweber mailing list
to the next - it has to do with the aweber integration not working
correctly with s2MemberPro for member UPGRADES. It works fine for new
members, but does not manage the aweber lists on the UPGRADES. So - yes

  • this does have a direct correlation with this discussion. It has to
    do with the aweber lists not functioning properly with s2Member Pro.
    All of my paypal API information is correct - I double checked it and
    triple checked it.

You make it WAY too difficult to get help and you assume too much that
people who buy your product know what to do next. I should not need to
hire a developer to integrate aweber properly or have any coding
experience to accomplish this task. Your product is supposed to be "out
of the box". I am capable of following step by step instructions - you
just tend to leave out steps and then the advice that I find on the
forums and "knowledge" base is to hire a developer or do complicated
coding. (by the way, I have searched for HOURS on your forums, boards,
etc to find solutions to these problems.)

Also, if I enable logging, you have a contradictory statement on the
same page as enabling logging warning me not to have logging enabled on
a live site for security reasons. The LAST THING I NEED - after all
this trouble - is to have my members ticked off at me because security
information is exposed. My site is live.

This was working fine before I upgraded to Pro!! I wish I had read your
policies about refunds before upgrading and known how extremely
difficult this is to implement for someone who does not know php code.

Explain to me WHERE to submit a help ticket that doesn't require me to
enable logging on my live site please.

On 2014-10-08 14:41, Cristián Lávaque wrote:

Dianne, that sounds like a problem different from the one discussed
here. If the user isn't being upgraded, that'd explain him not being
moved from one list to the other in AWeber.

Please submit a ticket and I'll help you through the helpdesk. But to
save some time, I'll ask you now to please make sure logging is
enabled, to verify your PayPal integration is complete and correct,
and to do all the common troubleshooting actions, in that order.

WP Admin -> s2Member -> Logging
http://www.youtube.com/watch?v=SvZxEQjezfY&list=PL8gPolqFnYqsPh9Y0TCjvwLkKuby29SYg
[1]
http://www.s2member.com/kb/common-troubleshooting-tips/ [2]

Please don't reply to this here, I'll wait for your ticket. Thanks!

Reply to this email directly or view it on GitHub [3].

Links:

[1]
http://www.youtube.com/watch?v=SvZxEQjezfY&list=PL8gPolqFnYqsPh9Y0TCjvwLkKuby29SYg
[2] http://www.s2member.com/kb/common-troubleshooting-tips/
[3]
#303 (comment)

@diannemclean
Copy link

So I have over 300 people who have upgraded - but they are still on my free member aweber list. So when I send out a marketing email to the 7000 members on my free list, enticing them to upgrade, the people who have already upgraded are confused. Not only that, I can't send them emails through my aweber account which should only go out to the upgraded members. Again, they ARE able to login as level 1 members after upgrading, they are able to view level 1 content. The issue is that level 0 members who are upgrading to level 1, are NOT being moved from the free member aweber list to the upgraded member aweber list. So you still have a problem with your aweber integration.

@diannemclean
Copy link

Also, I'm beginning a training course in a few weeks with over 150 speakers who look to me for advice on how to do what I do. I really really want to recommend s2 Member as their membership program, but if I can't even get it to work correctly for me, I'm not recommending to them. At least not the pro version. The free s2 member worked fine for several years. But since the day I upgraded to pro, I have had nothing but problems.

@wpsharks wpsharks locked and limited conversation to collaborators Oct 8, 2014
@wpsharks wpsharks unlocked this conversation Oct 9, 2014
@clavaque
Copy link
Contributor Author

clavaque commented Oct 9, 2014

Thanks for clarifying that they are being upgraded. I'm sorry I misunderstood your message.

The only thing that gets added with s2Member Pro to the List Servers API, is the GetResponse integration. The rest remains the same, so I'm not sure how the upgrade would have affected list transitions.

Could you verify that your configuration here is correct? WP Admin -> s2Member -> List Servers -> Automate

@diannemclean
Copy link

Yes - I did verify that before contacting you - the automation boxes are
checked off correctly.

This issue with the lists transitioning is only happening with upgraded
members. I have no issues with new members getting on the correct
lists.

The other issue that is happening with upgraded members is that the EOT
is not recording in their profile. But it's fine with new members.

They are required to be logged in as a level 0 member to even access the
upgrade page on my site. So that was something I did think ahead on.

This was all working fine the first week or so of September - before I
did the upgrade from the free version of s2Member to the pro version. I
don't know how it can affect the transitions either, I don't code your
plugin. But somehow that's when things went wrong. I upgraded to pro
after I had the first 30 people upgrade during the special event - it
was one of the first things on my list to do when I started making
money.

So I know the upgrades were working with the free version of s2Member
just fine. They were moved over to the correct list on aweber, and
those first 30 or so upgrades also show the EOT in their profile. But
after I upgraded to s2 Pro, they stopped transitioning to the level 1
list on aweber, and the EOT stopped recording in their profile. I
didn't make ANY changes to buttons or coding or anything. If you will
recall, I sent you a message that I needed more training on the Pro
version because I was intimidated and afraid to change anything. I
didn't realize that they had not moved over until the event was over at
the end of the month and my upgraded members emailed me asking me why
they are still getting solicitations from me to upgrade their account
when they have already done so. It's because they are still on the free
member mailing list.

On 2014-10-09 06:25, Cristián Lávaque wrote:

Thanks for clarifying that they are being upgraded. I'm sorry I
misunderstood your message.

The only thing that gets added with s2Member Pro to the List Servers
API, is the GetResponse integration. The rest remains the same, so I'm
not sure how the upgrade would have affected list transitions.

Could you verify that your configuration here is correct? WP Admin ->
s2Member -> List Servers -> Automate

Reply to this email directly or view it on GitHub [1].

Links:

[1]
#303 (comment)

@clavaque
Copy link
Contributor Author

I replied to your ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants