Last week a colleague sent me an email about a website they had been trying to get up and running and had run into a few problems. After having a poke around under the hood I came across the issues. I’d never seen them before.
WordPress is a really stable platform which I’ve been working with since its early days; I thought I’d seen it all. After trouble shooting, making a few minor tweaks to the core the issue hadn’t resolved.
This left one thing. The issue was with the web host.
I contacted the web host and requested they make the server changes and was promptly told this was a CMS issue and not their problem… I need to say, this isn’t a provider I ever use and after my recent encounter would never use and hell would freeze over before I would recommend them to my worst enemy.
After a phone call and several less than helpful emails, the tech it was escalated to remained absolutely adamant it was not a hosting issue decided it would be helpful to explain: “I am not saying anything bad about wordpress but its a free opensource CMS that we do not support as a hosting provider. …we may not understand how the themes or codes communicate or/how it behaves as we did not made the cms. ” [Ok that’s a fair call. Let’s ignore the typos and poor grammar.]
What really got me was: “Like in my sample mobile phone analogy, we provide the network signal , how the phone device or its software device behaves falls outside the network area.”
At this point smoke was coming out of my ears
Firstly, if you’re going to be condescending you could at least use correct grammar.
Seriously though, using his analogy… if the device and its software works perfectly on another network, which in this case it does, it’s going to be an issue with the network.
We had been backwards and forwards with the whole CMS vs Host for the last two days. Given I had finished half a dozen websites with the same base setup over the past six weeks, I can assure you there was nothing wrong with WordPress, the plugins or the theme. A key reason Across Communications develop with WordPress is that it is robust!
The outcome: we’ve moved the site to HostGator.
HostGator exported all of the email accounts (with the mail files) and the other backend stuff as part of the new account setup (which I may add is significantly cheaper for a better package than the host in question).
The moral of the story:
It’s always recommended you use a host which supports your chosen CMS. It’s ridiculous to think that host don’t support a CMS which is used for over 61 500 000 websites worldwide. But hey they exist.
We always use and recommend HostGator. (Lately we’re recommending a different host: SiteGround) They offer highly competitive hosting rates, out of this world 24/7/365 customer service and technical support. And you guessed it; they support WordPress (and Joomla, Drupal and dozens of other commonly used CMS, moodles, shopping carts and other really cool stuff).
In the interest of being totally transparent, Across Communications do get a small commission for recommending HostGator. That’s not why we recommend them though. We recommend them because simply they’re awesome. And our reputation is worth more than the small commission we get paid.
Rochen is also a good host for WordPress (and we don’t get a kick back for saying that). Personally I find the HostGator service more responsive and their rates are a little bit more competitive.
If you’ve got a pain in the ass web host you’d like to give the flick or a website you’d like to us to have a look at, shoot us an email or give Leigh a call on 0403 515 665.