infoteam wrote:

i'm trying to utilize the "Url of plan to display only this plan (',' to display multiple plans):" option under cbsubs 1.0.1 to display a registration form specifically for users to be able to see without it being on our registration or upgrade form?

What state does the settings need to be for me to send out the link and people be able to see it?

Thanks!

sorry, there is an error in the online help text.

Use '-' instead of ',' (see it in action here in "Buy CBSubs" button-link in left column).

FIxed for shortly upcoming CBSUbs 1.0.2.

You can't hide the plan entirely to my knowledge and still have the plan active at the same time. You can hie it from registration and upgrade unless a link is provided; this is done from workflows tab, but I do not believe you can hide it from everyone except when provided by a link.

infoteam wrote:

Thanks! I believe I got working what I needed to get working thanks to the missing info in the documentation.

May I suggest you make the change on the appropriate location for the next service release on the page itself and update the docs as well? It would have saved me a bit of hassle and hair pulling. I'm making myself bald at 35!


Thanks!

Yes, CBSubs 1.0.2 will fix the comment and the documentation.

You can't hide the plan entirely to my knowledge and still have the plan active at the same time. You can hie it from registration and upgrade unless a link is provided; this is done from workflows tab, but I do not believe you can hide it from everyone except when provided by a link.

You can hide individual plans from being proposed spontaneously by CBSubs starting in CBSubs 1.0.1:

There are 2 new settings in Plan -> Workflows:

- Propose spontaneously plan at registration
- Propose spontaneously plan for upgrades

Just set both to NO and the plan won't be proposed spontaneously, but only with the links containing it specifically.

They are documented in the use cases page 193, 199, 203, 209, 226-229.
We will also add them to the main pages in CBSubs 1.0.2 documentation.

Thanks for reporting back that those items need to be fixed respectively added to the documentation.