<?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>WordPress Web Hosting &#187; Foundation</title>
	<atom:link href="http://www.shrewdies.net/host/host/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.shrewdies.net</link>
	<description>Business Web Hosting For Shrewdies Not Dummies</description>
	<lastBuildDate>Fri, 13 Jan 2012 14:33:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Website Health: A Long Way To Go</title>
		<link>http://www.shrewdies.net/1730/website-health-a-long-way-to-go/</link>
		<comments>http://www.shrewdies.net/1730/website-health-a-long-way-to-go/#comments</comments>
		<pubDate>Sat, 07 Jan 2012 09:22:26 +0000</pubDate>
		<dc:creator>Keith from shrewdies</dc:creator>
				<category><![CDATA[Foundation]]></category>

		<guid isPermaLink="false">http://www.shrewdies.net/?p=1730</guid>
		<description><![CDATA[Since my last post here, my personal health has deteriorated, and my website health has suffered as a result. A few days after my last post, a fall resulted in a broken back, a broken skull, a broken knee, and broken dreams. But 2012 is the year to set all that aside. A time to [...]]]></description>
			<content:encoded><![CDATA[<p>Since my last post here, my personal health has deteriorated, and my website health has suffered as a result.</p>
<p>A few days after my last post, a fall resulted in a broken back, a broken skull, a broken knee, and broken dreams. But 2012 is the year to set all that aside. A time to fix the health of this website, and improve the health of all my visitors.</p>
<p>In a new project, I am working on bringing health freedom to people, their businesses, and their networks. I will share more of that with you as that develops, but since this website is here to support everyone who is responsible for building and operating websites, let me focus on website health here today.</p>
<p>There is a lot of confusing information about the way to test the health of your website. Various technical experts offer different views on the importance of many aspects of page structure. Various marketeers offer different views on the importance of many aspects of search engine optimization. Various online checkers have different methods for analyzing your page health. It is very easy to lose focus. We spend more time monitoring, analyzing, and improving, but that distracts us from the important job of delivering an easy-to-navigate website to as many people as possible.<br />
<span id="more-1730"></span></p>
<p>I have recently discovered the best tool to help webmasters since Google shared it&#8217;s vital Webmaster Tools. This new tool is only available to Firefox users at the moment. But then again, so am I.</p>
<p>Actually, that last bit is not strictly true, because I&#8217;ll work for anyone. However, I believe Firefox is the best browser for website building. Chrome is improving, and I also retain Microsoft Internet Explorer for testing. But successful webmasters are productive webmasters, so stick with whatever works for you. I use Chrome and Firefox together everyday. You are going to have to install Firefox if you want to take advantage of the tool I am about to describe. Other browsers may be covered in future releases.</p>
<h2>Your Website Health</h2>
<p>Before I start, I should warn that the following tool will not fix a bad site structure. If you have ignored my advice about a good website structure, then you will always be tending a sick donkey, compared to a thoroughbred race hound. I cannot blame you too much for not having a good plan, as I have not finished my articles about how to generate one on my management website. Let&#8217;s leave that one for now.</p>
<p>The tool you need for better website health is the aptly named <a href="http://www.prelovac.com/vladimir/browser-addons/seo-doctor" title="SEO Doctor">SEO Doctor from the exotically named Vladimir Prelovac</a>. Once installed as an add-on to your Firefox browser, SEO Doctor analyzes every page as it loads, giving you vital information about the health of your web pages. You get bonus points if you follow Vladimir&#8217;s advice:</p>
<blockquote><p>SEO Doctor works really well with <a href="https://addons.mozilla.org/en-US/firefox/addon/321/">Search Status</a>, in fact these may be the only two SEO extensions you will ever need in your browser.</p></blockquote>
<p>Actually they might be the only ones you NEED, but if I ever share my own add-on list with you, they will not be the only ones you WANT.</p>
<p>Over the next few days, I will describe the tests that SEO Doctor performs, and explain why they are important to you. In the meantime, there is excellent help built-in, and that includes links to Vladimir&#8217;s website for a more thorough explanation. Or, if you are stuck, or need any other help, please ask in the <a href="http://shrewdies.org/13/discuss-website-health/" title="Discuss Website Health">website health forum</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shrewdies.net/1730/website-health-a-long-way-to-go/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Google Tools To Enhance WordPress Installation</title>
		<link>http://www.shrewdies.net/1692/google-tools-to-enhance-wordpress-installation/</link>
		<comments>http://www.shrewdies.net/1692/google-tools-to-enhance-wordpress-installation/#comments</comments>
		<pubDate>Tue, 05 Apr 2011 16:33:22 +0000</pubDate>
		<dc:creator>Keith from shrewdies</dc:creator>
				<category><![CDATA[Foundation]]></category>

		<guid isPermaLink="false">http://www.shrewdies.net/?p=1692</guid>
		<description><![CDATA[In today&#8217;s page about installing WordPress, I&#8217;ve mentioned some essential tools. I&#8217;ve selected Google versions since they are free, effective, and easy to implement. As I mentioned, these tools are so easy to use, they do not really merit step-by-step instructions, though I will do this for some of the reporting features that I use [...]]]></description>
			<content:encoded><![CDATA[<div class="kctIntro">
<p>In today&#8217;s page about <a href="http://www.shrewdies.net/hosting/wordpress-installation/" title="WordPress Installation">installing WordPress</a>, I&#8217;ve mentioned some essential tools. I&#8217;ve selected Google versions since they are free, effective, and easy to implement.</p>
</div>
<p>As I mentioned, these tools are so easy to use, they do not really merit step-by-step instructions, though I will do this for some of the reporting features that I use elsewhere. The tools are important, as they give you management tools (covered at <a href="http://shrewdies.com/">Shrewdies Web Business Management</a>), and technical development tools covered throughout this site.</p>
<p>Of course, you may prefer tools from other companies, and I&#8217;m always happy to discuss the comparison, or help with other tools. Just use the forum to discuss alternatives, or ask for help.</p>
<p>The essential tools I cover here are Google Analytics, and Google Webmaster Tools. </p>
<p>Analytics gives you vital information about how traffic arrives at your site, where it comes from, and what happens to your visitors once they arrive at your site. Though much of this is for management use, technicians will find some of the information crucial for making decisions about navigation. Note that Analytics cannot be used on WordPress.com sites, which do have some free site usage statistics, but none that will help you monitor navigation paths.</p>
<p>Webmaster Tools gives you a wide range of information about site performance and interaction with the rest of the Internet. Though some of this is vital for management use, most of it is crucial to technicians to determine and fix weaknesses, and to make the most of your strengths.</p>
<p>The implementation screens for both these services are very simple, so I will not spend much time explaining them. There is plenty of flexibility about the way you enable them, and I will present what I believe is the optimum sequence.</p>
<h2>Google Analytics</h2>
<p>It pays to start with Analytics, as Google will use that account to verify Webmaster Tools later (though there are several other options). Once your Google account is open, you need to add a new Profile in Google Analytics, and you need to choose the option for a new domain.</p>
<p>Your first question, after entering your website domain address, is to choose a time zone. As all information is summarized by day (and other time intervals), you need to choose something that suits you best. This is normally your local time zone, but if your market is predominately located elsewhere, then it might help to chose that location. Ideally, you would choose the same timezone as your webserver location, but this is not critical. I find that, once in use, most of your time is spent comparing current time periods with historical positions to see if you are improving, so it doesn&#8217;t particularly matter where each day starts. If you plan to use AdSense or AdWords on the same website, then it really does help to have consistent timezones, but it will not harm you if you do not.</p>
<p>Note that the Country selector is a little strange &#8211; common countries are listed at the top, followed by less populous countries.</p>
<p>After entering your timezone, the next screen gives some code to add to your website.</p>
<p>The simplest way to add this to your website is to copy the code, and add it to the footer.php file in your theme (Admin &#8211; Appearance &#8211; Editor &#8211; footer.php). This has drawbacks because it means you have to repeat this edit if you change your theme, and you cannot easily use advance features without adding your own PHP or JavaScript code.</p>
<p>The better way is to use a WordPress Plugin to add Analytics code to your site simply by setting your profile Web Property ID, and other optional choices. I&#8217;m currently testing three plugins on various websites, and will report back on them in due course. In the meantime, you can discuss your own plugin choice or experiences in the Hosting forum.</p>
<p>Once your plugin options have been set, and your site starts generating traffic, and this will be monitored by Google Analytics. Remember, if you have set options not to track your own visits, you will not generate any Analytics data until you, or somebody else, visits the site without being logged in. There will be a few minutes delay between your first visit, and the Analytics screen reporting you as verified. As ever, if you have problems, please use the hosting forum.</p>
<h2>Google Webmaster Tools</h2>
<p>On your self-hosted WordPress.org website, enabling Google Webmaster Tools is as simple as adding the site URL, and choosing the &#8220;Link to your Google Analytics account&#8221; option. (Update: for this to work, it requires Asynchronous Analytics code <strong>in your page header</strong>. Not all plugins do this, as you will see in my forthcoming review, so probably best to choose one of the other options &#8211; I prefer uploading a file. I will do a further in-depth report on Webmaster Tools soon)</p>
<p>If you have a free WordPress.com site you can enable WebMaster Tools by choosing the &#8220;Add a meta tag to your site&#8217;s home page&#8221; option. This will reveal  a meta tag, and you need to highlight the content part of that tag &#8211; excluding the quotes. Paste this into the Tools (Admin &#8211; Tools) box labeled &#8220;Google Webmaster Tools&#8221; and save your changes.</p>
<p>For both these options, you click the Verify button next, and Google will report your site as verified, though you might have to wait a few minutes.</p>
<p>Though neither of these tools will provide much value until you publish some pages, you will soon find the data, especially from Webmaster Tools, to be indispensable. Please discuss your experiences with these tools, and any other similar services, on the <a href="http://www.shrewdies.net/web-hosting-forum/host-forum/">hosting forum</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shrewdies.net/1692/google-tools-to-enhance-wordpress-installation/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simple:Press Forum &#8211; Is The Best Good Enough?</title>
		<link>http://www.shrewdies.net/1610/simplepress-forum-is-the-best-good-enough/</link>
		<comments>http://www.shrewdies.net/1610/simplepress-forum-is-the-best-good-enough/#comments</comments>
		<pubDate>Fri, 28 May 2010 16:34:36 +0000</pubDate>
		<dc:creator>Keith from shrewdies</dc:creator>
				<category><![CDATA[Foundation]]></category>
		<category><![CDATA[Simple:Press]]></category>
		<category><![CDATA[WordPress forum]]></category>
		<category><![CDATA[WordPress setup]]></category>

		<guid isPermaLink="false">http://www.shrewdies.net/?p=1610</guid>
		<description><![CDATA[Simple:Press Forum is definitely the best forum software I&#8217;ve used for WordPress. There is no WordPress plugin to touch it, and the alternatives are simply too cumbersome to integrate. For most needs, Simple:Press forum provides all that you need, but I&#8217;ve also mentioned before that it is not as simple to administer as some &#8211; [...]]]></description>
			<content:encoded><![CDATA[<div class="kctIntro">Simple:Press Forum is definitely the best forum software I&#8217;ve used for WordPress.</p>
<p>There is no WordPress plugin to touch it, and the alternatives are simply too cumbersome to integrate.</p></div>
<p>For most needs, Simple:Press forum provides all that you need, but I&#8217;ve also mentioned before that it is not as simple to administer as some &#8211; but only because it has a wealth of options. And under the lid, tweaking the code is not particularly easy &#8211; again because there is so much included that it can be hard to find exactly what you want to change.</p>
<p>Mechanics aside, I have been trying for months to develop a simpler alternative built on posts and comments. This is not the most difficult coding challenge, but it is time-consuming, and there always seems something more important to do. Whilst doing the more important things, I noticed that Pods CMS has recently changed there forum for a completely different, simpler interface.</p>
<p>Looking deeper, I saw that it was based on Stack Overflow. Similar, in some ways, to Yahoo Answers, this approach means that we can focus on answering questions. This is a bit of an eye-opener for me, and I realize that promoting a forum to answer questions and share experiences and opinions is asking too much for one application.</p>
<p>I&#8217;ve decided to split my forum into a Question And Answer Section and a Discussion Forum. In an ideal world, these would be linked, and it would be absolutely possible to build such a beast with Pods CMS. But the time to build this from scratch means I&#8217;d rather look for something usable now, and seek better integration later.</p>
<p>The key here is to find something usable that is easily integrated into WordPress.</p>
<p>Step forward Question2Answer.</p>
<p>I&#8217;ve installed it on own of my sites, and I&#8217;ll report back on the details later. I&#8217;ve no intention to import questions from Simple:Press Forum, as I believe the two applications can work side by side. There will probably be a few more integration issues, but installation of Question2Answer using the WordPress user records was surprisingly easy.</p>
<p>Rather than repeat it here, I&#8217;ll refer you to my <a href="http://www.question2answer.org/qa/428/how-can-i-integrate-it-with-wordpress">Question2Answer WordPress installation notes</a> on the author&#8217;s support site.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.shrewdies.net/1610/simplepress-forum-is-the-best-good-enough/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>wp-config.php Essentials</title>
		<link>http://www.shrewdies.net/452/wp-config-php-essentials/</link>
		<comments>http://www.shrewdies.net/452/wp-config-php-essentials/#comments</comments>
		<pubDate>Sat, 01 May 2010 16:51:43 +0000</pubDate>
		<dc:creator>Keith from shrewdies</dc:creator>
				<category><![CDATA[Foundation]]></category>
		<category><![CDATA[Install WordPress]]></category>
		<category><![CDATA[WordPress setup]]></category>

		<guid isPermaLink="false">http://www.shrewdies.net/?p=452</guid>
		<description><![CDATA[wp-config.php is essential to WordPress. For manual installers, it is set and forget. For automatic installers (SimpleScripts or Fantastico) it is often quite invisible. wp-config.php WordPress Memory Post/Page Revisions wp-config.php Changes Unless something unexpected changes, WordPress 3 adds little different to the way wp-config.php works, so it is still vital to learn a couple of [...]]]></description>
			<content:encoded><![CDATA[<div class="kctIntro">wp-config.php is essential to WordPress.</p>
<p>For manual installers, it is <em>set and forget</em>. For automatic installers (SimpleScripts or Fantastico) it is often quite invisible.</p>
<div style="float:right;border:.1em solid #00009e;background-color:#9e9eff;margin:.7em;padding:.7em;width:38%;color:#00009e;">
<h4>wp-config.php</h4>
<ul>
<li><a href="http://www.shrewdies.net/452/wp-config-php-essentials/#memory">WordPress Memory</a></li>
<li><a href="http://www.shrewdies.net/452/wp-config-php-essentials/#revisions">Post/Page Revisions</a></li>
<li><a href="http://www.shrewdies.net/452/wp-config-php-essentials/#changes">wp-config.php Changes</a></li>
</ul>
</div>
<p>Unless something unexpected changes, WordPress 3 adds little different to the way wp-config.php works, so it is still vital to learn a couple of tweaks.</p></div>
<p>wp-config.php is well documented internally, and the installation instructions tell you what you need to change to make sure that your WordPress installation can see the database.</p>
<p>But, there are two situations that commonly occur in a standard WordPress installation that are far from ideal: memory exhausted messages and excessive page and post revisions.<br />
<span id="more-452"></span></p>
<h2 id="memory">WordPress Memory Problems</h2>
<p>I have mentioned <a href="http://www.shrewdies.net/261/wordpress-upgrade-2-9/">memory problems with WordPress</a> before. Though I only experienced it when upgrading with large plugins like Simple:Press Forum installed, I suspect this can also happen during normal running of some large plugins. Pods CMS has an error report, but as it looks to be a one-off, it could well be due to some other problem.</p>
<p>When I first experienced this problem, I used the temporary solution of de-activating large plugins during the upgrade. However, I later found the permanent solution to be an amendment to wp-config.php, as I noted on the original post, and repeat below.</p>
<h2 id="revisions">Excessive WordPress Revisions</h2>
<p>When WordPress introduced automatic saving of posts with revisions, it looked perfect for undecided people like myself. Changed a post only to realize you prefer an earlier version? No problem with WordPress, as the default installation settings give you a more or less complete revision history. But this can cause a problem if you frequently revise many posts and pages. Not only can you end up with a massive list of revisions on the edit page, but your database is becoming increasingly cluttered with copy upon copy of the same text &#8211; an absolute nightmare if you ever need to directly search or edit the database.</p>
<p>Many people hate the whole idea of revisions, and turn the feature off. I like to keep some recent versions, so I set the number to 3. Whichever you choose, you need to include a step in your installation routine to change the default setting by amending wp-config.php.</p>
<h2 id="changes">wp-config.php Changes</h2>
<p>All you need to do is add the following two lines to wp-config.php. It shouldn&#8217;t matter where you put them, but for convenience I add them before the line that includes <em>&#8220;stop editing&#8221;</em>.<br />
<code>define('WP_MEMORY_LIMIT', '64M');<br />
define('WP_POST_REVISIONS', 3);</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.shrewdies.net/452/wp-config-php-essentials/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress 3.0 Beta</title>
		<link>http://www.shrewdies.net/1585/wordpress-3-0-beta/</link>
		<comments>http://www.shrewdies.net/1585/wordpress-3-0-beta/#comments</comments>
		<pubDate>Fri, 30 Apr 2010 15:12:12 +0000</pubDate>
		<dc:creator>Keith from shrewdies</dc:creator>
				<category><![CDATA[Foundation]]></category>
		<category><![CDATA[Install WordPress]]></category>
		<category><![CDATA[WordPress 3]]></category>
		<category><![CDATA[WordPress setup]]></category>

		<guid isPermaLink="false">http://www.shrewdies.net/?p=1585</guid>
		<description><![CDATA[WordPress 3.0 Beta is now available, so I used it today on a new website. I wouldn&#8217;t normally use a beta version on a production website, but the full release will be available before that site is fully live, giving me a chance to test some new features. Site installation continues to be simple, and [...]]]></description>
			<content:encoded><![CDATA[<div class="kctIntro">WordPress 3.0 Beta is now available, so I used it today on a new website.</p>
<p>I wouldn&#8217;t normally use a beta version on a production website, but the full release will be available before that site is fully live, giving me a chance to test some new features.</p></div>
<p>Site installation continues to be simple, and I took the simplest option of using the automatic script provided by my server host. This has the nice option of changing the default admin username to something less guessable &#8211; always a good idea for improved security.</p>
<h2>WordPress Settings</h2>
<p>Settings are the same as version 2, so I made the usual adjustments:<span id="more-1585"></span>
<dl>
<dt>General Settings</dt>
<dd>Tagline and Email. I also ticked the membership so anyone can register, but it would be better to leave this until you get the membership plugins organized (more on this soon).</dd>
<dt>Discussion Settings</dt>
<dd>Enabled threaded comments, with depth set to the maximum of 10. Set moderation to hold comment if 1 link. More on discussion settings when someone asks for it.</dd>
<dt>Privacy Settings</dt>
<dd>Always a good idea to make sure your site is visible. If you can think of a situation where you would set it to block search engines, please tell me.</dd>
<dt>Permalink Settings</dt>
<dd>Vital to select the Custom Structure and change it to <code>/%post_id%/%postname%/</code> (we can discuss why this is so if you like). I usually change the category and tag base to something more site specific &#8211; there might be a slight search engine advantage, but I just think it looks better.</dd>
</dl>
<h2>Other WordPress Configuration</h2>
<p>It really should be categories and plugins next, but I could not resist investigating the new default template &#8211; Twenty Ten (surely not a tribute to Windows Ninety Five?). This seems to be a great improvement, but I have yet to find a WordPress theme that does not need a quick makeover with the editor. I think the essentials of WordPress themes needs a separate topic, so I&#8217;ll do one soon.</p>
<p>There also used to be essential modifications to wp-config.php. I&#8217;ll check this, and report back tomorrow.</p>
<p><!--more--><div style="margin-left:-1em;"><table><tr><td><script type="text/javascript"><!--
google_ad_client = "pub-7512621270035949";
/* shrewdies 300x250, created 22/12/09 */
google_ad_slot = "4026195862";
google_ad_width = 300;
google_ad_height = 250;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></td><td>
<script type="text/javascript"><!--
google_ad_client = "pub-7512621270035949";
/* shrewdies 300x250, created 22/12/09 */
google_ad_slot = "4026195862";
google_ad_width = 300;
google_ad_height = 250;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></td></tr></table></div></p>
]]></content:encoded>
			<wfw:commentRss>http://www.shrewdies.net/1585/wordpress-3-0-beta/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>WordPress Upgrade 2.9</title>
		<link>http://www.shrewdies.net/261/wordpress-upgrade-2-9/</link>
		<comments>http://www.shrewdies.net/261/wordpress-upgrade-2-9/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 20:37:44 +0000</pubDate>
		<dc:creator>Keith from shrewdies</dc:creator>
				<category><![CDATA[Foundation]]></category>
		<category><![CDATA[fatal error]]></category>
		<category><![CDATA[upgrade-wordpress]]></category>
		<category><![CDATA[WordPress Upgrade]]></category>

		<guid isPermaLink="false">http://www.shrewdies.net/?p=261</guid>
		<description><![CDATA[WordPress upgrade is now so easy, there is almost nothing to it. The new upgrade to WordPress 2.9 is typical of the inbuilt update routine. It simply updates itself, but there are a couple of points to watch out for. First, the usual warning &#8211; backup your database and files. It is easy to be [...]]]></description>
			<content:encoded><![CDATA[<div class="kctIntro">
<p>WordPress upgrade is now so easy, there is almost nothing to it.</p>
<p>The new upgrade to WordPress 2.9 is typical of the inbuilt update routine. It simply updates itself, but there are a couple of points to watch out for.</p>
</div>
<div id="attachment_262" class="wp-caption aligncenter" style="width: 610px"><img src="http://www.shrewdies.net/wp-content/uploads/wordpress-upgrade-fatal-error.gif" alt="WordPress Upgrade Fatal Error" title="WordPress Upgrade Fatal Error" class="size-full wp-image-262" height="147" width="600"><p class="wp-caption-text">WordPress Upgrade Fatal Error</p></div>
<p>First, the usual warning &#8211; backup your database and files.</p>
<p>It is easy to be complacent here, and assume that it never goes wrong. Frankly, it hardly ever fails, but if it does, it leaves you with no website, and no easy way of recovering it. If you are happy to run the risk of starting from scratch, then skip the backup &#8211; it&#8217;s what dummies do.<br />
For us shrewdies, a quick backup is the first step in upgrading WordPress. The backup service from your web host admin panel will do it easily in one step (unless you have a very poor host).</p>
<p>Second, simply click the &#8220;Upgrade Automatically&#8221; button, and wait a few seconds. It is that easy &#8211; but what if it goes wrong?</p>
<p>Occasionally, you will see a message like:</p>
<blockquote><p>Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 2515174 bytes) in [your-wp-path]/wp-includes/http.php on line 1331</p></blockquote>
<p><span id="more-261"></span>Do not panic &#8211; the &#8220;Fatal error&#8221; has not killed your website. It has stopped the WordPress upgrade, so your website is still functioning exactly as it was.</p>
<p>The problem is very easy to solve. Simply deactivate your plugins, upgrade WordPress, then reactivate your plugins.</p>
<p>If you have had any problems upgrading WordPress, please add your questions, or comments, below.</p>
<p><!--more--><div style="margin-left:-1em;"><table><tr><td><script type="text/javascript"><!--
google_ad_client = "pub-7512621270035949";
/* shrewdies 300x250, created 22/12/09 */
google_ad_slot = "4026195862";
google_ad_width = 300;
google_ad_height = 250;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></td><td>
<script type="text/javascript"><!--
google_ad_client = "pub-7512621270035949";
/* shrewdies 300x250, created 22/12/09 */
google_ad_slot = "4026195862";
google_ad_width = 300;
google_ad_height = 250;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></td></tr></table></div></p>
]]></content:encoded>
			<wfw:commentRss>http://www.shrewdies.net/261/wordpress-upgrade-2-9/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WordPress MU</title>
		<link>http://www.shrewdies.net/189/wordpress-mu/</link>
		<comments>http://www.shrewdies.net/189/wordpress-mu/#comments</comments>
		<pubDate>Sun, 18 Oct 2009 00:13:03 +0000</pubDate>
		<dc:creator>Keith from shrewdies</dc:creator>
				<category><![CDATA[Foundation]]></category>
		<category><![CDATA[wordpress-mu]]></category>

		<guid isPermaLink="false">http://www.shrewdies.net/?p=189</guid>
		<description><![CDATA[I had my chance, today, to see if my perfect instructions for installing WordPress MU are still perfect. Actually, I can see immediately that perfection falls short by lacking a screenshot. So I&#8217;ve added one. There are still no Fantastico or Simple Scripts that I am aware of to install automatically, so you have to [...]]]></description>
			<content:encoded><![CDATA[<div class="kctIntro">I had my chance, today, to see if my perfect instructions for installing WordPress MU are still perfect.</p>
<p>Actually, I can see immediately that perfection falls short by lacking a screenshot.</p>
<p>So I&#8217;ve added one.</p></div>
<div id="attachment_192" class="wp-caption aligncenter" style="width: 610px"><img src="http://www.shrewdies.net/wp-content/uploads/wordpress-mu-installation.gif" alt="Wordpress MU Installation" title="Wordpress MU Installation" width="600" height="786" class="size-full wp-image-192" /><p class="wp-caption-text">Wordpress MU Installation</p></div>
<p>There are still no Fantastico or Simple Scripts that I am aware of to install automatically, so you have to copy the files to your server, then fill in the form shown above (with your own details, of course).</p>
<p>The choice of sub-domains or sub-directories defaults to the correct choice. I cannot think of a reason why you would want subdirectories, but this would make an interesting topic for discussion in the <a href="http://www.shrewdies.net/web-hosting-forum/host-forum/" title="Discuss Installing WordPress MU">WordPress MU Installation Forum</a>, if you think you need sub-directories.</p>
<p>The manual install routine is still extremely simple, but as with most things, there is a right way and a wrong way to do it. The wrong way is to leap in without planning. The right way is to follow these simple steps.<br />
<span id="more-189"></span>
<ol>
<li>Prepare your web server &#8211; a clean root directory, or create a sub-directory to run WordPress MU from. The choice will be obvious from your site plan, and if you do not have one, stop now.</li>
<li>Copy the downloaded WPMU installation to your web server.</li>
<li>Prepare a database and an admin user with full privileges, and keep a browser window open with the database and username on view. Better still, copy them into your site plan.</li>
<li>In a new browser window, go to your website root or the directory you used in step 1.</li>
<li>Fill in the details on the form, using copy and paste for your database and user name.</li>
<li>Note the admin password on the confirmation screen &#8211; it&#8217;s a good idea to change it immediately to something you can remember.</li>
</ol>
<p>Note that there is now no need to change the permissions of the root and wp-content directories, though the confirmation screen still warns you to change them back.</p>
<p>I&#8217;ll keep you informed of other differences between standard and multi-user versions, as I continue with the foundation, function and formatting stages.</p>
<p>A final note about naming. The multi-user version is now called WordPress µ &#8211; that Greek letter being pronounced mew. On this site, I tend to refer mostly to WordPress MU, as that seems to be the most common usage. WordPress Multi User, WPMU, and occasionally WordPress Multiuser are also used, and they all mean the same thing.</p>
<p><!--more--><div style="margin-left:-1em;"><table><tr><td><script type="text/javascript"><!--
google_ad_client = "pub-7512621270035949";
/* shrewdies 300x250, created 22/12/09 */
google_ad_slot = "4026195862";
google_ad_width = 300;
google_ad_height = 250;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></td><td>
<script type="text/javascript"><!--
google_ad_client = "pub-7512621270035949";
/* shrewdies 300x250, created 22/12/09 */
google_ad_slot = "4026195862";
google_ad_width = 300;
google_ad_height = 250;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></td></tr></table></div></p>
]]></content:encoded>
			<wfw:commentRss>http://www.shrewdies.net/189/wordpress-mu/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

