Webhosting Features

[cartama]

Shawn,

Biggest problem from the web hoster point of view is that there are only 2 types of service: a domain and an email. The email part seems to work out OK, but for domains there are several types. For instance we have some that are registered through us but there is no corresponding site, some that are parked with us, some that are aliases of other sites, and some that are real web sites. We use the Tag field to distinguish those currently.

But the real problem is when the customer is adding services via the web interface. If he add two products: web hosting and web alias, then adds the domains, Optigold doesn't know which domain corresponds to which product, so there's a manual step by me.

Then if I want to have a search engine submission service, there's no way to make that work. So what we need is for billing cycle items and services to be tied together.

It would also be nice if there was a way to call a custom PHP script to supply some of the options... e.g. if the customer selects windows web hosting, my script could figure out which sever to put the site on, and return a server ID which would go in the Tag field. This would enhance the product enormously.

Mark
Cartama

[digitalpoint]

Agreed... in the new Optigold (rewrite from the ground-up), that's already taken into account. You define the services you offer (including what types of things you want to track for each service) within the system.

[mcolvin]

Now...You knew this question had to come at some point... :-)

Any guesses, and it can be huge ballpark, when some version of the rewrite would be available? Obviously it is a huge process, but are we looking at this year? Summer? Next year?

You've got us all salivating out here!

Mike

[digitalpoint]

None what-so-ever at this point...

But it is coming along nicely so far. :)

[cartama]

Shawn,

Usage is also a problem for web hosts. The way it should be is that the bandwidth and disk quotas should be stored in the billing cycle. The sum of the bandwidth and disk allocations from all the billing cycles in the account should be computed and used for billing purposes. e.g. if I have two domain billing cycle items in an account each with 100MB of disk space, the customer should only be charged an overage fee if he's using more than 200MB of disk.

The way it works now is really awkward since the usage has to be manually updated when extra billing cycle items are added.

Mark
Cartama