(Posted by mistake in "Use Cases")

I currently have a "Parent" plan entitled "Regular Subscriptions" under which are grouped three "Child" plans: 3-month, 6-month and 1-year.

My objective is to have my members first choose the "Parent," i.e, "Regular Subscriptions" which then displays the three "Child" plans.

That part works just fine.

But ... my members are ending up with TWO subscriptions, the first being "Regular Subscriptions" (set to "Free" with an initial validity of 30-minutes and unlimited occurrences) and another UNPAID subscription correlating to the appropriate "Child" plan of their selection.

The "Parent" is also displaying "- for Lifetime Subscription, then Free per 30 minutes." which is NOT to be the case!

How am I able to provide my members with the ability to first choose "Regular Subscriptions" ... have that choice then open a "menu" of the "Child" plans, with the member then selecting one of them ... resulting in only one, paid subscription?

Hi. I'm having the same problem but can't seem to figure out the fix.

I have the Parent set to exclusive, non-upgrade, free, lifetime, and have set the price display from [AUTOMATIC] to a space.

I have the child set to exclusive and am allowing upgrade.

This shows up just as I like it, but if I select the child, both the child and the parent are selected.

I would like only for the child to be selected. What am I missing here? Thank you.

The parent is automatically selected, it's required in order to select the child.

If this is the case, the user will be registered for the "divider" category as well as the child category. That will be very redundant in the database, especially under the "Subscriptions" list. This could also cause confusion for the user when the view what plans they are subscribed to.

I suppose I will need to list all of the subscription plans as a separate parent category with no child. Unfortunately, this will not allow me to organize the plans based on similarity, etc.

Is this my only option? If so, do you forsee the possibility in future releases of CB Subs to use a "divider" parent without it creating a registration record in the database? Thank you.