URL Http Post Not Setting Options Correctly

Hi,
I use the CBSubs URL to send http posts to a server. Everything has always worked except I noticed something today and want to make sure it is setup correctly.

There is a setting to set how many licenses a user has per product. It passes this to the server via http post. Here is the option you gave me before and as far as I know, it's always worked so a bit confused as to why this didn't.

EX: user had previously purchased this plan with 1 license (this is an option with a value = 1). user purchased again with 2 licenses (this is an option with a value = 2).
- so the http post should have passed a value = 2, but instead it didn't update the value from 1 to 2, therefore the server received a value of 1.

Here's the code for this http post being passed: licenses_allowed=[cb:if PLAN_OPTS_OPTION_LICENSESRENEW=""]1[cb:else][PLAN_OPTS_OPTION_LICENSESRENEW][/cb:else][/cb:if]

Is there something wrong or some reason this would not have properly updated the value = 2? Also, in this if/else condition.... is it stating IF value = null on the server OR IF value = null in CBSubs? In this case, it should have had a value in both places of 1, but should have overwritten it with 2, correct?

Thank you and look forward to hearing back.

I can further confirm there is an issue somehow. Just had another user who renewed & previously had 2 licenses. When they renewed, they selected 1 license, however the value wasn't updated server side.

So somehow the value is not being passed correctly. Can you see some issue with the aforementioned code?

I just need it to always pass a value which is specified in the options/value. AND if there isn't currently a value stored (meaning they've never purchased any of the options previously), it should be able to somehow get the new value and send it.

Strange, seams to be working fine in my tests using CBSubs Emails to email me the option value. Also appears working fine when setting to a field. Are you sure it's not whatever you're sending the HTTP request to that's the problem?

You bet, it is updating all the other fields appropriately and not throwing any errors at all. For whatever reason, this is the only value it isn't updating correctly.

Let me do a thorough run through of the code server side. I will make sure there isn't something that could be missing the incoming data.

I will update in just a bit. Thank you for your patience!

I sincerely apologize, it looks like there was something on our end. I will confirm 100% on the next user update, but from our testing, it's good.

Basically, we needed to make an update to accept the new options since they were added into CBSubs as they weren't needed server side prior to the options because the value never changed per plan.

Sorry again, I'll keep a close eye on it