<?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>Shawn Plep &#187; WordPress</title>
	<atom:link href="http://shawnplep.com/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://shawnplep.com</link>
	<description>Shawn Plep is a web programmer, SEO, and hacker from New Orleans, Louisiana.</description>
	<lastBuildDate>Wed, 07 Jul 2010 18:22:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Run Multiple Sites with One WordPress Install</title>
		<link>http://shawnplep.com/wordpress/run-multiple-sites-with-one-wordpress-install/</link>
		<comments>http://shawnplep.com/wordpress/run-multiple-sites-with-one-wordpress-install/#comments</comments>
		<pubDate>Sun, 30 May 2010 15:21:02 +0000</pubDate>
		<dc:creator>Shawn</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[multiple domains]]></category>
		<category><![CDATA[multisite]]></category>
		<category><![CDATA[wordpress 3]]></category>
		<category><![CDATA[wp-mu]]></category>

		<guid isPermaLink="false">http://shawnplep.com/?p=84</guid>
		<description><![CDATA[Using a single codebase of WordPress to run more than one site has never been easy to do &#8211; all previous methods involved hacks, and never allowed 100% compatibility with all plugins. I&#8217;ve experienced both homebrew single-codebase hacks and I&#8217;ve also used Virtual Multiblog (the best previous method).
However, with the release of WordPress 3, multiblog [...]]]></description>
			<content:encoded><![CDATA[<p>Using a single codebase of WordPress to run more than one site has never been easy to do &#8211; all previous methods involved hacks, and never allowed 100% compatibility with all plugins. I&#8217;ve experienced both homebrew single-codebase hacks and I&#8217;ve also used <a rel="nofollow" href="http://shawnplep.com/c/Virtual_Multiblog/84/1" rel="nofollow">Virtual Multiblog</a> (the best previous method).</p>
<p>However, with the release of WordPress 3, multiblog support is included natively. And it works great &#8211; the plugins I tested are all usable with none of the previous issues I&#8217;d seen with the &#8220;hacks&#8221; I had tried in the past.</p>
<p>In addition, by using a plugin (a plugin intended for WP-MU actually), you can run your multiple WordPress sites on their own domain names.</p>
<p>Best of all, it can all be done by using a single shared-hosting account.</p>
<p>At present, WordPress 3 is still in beta, but that hasn&#8217;t stopped me from putting it to use. I currently have a fully-functional network of around 20 sites, all running from a single install of WordPress 3 on a Hostgator shared hosting account and it hasn&#8217;t thrown up any errors or anything. For the most part, WP 3 is probably stable for most uses. Just back up your data regularly &#8211; especially before you attempt to upgrade anything.</p>
<p>Here&#8217;s how to do it, in very basic steps:<br />
1. Install the latest WordPress on your hosting account. (These instructions assume cPanel hosting.) At the moment, version 3 is located <a rel="nofollow" href="http://shawnplep.com/c/here/84/2">here</a>.<br />
2. In your cPanel account, enable wildcard subdomains. This is done by creating a subdomain of &#8220;*&#8221;. Yes, just an asterisk.<br />
3. For each of the domains you plan on hosting, add it as a Parked Domain. (Of course, this excludes your &#8220;main&#8221; domain.)<br />
4. In your wp-config.php file, add the following: <code>define(‘WP_ALLOW_MULTISITE’, true);</code><br />
5. In your WordPress admin, go to Tools->Network to enable the hosting of multiple blogs. Choose the <strong>subdomain</strong> option. Do <em>not</em> choose the subdirectory option!<br />
6. Create your sites from within the new &#8220;Super-Admin&#8221; menu.<br />
7. Download and install the <a rel="nofollow" href="http://shawnplep.com/c/Domain_Mapping_Plugin/84/3">Domain Mapping Plugin</a>.<br />
8. For each of your &#8220;sub-sites&#8221;, login to the admin and go to Tools->Domain Mapping. Enter the domain name and check the box.<br />
9. Go back to your main site&#8217;s Super Admin menu.<br />
10. Click on &#8220;Sites&#8221; and edit each site. For each one, change the domain to it&#8217;s full actual domain name.</p>
<p>At this point, you should be able to login to each of the sites&#8217; admin section from it&#8217;s domain name. Each site will have access to all the Themes and Plugins, and you can easily upgrade all the sites at once. Easier maintainability for sure!</p>
]]></content:encoded>
			<wfw:commentRss>http://shawnplep.com/wordpress/run-multiple-sites-with-one-wordpress-install/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How to Conceal Your WordPress Version</title>
		<link>http://shawnplep.com/wordpress/how-to-conceal-your-wordpress-version/</link>
		<comments>http://shawnplep.com/wordpress/how-to-conceal-your-wordpress-version/#comments</comments>
		<pubDate>Fri, 10 Apr 2009 22:23:14 +0000</pubDate>
		<dc:creator>Shawn</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[functions.php]]></category>
		<category><![CDATA[wordpress version]]></category>

		<guid isPermaLink="false">http://shawnplep.com/?p=21</guid>
		<description><![CDATA[There may be reasons you don&#8217;t wish to disclose that you&#8217;re using WordPress, or you may simply wish to disguise which version you&#8217;re using. I hope your reasoning isn&#8217;t for &#8220;security&#8221;, because this isn&#8217;t truly effective as a security measure. But whatever your reason, here&#8217;s how to do it.
First, go to your /wp-content/themes folder, and [...]]]></description>
			<content:encoded><![CDATA[<p>There may be reasons you don&#8217;t wish to disclose that you&#8217;re using WordPress, or you may simply wish to disguise which version you&#8217;re using. I hope your reasoning isn&#8217;t for &#8220;security&#8221;, because this isn&#8217;t truly effective as a security measure. But whatever your reason, here&#8217;s how to do it.</p>
<p>First, go to your /wp-content/themes folder, and open the folder for your current theme. There should be a file named &#8220;functions.php&#8221;. (If this file doesn&#8217;t exist, simply create the file.) Open this file, and add the following line to it:<br />
remove_action(&#8216;wp_head&#8217;, &#8216;wp_generator&#8217;);</p>
<p>That directive tells WordPress to remove the action of displaying the generator (which shows your WordPress version). It&#8217;s that simple!</p>
<p>You can do a lot of neat things within the functions.php file, as well &#8211; including adding new functions and removing other actions. For instance, you can remove some of the other (possibly useless) header info that WordPress outputs by default:<br />
remove_action(&#8216;wp_head&#8217;, &#8216;rsd_link&#8217;);<br />
remove_action(&#8216;wp_head&#8217;, &#8216;wlwmanifest_link&#8217;);</p>
<p>Think of the functions.php file as a way to implement a certain amount of plugin-like functionality, without having to actually install a plugin. If you know how to code in PHP the possibilities are vast.</p>
]]></content:encoded>
			<wfw:commentRss>http://shawnplep.com/wordpress/how-to-conceal-your-wordpress-version/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
