Why so many inconveniences?

[John 18]

Since I started one month ago, I find so many inconveniences with your hosting that I don't have with many other hosting companies. If I had not paid for a year, I would probably leave. But I think you all are a hard working bunch so perhaps you may want to look into improving your hosting so that a user has an easier time.

Some of the problems that frustrated me:

1. Activating or updating Awstats - I have to keep writing to ask to update each domain. Too much trouble. I have written again and again to your support. They are very good but each time they only do the domains I request for. Why can't you do it automatically? My friends who bought single domain hosting also had problems about activating.

2. RSS - Why the need for the ini files. I never have to do that before.

3. Shopping cart - also I need to register globals. etc.

But at least your support has been very prompt.

TQ

[tjplaw]

I don't know how much experience you have with web hosting or website ownership, but WHB couldn't make it any easier for it's clients.


1. Activating or updating Awstats.
How simple can this be. Just log into your Cpanel, scroll to the bottom,
click Statistics Software Configuration. Place a check next to the stats software you wish to use. I believe that the stats are updated every 24 hours, why would you need to check stats more than that?


2. RSS - Why the need for the ini files. I never have to do that before.
I'm no expert in RSS, personally I think that RSS feeds are a bloat for servers.
Unless you own a big news website or sell popular products, RSS is worthless.
If I want to keep updated on the news, I will visit the website.

Doesn't the use of ini files work well using cold fusion?

3. Shopping cart - also I need to register globals. etc.
I believe that this is a requirement using PHP 5? "Note the Question Mark"

Isn't the use of register global bad, I mean unsecure.
Honestly, register globals should always be off.

I do agree that WHB's support is fast. I would say Top Notch.

I've used over 20 different web hosts over the years, and prompt customer support has always been my deciding factor in choosing a web host.
You made the right choice in choosing WHB.

[JasonD]

Globals are bad...

INI is a good thing, and a requirement for virtual servers, with virtual directories. (A requirement, because folders are not real, related to location, and the main host would have to update on every change, which is a security issue, if you are able to edit the main servers ini files. PHP does not use a master file for sub-dir. It is inefficient to process 180 commands in every dir. It is logical to only use commands that pertain to that dir.)

RSS is bloat, only when it comes to code, and processing. The actual micro-text is marginal. It is the updates and processing that kills. (You are right, if you have to get a message out to 1,000,000 users... then it is NOT bloat, it is a bloat saver. If you only have 300 visitors, it is borderline.)

I agree, some things can be elaborated on better, but there is a lot going-on that is made easy. (Simple sites, just don't have the functionality that is offered here. Hard to find a prefab that "Does it all", this one comes close.)

Hope you get all that figured-out. (I would not use anything that REQUIRES GLOBALS. They are placing your account at risk. Write them, and tell them to update to the latest security, and to stop using ghetto programming techniques that put you at risk. Globals danger was KNOWN since php 2, and even PHP tells you to turn it off. Globals are only safe on Intranet, and intended for SECURE servers, not www internet use.)

You should NEVER EVER EVER EVER use globals on a shared server, or a non-ssl server. Every person that shares your server can see your data. (Shared servers have 2-2000 other websites on a single computer, and they all have access to ANY GLOBALS. Thus the term, GLOBAL. Fine if you own all the other 2000 websites, and need to share that info. Not fine if those other sites are strangers. One could be a hacker, waiting for CC info to come through.)

You need a dedicated IP package for a SSL connection. Then globals are safe to use, if you only use SSL connections for that entire server, on every page, with every transaction.