CBSubs PostAfPro plugin except for staff

Well these codes with substitutions are the code you gave me more than a year ago in order to get the correct affiliate ids

Can you tell me what to do at this stage ?
Is this possible to add an auto action to this integration to achieve what we want ?
Meaning overwriting a cookie when the affiliate code is manually inserted in the registration form or found in CB table when updating a subscription ? And avoiding this when a mod is manually subscribing a customer.

For now, the affiliate id is only one field in the CBSubs plan.
What we want to do is make it dynamic so that this field is either a CB field for an existing customer, or is taken from the cookie with an ability to be manually overwritten on the registration form.



Thanks for the help on this, we have been struggling with this for months

Well these codes with substitutions are the code you gave me more than a year ago in order to get the correct affiliate ids

Don't recall what I did a year ago, but have a hard time believing I gave you obviously non-working code.

Can you tell me what to do at this stage ?
Is this possible to add an auto action to this integration to achieve what we want ?
Meaning overwriting a cookie when the affiliate code is manually inserted in the registration form or found in CB table when updating a subscription ? And avoiding this when a mod is manually subscribing a customer.

Depends on what you're trying to do. Still trying to understand what it is you're attempting. You want to use the fields value as the affiliate id if supplied otherwise use the cookie? However, if the user is a moderator you want it to ignore the cookie and only track if the field has a value in the case of moderator? In onCPayBeforeStorePaymentBasketUpdated is where you'd handle switching between the field value and the cookie as needed, but you need the field value of the basket user and not of the viewing user. So something like the below probably.


That only handles the setting of the postafpro_affiliateid to the basket though. You need to next make sure the affiliate tracking is blocked entirely if postafpro_affiliateid has no value and the user is a moderator as PDTs will still cause PostAfPro to pick up the cookie (I guess you could expire it at this point, but it'd be more reliable to just handle these checks in PHP). That check would need to be added to onCPayAfterPaymentStatusUpdateEvent where it adds the $affiliateID. Something like the below probably.

FROM: TO:
Please note this is just an example and was not tested. Please test thoroughly and adjust as needed.

Yes this is what I want to achieve.
Will test this and thanks a lot for the hints.

May I suggest that it would be perfect if this file could be overwritten by an auto action or an override ? so that it can be kept modified at each upgrade ?

Thanks anyway

You can rename the files, the PHP class name, and adjust the XML file accordingly so it becomes your own installable plugin.

Coming back on the code you suggested, it seems to work fine for the cases when the field value is provided either on the registration page, or is already set in the client profile when this is an upgrade.

But when a moderator tries to register a new customer without the field value, the moderator's cookie is still used.

We add the PAP tracks code on our pages, could it interfere with the postafpro plugin ?
I also tried to cancel the cookie with :
But no chance neither, the cookie is still there in the browser

I don't understand where I miss the point...

With the above code I've supplied the postafpro_affiliateid basket value is never set for moderator usage if the field value isn't supplied then before it logs the commission it checks if postafpro_affiliateid has a value and if it doesn't and the user is a moderator it terminates the process there. The below is what terminates the commission process.

FROM: TO:
Most likely what your issue is is the basket is being paid via IPN and not PDT. This means the IPN user is of course not a moderator so the process never terminates, but IPN case shouldn't have a cookie to begin with so that really shouldn't be logging anything either. At any rate you can try the below.

FROM: TO: