RE: What is the best way to lock an application down using CB Subs

Hi,

I should appreciate it if someone could suggest to me a good way to prevent people under the age of 21 from either accessing a certain application on the site or preventing them from being able to click on a specific link that takes them to the providers site requesting for card payments to play for real money. We intend to make the "age" field mandatory so hopefully that could work in our favor here when implementing a solution.

Is there a method where one could lock down a specific application/menu/button or component using CB Subs?

Thanks
Fuquan

I recommend reading your CBSubs documentation which you can download from the CBSubs GPL downloads section for various usages. CBSubs won't be able to popup some sort of age verification, but it can present a page for them to subscribe when accessing XYZ page (you can protect URLs, modules, articles, entire extensions, and more). Age verification can be dealt with by having a date of birth field that's set to required. You could also use a terms and conditions fieldtype to have them agree to your terms that they guarantee they're of age.

Thanks Kyle, I see potential for working out a solution in the options you mentioned one just has to work his head around the most optimal way to achieve the desired result using one (or a combination) of your suggestions. Oh! by the way, have you updated the CBSubs manual to be reflective of 4.0? as I do have the CBSubs manual but the only impairment there is to using it is that the look and feel represented in the manual is for version 3.0 and it often ends up confusing one (and adding additional time/effort) when trying to map it with 4.0 which looks different.

Anyway, I will have to play around with the suggestions you proposed. Thanks and do have a pleasant day!

Thanks Kyle, I see potential for working out a solution in the options you mentioned one just has to work his head around the most optimal way to achieve the desired result using one (or a combination) of your suggestions.

Most sites just do this via a terms and conditions and is probably the easiest to get up and running as it's just a single field. The alternative is a date of birth field which is also fairly easy to setup. For the date field you'd adjust the minimum year so they couldn't select anything less than 21. There's probably some other solutions, but the complexity just gets higher from there. For example you could allow any age at registration then use CB Auto Actions to redirect away on login attempt or something.

Oh! by the way, have you updated the CBSubs manual to be reflective of 4.0? as I do have the CBSubs manual but the only impairment there is to using it is that the look and feel represented in the manual is for version 3.0 and it often ends up confusing one (and adding additional time/effort) when trying to map it with 4.0 which looks different.

CBSubs 4.x at this time is primarily bug fixes. Usability wise there's no difference between 3.x and 4.x so the current documentation should be fine.