<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>WP Pro - Design, Development and Professional WordPress Hosting for Serious Bloggers &#187; Web Hosting</title>
	<atom:link href="http://www.wppro.org/tag/web-hosting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.wppro.org</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 07 Apr 2010 16:56:14 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Top Reasons to not use Yahoo! Hosting</title>
		<link>http://www.wppro.org/2007/11/29/top-reasons-to-not-use-yahoo-hosting/</link>
		<comments>http://www.wppro.org/2007/11/29/top-reasons-to-not-use-yahoo-hosting/#comments</comments>
		<pubDate>Thu, 29 Nov 2007 16:57:51 +0000</pubDate>
		<dc:creator>Sunny</dc:creator>
				<category><![CDATA[Resources]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Spam]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Web]]></category>
		<category><![CDATA[Web Hosting]]></category>
		<category><![CDATA[WP]]></category>

		<guid isPermaLink="false">http://www.headsetoptions.org/2007/11/29/top-reasons-to-not-use-yahoo-hosting/</guid>
		<description><![CDATA[I try not to write such posts, but the frustrations expressed by my clients who hosts on Yahoo! Small Business compels me to point out the obvious shortcomings of a popular host. This non-exhaustive list is in no particular order, it’s just the top 4 reasons why I would not recommend or host any on [...]]]></description>
			<content:encoded><![CDATA[<div class="span-8">
<p>I try not to write such posts, but the frustrations expressed by my clients who hosts on Yahoo! Small Business compels me to point out the obvious shortcomings of a popular host. This non-exhaustive list is in no particular order, it’s just the top 4 reasons why I would not recommend or host any on my sites on Yahoo!</p>
<h3>One-Click-Install of Outdated Software</h3>
<p>A client recently used the one click install feature to add WordPress to her site, within days it was hacked and she lost everything she had moved from another CMS (luckily she still had her backups). The problem was the defunct version of WordPress that Yahoo! installed; WP version 2.0.2, which beats <a title="al gore wp version" href="http://www.headsetoptions.org/2007/11/27/al-gores-wordpress-powered-site-hacked/">Al Gore&#8217;s hacked sites WordPress version</a>. Yahoo! claims to be partners with WordPress.org and provide search capabilities for the official WordPress sites, yet the version they install on thousands of user sites is full of holes prone to malicious attacks and hijacks.</p>
</div>
<div class="span-8 last">
<img src="http://i71.photobucket.com/albums/i136/headsetop/antiyahooad.jpg" alt="yahoo hosting magic" />
</div>
<div class="clear"></div>
<h3>Forces to use Yahoo! Mail, no PHPMail</h3>
<p>This is somewhat funny and restrictive setup that Yahoo! Hosting has in place to screw users from using phpMail functions. The most common addon on any new WordPress site is the contact form, yet Yahoo! wont allow you to use one. The only situation when it would work is if the from email ID entered in the Contact Form is from the <a title="php main on yahoo" rel="nofollow" href="http://help.yahoo.com/l/us/yahoo/smallbusiness/webhosting/php/php-17.html" target="_blank">same domain as the site you are on</a>. For example, if you are hosting the domain example.com on Yahoo! Hosting, the only people who can use the contact form are those with emails like someone@example.com, essentially email ID&#8217;s set with the same domain! Does that even make sense? Their reason is, if you had access to send emails to and from your site, you might use the privilege to spam someone else. Privilege to Spam? Yahoo! assume that its subscribers are spammers and treat them like one irrespective of if you really are one or not. While there are ways around this issue, it is not worth the time and effort.</p>
<h3>Restrictive Controls and no .htaccess Access</h3>
<p>Although this feature is mostly used by advanced users, they don&#8217;t let users have access to their own .htaccess files. What this could mean is, you are not allowed to set up redirects, and if you do manage to set one up from within the WP install, Yahoo! will delete the file and if you are the &#8216;unlucky types&#8217;, it might even kick you out of the system completely without the opportunity to restore or reverse the .htaccess edits. Lame.</p>
<h3>Customer Support</h3>
<p>I ended up calling Yahoo! on behalf of my client and was on hold for a good 50+ minutes just to hear the guy on the other end tell me he will &#8220;<em>get the engineers to look at the issue the next morning</em>&#8221; and that &#8220;<em>the issue will be resolved in 3 to 5 days</em>&#8220;. I replied (in astonishment) &#8220;3 to 5 days?&#8221; and he replied very calmly, &#8220;that&#8217;s less than a week&#8221; (almost as if service in &#8220;less than a week&#8221; should make me feel special!). Obviously Yahoo! Hosting thinks your site is not important and can be down 5 days, after all, why bother rushing their engineer to look into petty matters when they could be spending it on keeping up the <a title="alexa ranking for yahoo" rel="nofollow" href="http://www.alexa.com/site/ds/top_sites?ts_mode=global&amp;lang=none" target="_blank">number 1 site in the world</a>.</p>
<h3>Need more?</h3>
<p>I&#8217;ll let the readers add the rest using the comment form below.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.wppro.org/2007/11/29/top-reasons-to-not-use-yahoo-hosting/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
	</channel>
</rss>
