Re: Feature Request: entire "custom" string as a token

2012-01-05T02:35:21-05:00

Thank you for the heads up Raam, and @detheir, thanks for the great idea.

I'll certainly add this to our TODO list for a future release.

Statistics: Posted by Jason Caldwell — January 5th, 2012, 2:35 am

Re: Feature Request: entire "custom" string as a token

2012-01-03T17:56:40-05:00

Hi dethier,

Thanks for the suggestion! I will forward this along to the lead developer.

Statistics: Posted by Raam Dev — January 3rd, 2012, 5:56 pm

Feature Request: entire "custom" string as a token

2012-01-03T14:00:32-05:00

Currently with the notification API you allow users to include various custom values using "cv1", "cv2" etc. However, I'm implementing a solution that could have a varied number of custom values and so I can't reliably create a notification url using your existing tokens to account for all the possible numbers of custom values.

The solution I'm using right is just to use your built-in hooks in the payment processing to capture the custom vars and do my processing there, however, it was a real pain to discover all the variables available to me and even with the hooks I'm concerned that future updates to s2member will create a maintenance headache for me.

A better solution would be if you can provide a token for sending the entire "custom" string via the notification api url (i.e %%custom%%), then I can just do my processing on the script I have at the url.

I'd LOVE it if you could implement this in the next release. It wouldn't be hard to add.

Statistics: Posted by dethier — January 3rd, 2012, 2:00 pm

Community Support Forums

Re: Feature Request: entire "custom" string as a token

Re: Feature Request: entire "custom" string as a token

Feature Request: entire "custom" string as a token