|Posted: Sunday Dec 16th, 2012 at 9:58 pm #34800|
I put in the auto-login hack mentioned several times on this forum (e.g. http://www.s2member.com/forums/topic/auto-login-code-question/). I use PayPal Pro Forms. In addition to interrupting redirection to the url in the “success” parameter, I found that it also gets in the way of tracking and notifications.
To get around this limitation, I tried using API Notifications. However this would only work when a user is already registered and logged in *before* checking out with PayPal Pro Forms. If they were registering at the same time, then the notification urls are never hit. I set notification urls for both Sign Up Notifications and Payment Notifications. Neither are hit.
When I delete the auto-login hack, the Payment Notification is hit. Which is good. Surprisingly, the Sign Up Notification isn’t hit. I thought that if a user signed up and paid in one go then both notifications would be hit?
1. Is there a way have auto-login AND notifications at the same time? Any leads I should investigate?
2. Is there a chart somewhere that lays out which notification and tracking will be hit for a particular action. For example, a table with all the notifications and tracking triggers in the first row, user events like registration and payment on the first column, then true/false in the table indicating whether the given user event will trip the given trigger. This would be enormously helpful in understanding if I am seeing expected behavior or if something is wrong.
- s2Member® Products