<?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>GotChance &#187; Wordpress</title>
	<atom:link href="http://gotchance.com/blog/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://gotchance.com/blog</link>
	<description>web (design + development) and other geeky stuff !</description>
	<lastBuildDate>Fri, 21 May 2010 19:33:43 +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>Upgraded From WordPress 2.6.2 to 2.8 Baker</title>
		<link>http://gotchance.com/blog/2009/06/11/upgraded-from-wordpress-2-6-2-to-2-8-baker/</link>
		<comments>http://gotchance.com/blog/2009/06/11/upgraded-from-wordpress-2-6-2-to-2-8-baker/#comments</comments>
		<pubDate>Thu, 11 Jun 2009 16:26:35 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://gotchance.com/blog/2009/06/11/upgraded-from-wordpress-2-6-2-to-2-8-baker/</guid>
		<description><![CDATA[I hadn’t upgraded from my WordPress 2.6.2 for very long. I’m sorta don’t like Upgrading wordpress at all. Today, finally i decided to upgrade using the WordPress Automatic Upgrade Plugin. When i logged into the Dashboard, i came to know that WordPress 2.8 has been released. So, i upgraded immediately. It went on smoothly. So, [...]]]></description>
			<content:encoded><![CDATA[<p>I hadn’t upgraded from my <a href="http://gotchance.com/blog/2008/10/22/upgraded-to-wordpress-262/">WordPress 2.6.2</a> for very long. I’m sorta don’t like Upgrading wordpress at all. Today, finally i decided to upgrade using the <a href="http://wordpress.org/extend/plugins/wordpress-automatic-upgrade/">WordPress Automatic Upgrade Plugin</a>. When i logged into the Dashboard, i came to know that WordPress 2.8 has been released. So, i upgraded immediately. It went on smoothly. So, i can confirm that it works well for upgrading to 2.8.</p>
<p>Now, coming back to WordPress 2.8, i visited the <a href="http://wordpress.org/development/2009/06/wordpress-28/">WordPress blog</a> to know about the new features in 2.8. There are some very nice features. My favorite are :</p>
<p><strong>CodePress Highlighting in the Editor :</strong> Finally, i need not fire up my PSPad Editor for making small changes to the theme or the plugins.</p>
<p><strong>New Widgets Interface : </strong>As i said, i never really had the chance to play with the Dashboard of 2.7, except for on my Demo and local Dev installations. So, the new widgets interface is really nice.</p>
<p><strong>Screen Options : </strong>Enables us to set how many items to show per page. I have the habit of manually checking and deleting the comments marked as Spam. So, it is easier when all the comments are displayed in a single page.</p>
<p><strong>Installing Themes from Dashboard : </strong>Previously this was possible for plugins. As promised, they’ve added the feature for themes too. Though i’ll never be using this, it’ll be useful for casual bloggers who like to change the look of their blog often.</p>
<p>So, if you’re thinking of updating to 2.8, delay no further. Its a worthwhile upgrade. Use the WPAU plugin to make the process as easy as sipping coffee.</p>
]]></content:encoded>
			<wfw:commentRss>http://gotchance.com/blog/2009/06/11/upgraded-from-wordpress-2-6-2-to-2-8-baker/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Is It That Important To Get Rid Of WordPress Search ?</title>
		<link>http://gotchance.com/blog/2009/06/09/is-it-that-important-to-get-rid-of-wordpress-search/</link>
		<comments>http://gotchance.com/blog/2009/06/09/is-it-that-important-to-get-rid-of-wordpress-search/#comments</comments>
		<pubDate>Tue, 09 Jun 2009 10:47:05 +0000</pubDate>
		<dc:creator>Hari</dc:creator>
				<category><![CDATA[Wordpress]]></category>

		<guid isPermaLink="false">http://gotchance.com/blog/2009/06/09/is-it-that-important-to-get-rid-of-wordpress-search/</guid>
		<description><![CDATA[Today, this post from ProBlogDesign popped up on my Google Reader and made me wonder “if it is that important to get rid of WordPress search ?”. I know i’ve already written about WordPress Search. But, it is a topic worth taking a second look at. Quickly read through that post and do the search [...]]]></description>
			<content:encoded><![CDATA[<p>Today, <a href="http://www.problogdesign.com/wordpress/does-google-custom-search-get-more-searches-than-regular-wordpress-search/">this post</a> from ProBlogDesign popped up on my Google Reader and made me wonder “if it is that important to get rid of WordPress search ?”. I know i’ve already written about <a href="/2008/12/18/improve-your-wordpress-search-functionality-why-and-how/">WordPress Search</a>. But, it is a topic worth taking a second look at. Quickly read through that post and do <a href="http://www.problogger.net/?s=things+you+know+about+my+dad+problogger">the search</a> on ProBlogger today. The post that i mentioned has been promoted to 17th position from its earlier 12th position. How cool.</p>
<p>WordPress, sure, is an awesome piece of blogging software. But, why is the search functionality of WordPress so poor ? What are the basic flaws ?</p>
<ul>
<li>Search results are sorted according to date, while all search results should be sorted according to relevance. </li>
<li>WordPress searches only “title” and “content”. While that may be logical for a “blog”, the search SHOULD include comments, author, category etc.. For eg, when i search for “<a href="http://gotchance.com/blog/?s=Hari">Hari</a>”, it is supposed to bring up all the posts written by me, with the priority being as follows : 1) having “Hari” in title. 2) having “Hari” in post content. 3) having “Hari in comments. and 4) lastly, doesn’t have “Hari but was written by me. But what happens actually ? The top results are the posts which contain the word “sHARIng”. How funny… </li>
<li>Another example is when i search for “<a href="http://gotchance.com/blog/?s=Advertising">Advertising</a>”, it is supposed to bring up the posts from my <a href="http://gotchance.com/blog/category/advertising/">Advertising</a> category. But, only one post from that category actually appears in the results. Whether or not the post contains the term “Advertising”, i (a human) have classified it under Advertising. WordPress should give priority to my classification rather than some dumb SQL query. </li>
</ul>
<p>I noticed that some of the top blogs on my Google Reader have replaced WordPress Search with alternatives.</p>
<ul>
<li><a href="http://techcrunch.com">TechCrunch</a> – uses <a href="http://developer.yahoo.com/search/boss/">Yahoo BOSS</a> </li>
<li><a href="http://johnchow.com/">John Chow</a> – uses <a href="http://www.lijit.com/">Ligit</a> </li>
<li><a href="http://dailymobile.se">Daily Mobile</a> and <a href="http://makeuseof.com/">Make Use Of</a> and tons of others – use <a href="http://www.google.com/coop/cse/">Google CSE</a> </li>
</ul>
<h3>Is Google CSE the only Answer ?</h3>
<p>Google CSE is a really good service. But, should you use it on your blog ? With the “google”ish layout and the Ads, you completely lose the blog feel of it. Also, for an average blog with many hundred or few thousand posts, the Google search algorithm is not absolutely necessary. You can live with certain changes to your WordPress Search algorithm. For details on tweaking your WordPress search, do take a look at <a href="http://yoast.com/wordpress-search/">this post</a>. </p>
<p>Do you have any other suggestions to improve WordPress search ? Share with us in the comments.</p>
]]></content:encoded>
			<wfw:commentRss>http://gotchance.com/blog/2009/06/09/is-it-that-important-to-get-rid-of-wordpress-search/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

