-
Notifications
You must be signed in to change notification settings - Fork 36
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
Comments
Yes, I agree. Moving this to the next release milestone. |
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 |
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! |
@jaswsinc Could this parser integration problem be related to this other issue? #260 |
@jaswsinc When is the next milestone due? Thank you! |
TODO:
|
👍 :) |
Refactor `list-servers.inc.php`. See: wpsharks/s2member#303
Next release changelog:
|
TODO:
|
Next release changelog:
|
Reopening. Final testing shows a problem with list server processing. |
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. |
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. |
Next release changelog:
|
:) |
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. |
Thanks.
Opening a separate issue for this. #359 |
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! |
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 Please don't reply to this here, I'll wait for your ticket with the results from the above. Thanks! |
I did not say that people were not being upgraded - they are able to
You make it WAY too difficult to get help and you assume too much that Also, if I enable logging, you have a contradictory statement on the This was working fine before I upgraded to Pro!! I wish I had read your Explain to me WHERE to submit a help ticket that doesn't require me to On 2014-10-08 14:41, Cristián Lávaque wrote:
|
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. |
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. |
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 |
Yes - I did verify that before contacting you - the automation boxes are This issue with the lists transitioning is only happening with upgraded The other issue that is happening with upgraded members is that the EOT They are required to be logged in as a level 0 member to even access the This was all working fine the first week or so of September - before I So I know the upgrades were working with the free version of s2Member On 2014-10-09 06:25, Cristián Lávaque wrote:
|
I replied to your ticket. |
@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
The text was updated successfully, but these errors were encountered: