workflow issue

Hi,

Upgrading a site from 1.5.x to 2.5.x - lots to do! What I did (per client's request and based on suggestion in CB Subs manual) was create a free plan that gives users site registration. The default is the paid subscription plan but the site registration free plan is also available. According to the manual, this is the way to go to allow CB Subs to handle all registration.

The problem is this: When a user registers on the free plan, I've only included certain fields to be available (name, user name, password, email.) If someone wants to then upgrade to a paid plan, the payment goes through okay but the user never gets a chance to included other, membership-type fields. They are locked into the fields that they used during registration.

How do I solve this? I'd like the upgrade to allow the user to include some very important fields in the profile that are not available in the free site registration.

Thanks,
Mark

Workflows tab only controls access to fields on registration. To also protect on profile you need to CBSubs Fields Tabs Protection. When a user is upgrading their subscription there is no registration process and thus no fields. To update the fields they now have access to after an upgrade they need to go to profile edit.

Thank you for your quick reply!

I came to the conclusion you mentioned in your post and so what I've done is limited the pages a registered user can access. A simple registered user can not edit their profile. You have to join the org to have access to that.

Might I humbly request that a fields 'upgrade' be put on the wish list of items for future versions. There's a similar function on SobiPro AFAIK where you charge for fields. Same with DirectoryPress for Wordpress. For orgs that charge extra for URL listings, etc. this makes a lot of sense.

Many thanks,
Mark

The best I can suggest is to use CB Auto Actions or a new CBSubs integration to redirect them to profile edit after a successful purchase. We do not have a partial profile edit page for example. Possibly with a future release of CB we'll have API for this, but I can't make any guarantee.