<?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/"
	xmlns:series="http://unfoldingneurons.com/"
	>

<channel>
	<title>Voodoo Programming &#187; LiveSearch</title>
	<atom:link href="http://www.cneophytou.com/tag/livesearch/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cneophytou.com</link>
	<description>Things programmers do that they know shouldn&#039;t work but they try anyway, and which sometimes actually work, such as recompiling everything.</description>
	<lastBuildDate>Fri, 12 Nov 2010 17:07:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>LiveSearch 1.3</title>
		<link>http://www.cneophytou.com/2007/03/27/livesearch-13/</link>
		<comments>http://www.cneophytou.com/2007/03/27/livesearch-13/#comments</comments>
		<pubDate>Tue, 27 Mar 2007 00:01:43 +0000</pubDate>
		<dc:creator>Constantinos</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[WP Plugin]]></category>
		<category><![CDATA[CC Licence]]></category>
		<category><![CDATA[LiveSearch]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.cneophytou.com/2007/03/27/livesearch-13/</guid>
		<description><![CDATA[I&#8217;ve finished work on LiveSearch 1.3 some time ago, just never got around to creating a tarball and uploading it to this site. The major change was that it no longer requires that the searchform.php and livesearch.css files be manually copied to your themes directory. If you want to make theme-specific changes to it you [...]]]></description>
			<content:encoded><![CDATA[I&#8217;ve finished work on LiveSearch 1.3 some time ago, just never got around to creating a tarball and uploading it to this site. The major change was that it no longer requires that the searchform.php and livesearch.css files be manually copied to your themes directory. If you want to make theme-specific changes to it you can still have a copy of those files in your theme directory, and if they&#8217;re found there they will be used instead of the default ones. Plus a few bug fixes and javascript improvements here and there.<br />
<br />
If you&#8217;re interested, I created a <a href='http://code.google.com/p/livesearchwpplugin/'>Google Code</a> project for this and all the files are stored there.<br />
<br />
As before, here are quicklinks to the <a href='http://www.cneophytou.com/wp-content/uploads/2007/03/livesearch.zip' title='LiveSearch 1.3 zip'>zip archive</a> and the <a href='http://www.cneophytou.com/wp-content/uploads/2007/03/livesearch.tgz' title='LiveSearch 1.3 tgz'>gzipped tarball</a>, as well as the main <a href='http://www.cneophytou.com/2006/03/26/livesearch/'>LiveSearch</a> post.]]></content:encoded>
			<wfw:commentRss>http://www.cneophytou.com/2007/03/27/livesearch-13/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	
		<series:name><![CDATA[LiveSearch]]></series:name>
	</item>
		<item>
		<title>LiveSearch 1.2</title>
		<link>http://www.cneophytou.com/2006/04/06/livesearch-12/</link>
		<comments>http://www.cneophytou.com/2006/04/06/livesearch-12/#comments</comments>
		<pubDate>Thu, 06 Apr 2006 21:02:32 +0000</pubDate>
		<dc:creator>Constantinos</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[WP Plugin]]></category>
		<category><![CDATA[CC Licence]]></category>
		<category><![CDATA[LiveSearch]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.cneophytou.com/2006/04/07/livesearch-12/</guid>
		<description><![CDATA[Ok. I&#8217;ve widgetized this plugin, and updated the headers of the plugin. Now you can just install it, and put it anywhere on your sidebar using the Widget plugin. In its options you can specify whether or not you want the searchbox to be encompassed in the default widget wrappers (disabled by default). Pretty straight [...]]]></description>
			<content:encoded><![CDATA[Ok. I&#8217;ve widgetized this plugin, and updated the headers of the plugin. Now you can just install it, and put it anywhere on your sidebar using the Widget plugin. In its options you can specify whether or not you want the searchbox to be encompassed in the default widget wrappers (disabled by default). Pretty straight forward.<br />
<br />
The css still needs to be updated, but I don&#8217;t know if I&#8217;ll be getting to that anytime soon. Any upgrades/suggestions anyone might have are more than welcome.<br />
<br />
Here is a quicklink to the <a id="p34" href="http://www.cneophytou.com/wp-content/uploads/2006/03/livesearch.zip">zip archive</a>. Original files are always linked from the main <a href="http://www.cneophytou.com/2006/03/26/livesearch/">LiveSearch post</a>.]]></content:encoded>
			<wfw:commentRss>http://www.cneophytou.com/2006/04/06/livesearch-12/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
	
		<series:name><![CDATA[LiveSearch]]></series:name>
	</item>
		<item>
		<title>LiveSearch Update</title>
		<link>http://www.cneophytou.com/2006/03/28/livesearch-update/</link>
		<comments>http://www.cneophytou.com/2006/03/28/livesearch-update/#comments</comments>
		<pubDate>Tue, 28 Mar 2006 20:55:48 +0000</pubDate>
		<dc:creator>Constantinos</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[WP Plugin]]></category>
		<category><![CDATA[CC Licence]]></category>
		<category><![CDATA[LiveSearch]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.cneophytou.com/2006/03/28/livesearch-update/</guid>
		<description><![CDATA[I&#8217;ve updated the code to include an option for the size of the search box which I neglected the first time around. I also crudely fixed up the code so that no javascript errors occur when a page without the searchbox is loaded. (For example on my site, any page outside the blog). I&#8217;ve done [...]]]></description>
			<content:encoded><![CDATA[I&#8217;ve updated the code to include an option for the size of the search box which I neglected the first time around. I also crudely fixed up the code so that no javascript errors occur when a page without the searchbox is loaded. (For example on my site, any page outside the blog). I&#8217;ve done some preliminary testing and it seems to work. If anyone can (or wants to) improve on this, please do so! The archive files on the <a href='http://www.cneophytou.com/2006/03/26/livesearch/'>original post</a> have been updated to reflect the new changes.<br /><span id="more-45"></span>
<br />
The next step would be to fix up the css a little bit. One thing I don&#8217;t like on my site is that the first result is not indented properly with the rest&#8230; I need to take a look at that. Also, would anyone be interested in moving all the color/size options for the css in the wp-options page? Is this a good/bad idea? This would be done by moving the css outside of the file and into the plugin code, so it gets printed directly in the header rather than linked to. It would make it relatively easier to make simple changes, but much harder to customize the css completely. It&#8217;s not that hard to do it, I just don&#8217;t know if people would prefer it that way or not. Also worth to note that with an external css file people can customize a different css for each of their themes if they are using multiple ones, whereas with all the color/size options moved into the WP Options page, then all that would have to be changed manually&#8230;]]></content:encoded>
			<wfw:commentRss>http://www.cneophytou.com/2006/03/28/livesearch-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<series:name><![CDATA[LiveSearch]]></series:name>
	</item>
		<item>
		<title>LiveSearch</title>
		<link>http://www.cneophytou.com/2006/03/26/livesearch/</link>
		<comments>http://www.cneophytou.com/2006/03/26/livesearch/#comments</comments>
		<pubDate>Sun, 26 Mar 2006 13:39:17 +0000</pubDate>
		<dc:creator>Constantinos</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[WP Plugin]]></category>
		<category><![CDATA[CC Licence]]></category>
		<category><![CDATA[LiveSearch]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.cneophytou.com/2006/03/14/livesearch/</guid>
		<description><![CDATA[You might notice the spiffy little search box on the navigation bar of this blog. It&#8217;s an implementation of the LiveSearch code which I incorporated recently. It&#8217;s a nice little tool, using pretty straight basic (albeit a bit complex) AJAX code. However it did require some effort to implement this, as several files needed to [...]]]></description>
			<content:encoded><![CDATA[You might notice the spiffy little search box on the navigation bar of this blog. It&#8217;s an implementation of the <a href="http://fernando.dubtribe.com/archives/2005/06/01/livesearch-for-wordpress-1512/">LiveSearch code</a> which I incorporated recently.<br />
<br />
It&#8217;s a nice little tool, using pretty straight basic (albeit a bit complex) AJAX code. However it did require some effort to implement this, as several files needed to to be modified, and the required files placed all over the place. This meant that the ability to use this tool was restricted to people with some understanding of PHP, and also did not enable the clean integration of the code in WordPress.<br /><span id="more-31"></span>
<br />
So what I have done is integrate the required code/css into a small plugin which can be managed via the WordPress administration section. The plugin consists of a single directory which should be placed in your wp-content/plugins directory<span class='deprecated'>, as well as two files that should be placed in your chosen theme directory. If you use multiple themes (for example via the Theme Switcher plugin), then you should place a copy of these two files in the directory of each theme you want to use it in. The two files are:</span><br />
<code>
<span class='deprecated'>livesearch.css</span><br />
<span class='deprecated'>searchform.php</span>
</code><br />
<span class='deprecated'>The first one is so that users can style the LiveSearch boxes so it fits with their chosen theme, and users should not be required to make manual modifications to their code every time they change a theme. The second file is a replacement of the existing one, and enables the LiveSearch box. In case the plugin is disabled from the WordPress admin section (or simply disabled from the LiveSearch Options page, or the plugin deleted from the plugins directory), then the default search box will be displayed instead, without breaking its functionality (with some minor modifications). Note that running your WordPress installation with LiveSearch enabled will turn the &#8220;Search&#8221; button off, but disabling the plugin will turn it back on.</span><br />
<span class='update'>Updated 2007-03-27:</span> <a href='http://www.cneophytou.com/2007/03/27/livesearch-13/'>LiveSearch 1.3</a> is now up! No files need to be moved to make this version work. You can edit <code>livesearch.css</code> in-place, in its plugin directory. If you wish to maintain multiple themes, then you can still move <code>livesearch.css</code> into your theme directory. A style file found in the current theme&#8217;s directory will always be used over the one located in the plugin directory.<br />
<br />
<span class='update'>Updated 2008-03-17:</span> Updated to <a href="http://downloads.wordpress.org/plugin/livesearch.1.4.zip">LiveSearch 1.4</a>, to support WordPress 2.5.<br />
<br />
As a side note, the outputed html should be XHTML Strict, with tentative WCAG triple-a compliance (like the rest of this site. Visit <a href="/about/accessibility/">the accessibility page</a> for more information.<br />
</p><h2>Download:</h2><p>
You can download the plugin from its <a href='http://wordpress.org/extend/plugins/livesearch/' title='LiveSearch'>WordPress Plugin Directory</a>, unpack it and follow the README instructions to install it (which are pretty much a review of this post).<br />
<br />
As is always the case in this sort of thing, there are no guarantees. The plugin should work, but just in case make a backup of any files you replace (though now you shouldn&#8217;t need to even do that). There&#8217;s always room for improvement, and I&#8217;m not just referring to the LiveSearch code, but also to the plugin wrapper. Feel free to comment.<br />
</p><h2>Change Log</h2>
<ul>
<li>v1.4 &#8211; Plugin works with WordPress 2.5 (thanks to the Korean <a href="http://unfusion.kunsan.ac.kr/word/archive/779">Club despair</a> blog) and is now also hosted on the <a href='http://wordpress.org/extend/plugins/livesearch/' title='LiveSearch'>WordPress Plugin Directory</a></li>
<li>v1.3 &#8211; Plugin now completely drag-and-drop, no need to copy any files anywhere. Minor bug fixes/improvements in javascript code. Now hosted on <a href='http://code.google.com/p/livesearchwpplugin/'>Google Code</a></li>
<li>v1.2 &#8211; Plugin widgetized, minor javascript changes</li>
<li>v1.1 &#8211; Fixed potential javascript errors</li>
<li>v1.0 &#8211; Original plugin, LiveSearch code copy/pasted directly without modifications</li>
</ul>
<p>
For more detailed explanations of the changes in each version, follow the series links in the sidebar.]]></content:encoded>
			<wfw:commentRss>http://www.cneophytou.com/2006/03/26/livesearch/feed/</wfw:commentRss>
		<slash:comments>71</slash:comments>
	
		<series:name><![CDATA[LiveSearch]]></series:name>
	</item>
	</channel>
</rss>

