Suggestions

[KuJoe]

How about an option that requires the users to verify their e-mails by having an activation code/link sent on account creation?

Some form of CAPTCHA when signing up (to prevent automated sign-ups).

Allowing admins to require an access code to sign-up for certain packages. I used to use this method on another script a while back to make sure users signed up on the forum before they could create an account. I would have an access code and put it in the forum's welcome e-mail. They sign-up with the access code to get a free hosting account.

IP + E-mail banning.

Ability to disable Knowledge Base.

Display IP in client details (possibly have a link to do a whois at whois.domaintools.com or resolve the IP to the ISP/country).

[Nick]

if you want them to sign up for the forums, make it a post2host package with 0 signup/ 0 posts per month.

Just disable the support area to disable the knowledge base.

[KuJoe]

But I like the ticket system, just no use for the knowledge base. I'm trying to avoid doing as much editing to the code as possible to allow for future upgrades, I've already butchered all of the index.php and .tpl files.

[Nick]

if you don't like the knowledgebase, just ignore it.

[KuJoe]

Yes but it looks worse having an empty one versus none at all. I'm not saying it's a major issue, just a suggestion.

[KuJoe]

Another suggestion: Putting in a check in the order form to see if a user is logged in already (if Multiple Signups is set to disabled).

[Nick]

if multiple signups is disabled it will block that person's IP from signing up again, so this is redundant.

[KuJoe]

I know that but if the person changes IPs then the least the script can do is check to see if they are already logged in.

[Jimmie]

Like session checking?

[KuJoe]

I'm not a programmer so I don't know the best method but if it's not to difficult then sure. I understand the code is still new so bugs like this are expected.