most excellent, removing the {} worked

the only questions remaining... on each renewal, will this same [PLAN_OPTS_OPTION_ADDITIONALLICENSES] parameter work? meaning will it send the same value that it did on activation via the CBSubs Integrations / URL?

if a user wishes to downgrade from 2 to 1 license for example, will they be able to do that via their user profile like normal? will they have to unsubscribe & resubscribe or are they able to upgrade/downgrade?

can we use ADDITIONALLICENSES for other plans as well being the variable name? or should we create different ones for each plan, such as ADDITIONALLICENSESPLAN1, ADDITIONALLICENSESPLAN2, ADDITIONALLICENSESPLAN3 etc.....

i'm editing this because i've found an issue... if current subscribers are on one of the plans, and we have the [PLAN_OPTS_OPTION_ADDITIONALLICENSES] sent to our server via CBSubs / integrations / url, it will not pass a value properly. i've even tried setting the "default" value in the Options & i am concerned that any current member's renewal will not work properly because they don't have a [PLAN_OPTS_OPTION_ADDITIONALLICENSES] value. how can i get a value to be sent via the URL integration for users already subscribed to said plan and renewing? must we create new plans? this seems non-optimal if so.

thank you

krileon wrote:

It's not passed properly how? You mean for users that don't have a plan option value selected? It should just be empty value in that case.

Right, so when the http post is sent, the server is expecting a value. In this case, if it's empty, the server will throw an error.

So for 100% current autorecurring subscribers, this wouldn't work unless a value can be sent. This is what I thought the "Default" option was for on the right side just below the "Blank Text" field. Is there a way you have it send the value we put into this Default field IF it is empty?

For example; we input a default value = 1, then any current subscriber's renewal would send this value of 1 via the URL (https post) unless they've chosen an option. In which case it would send their chosen option as it's doing now.

Basically, we'd love to use this feature but we need it to be backwards compatible with current users.

I'm on it to test, thank you!

Most excellent, this was the trick

One other question, is it possible to send the value across multiple plans? For example, user subscribes to plan1 & later subscribes to plan2.

Could I use the same substitution string in plan1 to pass in plan2?

EX:
When user subscribes to "plan2", pass the data from plan1 as follows?
[PLAN1_OPTS_OPTION_ADDITIONALLICENSES=""]DEFAULT_HERE[cb:else][PLAN1_OPTS_OPTION_ADDITIONALLICENSES][/cb:else][/cb:if]

I realize this may seem a bit strange, but one of our plans is dependant on the initial plan's amount of licenses so we'd like to be able to pass the initial plan's value into plan2's CBSubs / Integrations / URL so it doesn't change when they purchase plan2.