<?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>Fnode Networks &#187; Wordpress</title>
	<atom:link href="http://www.fnode.com/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fnode.com</link>
	<description></description>
	<lastBuildDate>Wed, 23 Nov 2011 20:18:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>WordPress Find and Replace String</title>
		<link>http://www.fnode.com/2009/06/wordpress-find-and-replace-string/</link>
		<comments>http://www.fnode.com/2009/06/wordpress-find-and-replace-string/#comments</comments>
		<pubDate>Sat, 13 Jun 2009 13:48:46 +0000</pubDate>
		<dc:creator>Nish Vamadevan</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.fnode.com/?p=415</guid>
		<description><![CDATA[I had to do a find and replace a string on all of the wordpress post. This can only be done via a MySQL query and won’t take more than a minute. This is how it’s done. In the following example, I will be finding X and replacing it with Y The string will find [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>I had to do a find and replace a string on all of the wordpress post. This can only be done via a MySQL query and won’t take more than a minute.</p>
<p>This is how it’s done. In the following example, I will be finding X and replacing it with Y</p>
<p>The string will find X in every single post and replace it with Y. This also works with phrases, URLs etc..</p>
<pre>update wp_posts set post_content = replace(post_content, 'X', 'Y')</pre>]]></content:encoded>
			<wfw:commentRss>http://www.fnode.com/2009/06/wordpress-find-and-replace-string/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>301 Redirect WordPress Posts To New Domain</title>
		<link>http://www.fnode.com/2008/04/301-redirect-wordpress-posts-to-new-domain/</link>
		<comments>http://www.fnode.com/2008/04/301-redirect-wordpress-posts-to-new-domain/#comments</comments>
		<pubDate>Tue, 01 Apr 2008 13:31:59 +0000</pubDate>
		<dc:creator>Nish Vamadevan</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[redirect]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.nishv.com/2008/04/01/301-redirect-wordpress-posts-to-new-domain/</guid>
		<description><![CDATA[301 Redirect is considered as a permanent redirect compared to a 302 redirect which is temporary. Therefore when moving wordpress to a new domain, it is a good idea to redirect all the posts to the new domain. This way all the search engine records will be kept intact and this means you won’t lose [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>301 Redirect is considered as a permanent redirect compared to a 302 redirect which is temporary. Therefore when moving wordpress to a new domain, it is a good idea to redirect all the posts to the new domain.</p>
<p>This way all the search engine records will be kept intact and this means you won’t lose any traffics / hits to the website.</p>
<p>This doesn’t mean redirecting from <strong>nishv.com</strong> to <strong>fnode.com</strong>, it will also redirect every single <acronym title="Uniform Resource Locator">URL</acronym> associated with <strong>nishv.com</strong> to <strong>fnode.com</strong>.</p>
<p>For instance, if a user is looking for a particular post and goes to <strong>nishv.com</strong>, they will be redirected to the corresponding post on <strong>fnode.com </strong></p>
<p>Here is an example of one of the most popular post on the site&#8230;</p>
<p><a href="http://www.fnode.com/2007/06/02/make-bisoncam-work-on-windows-vista/">http://www.nishv.com/2007/06/02/make-bisoncam-work-on-windows-vista/</a></p>
<p>When users clicks on the above link, they will be automatically redirect to</p>
<p><a href="http://www.fnode.com/2007/06/02/make-bisoncam-work-on-windows-vista/">http://www.fnode.com/2007/06/02/make-bisoncam-work-on-windows-vista/  </a></p>
<p>This way, the user won’t notice the domain change because it is 99% directed via search engine or linked <acronym title="Uniform Resource Locator">URL</acronym>.</p>
<p>This method is also a good way to let GoogleBot to know that the domain has been moved permanently from <strong>nishv.com</strong> to <strong>fnode.com</strong></p>
<p>Here is the code below and I used which goes into the .htaccess file. All you got to do is to replace the <acronym title="Uniform Resource Locator">URL</acronym> to make it work with your own domain.</p>
<pre>
# BEGIN WordPress
RewriteEngine On
RewriteCond %{HTTP_HOST} ^www.nishv.com
RewriteRule (.*) http://www.fnode.com/$1 [R=301,L]
# END WordPress
</pre>]]></content:encoded>
			<wfw:commentRss>http://www.fnode.com/2008/04/301-redirect-wordpress-posts-to-new-domain/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>Moving wordpress blog to new domain</title>
		<link>http://www.fnode.com/2008/03/moving-wordpress-blog-to-new-domain/</link>
		<comments>http://www.fnode.com/2008/03/moving-wordpress-blog-to-new-domain/#comments</comments>
		<pubDate>Wed, 19 Mar 2008 00:23:02 +0000</pubDate>
		<dc:creator>Nish Vamadevan</dc:creator>
				<category><![CDATA[Wordpress]]></category>
		<category><![CDATA[redirect]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.nishv.com/2008/03/19/moving-wordpress-blog-to-new-domain/</guid>
		<description><![CDATA[I have finally decided to move this wordpress blog to the parent domain (www.fnode.com) and going to be concentrating on more Tech, Online, News, and Reviews and I have decided to use this domain for mainly Journals and Tip / How-To purposes. I think that way, I can separate the media side of things from [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>I have finally decided to move this wordpress blog to the parent domain (<a href="http://www.fnode.com">www.fnode.com</a>) and going to be concentrating on more Tech, Online, News, and Reviews and I have decided to use this domain for mainly Journals and Tip / How-To purposes. I think that way, I can separate the media side of things from personal journals.</p>
<p>This is how I moved my wordpress blog from <strong>nishv.com</strong> to <strong>fnode.com </strong></p>
<ul>
<li>Install wordpress on <strong>fnode.com</strong></li>
<li>Went to <strong>nishv.com</strong> and copied the <strong>wp-content</strong> Directory and replaced it with the Directiory on <strong>fnode.com</strong> (So all the theme, plug-in and the uploaded contents are all there&#8230;)</li>
<li>Went to <strong>nishv.com</strong> and used phpMyAdmin to drum an <strong>.sql</strong> file of the database. (You may prefer .gz depending on the file size)</li>
<li>Went to <strong>fnode.com</strong> and used phpMyAdmin to drop all the tables on the wordpress database.</li>
<li>Imported the backed up database from <strong>nishv.com</strong></li>
</ul>
<p>Ran the following <acronym title="Structured Query Language">SQL</acronym> Queries&#8230;</p>
<pre>
UPDATE wp_options SET option_value = replace(option_value, 'http://www.nishv.com', 'http://www.fnode.com') WHERE option_name = 'home' OR option_name = 'siteurl';
UPDATE wp_posts SET guid = replace(guid, 'http://www.nishv.com','http://www.fnode.com');
UPDATE wp_posts SET post_content = replace(post_content, 'http://www.nishv.com', 'http://www.fnode.com');
</pre>
<p>That’s it, All set, now you can tweek the blog!</p>]]></content:encoded>
			<wfw:commentRss>http://www.fnode.com/2008/03/moving-wordpress-blog-to-new-domain/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

