<?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>WP Engineer &#187; Firefox</title>
	<atom:link href="http://wpengineer.com/tag/firefox/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpengineer.com</link>
	<description>WordPress News, Hacks, Tips, Tutorials, Plugins and Themes</description>
	<lastBuildDate>Sun, 22 Jan 2012 13:32:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>OpenSearch &#8211; Search Field For Mozilla And Internet Explorer With WordPress</title>
		<link>http://wpengineer.com/239/opensearch-search-field-for-mozilla-and-internet-explorer-with-wordpress/</link>
		<comments>http://wpengineer.com/239/opensearch-search-field-for-mozilla-and-internet-explorer-with-wordpress/#comments</comments>
		<pubDate>Thu, 16 Oct 2008 13:37:06 +0000</pubDate>
		<dc:creator>Frank</dc:creator>
				<category><![CDATA[WordPress Tutorials]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Search]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://wpengineer.com/?p=239</guid>
		<description><![CDATA[Nowadays search field in your browser improved quite a bit, even IE supports OpenSearch format. But what is so great about OpenSearch and how easy it is to use with your WordPress installation has two aspects: WordPress comes already with OpenSearch and it's easy configurable with XML. You just have to put a link in [...]]]></description>
			<content:encoded><![CDATA[<p>Nowadays search field in your browser improved quite a bit, even IE supports OpenSearch format. But what is so great about OpenSearch and how easy it is to use with your WordPress installation has two aspects: WordPress comes already with <a href="http://www.opensearch.org/">OpenSearch</a> and it's easy configurable with XML.</p>
<p><img src="http://wpengineer.com/wp-content/uploads/ieos.png" alt="in IE 7" title="ieos" width="336" height="204" class="aligncenter size-full wp-image-240" /></p>
<p>You just have to put a link in your theme and a xml file on your server to let the browser know that your blog supports the search field. So go ahead and improve your Plugin with little work and no use of a Plugin.</p>
<p>The following code should explain it. Adjust the syntax and link to the favicon and xml-file.</p>
<p>After you uploaded both files (<em>favicon.ico</em> und <em>os.xml</em>) add a link into the <em>header.php</em> of your theme. You can use the code one by one if you put os.xml in your root. After that it's possible to integrate your blog in Firefox and Internet Explorer.</p>
<p><img src="http://wpengineer.com/wp-content/uploads/ffos.png" alt="" title="ffos" width="316" height="450" class="aligncenter size-full wp-image-241" /></p>
<p>The declaration of each XML tag is well documented on <a href="http://www.opensearch.org/Specifications/OpenSearch/1.1">the OpenSearch website</a>.</p>
<h3>for the head area in your template - header.php:</h3>
<pre lang="php">
&lt;link rel=&quot;search&quot; type=&quot;application/opensearchdescription+xml&quot; title=&quot;&lt;?php bloginfo(&#039;name&#039;); ?&gt;&quot; href=&quot;&lt;?php bloginfo(&#039;url&#039;); ?&gt;/os.xml&quot; /&gt;
</pre>
<h3>XML file:</h3>
<p>Copy code, adjust and save as <em>os.xml</em>, then upload on your server.</p>
<pre lang="xml">
&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;OpenSearchDescription xmlns=&quot;http://a9.com/-/spec/opensearch/1.1/&quot;&gt;
	&lt;ShortName&gt;bueltge.de &#091;by:ltge.de&#093;&lt;/ShortName&gt;
	&lt;Description&gt;Use bueltge.de to search on blog.&lt;/Description&gt;
	&lt;Url type=&quot;text/html&quot; method=&quot;get&quot; template=&quot;http://bueltge.de/?s={searchTerms}&quot;&gt;&lt;/Url&gt;
	&lt;Contact&gt;info@bueltge.de&lt;/Contact&gt;
	&lt;LongName&gt;bueltge.de &#091;by:ltge.de&#093; Weblog Search&lt;/LongName&gt;
	&lt;Image height=&quot;16&quot; width=&quot;16&quot; type=&quot;image/x-icon&quot;&gt;http://bueltge.de/favicon.ico&lt;/Image&gt;
	&lt;Tags&gt;Weblog WordPress Webdevelopment&lt;/Tags&gt;
	&lt;Url type=&quot;application/atom+xml&quot; template=&quot;http://bueltge.de/?q={searchTerms}&amp;pw={startPage?}&amp;format=atom&quot;/&gt;
	&lt;Url type=&quot;application/rss+xml&quot; template=&quot;http://bueltge.de/?q={searchTerms}&amp;pw={startPage?}&amp;format=rss&quot;/&gt;
	&lt;Url type=&quot;text/html&quot; template=&quot;http://bueltge.de/?q={searchTerms}&amp;pw={startPage?}&quot;/&gt;
	&lt;Query role=&quot;example&quot; searchTerms=&quot;blog&quot;/&gt;
	&lt;Developer&gt;Frank Bueltge&lt;/Developer&gt;
	&lt;Attribution&gt;
	    Search data Copyright 2007, bueltge.de &#091;by:ltge.de&#093;, All Rights Reserved
	&lt;/Attribution&gt;
	&lt;SyndicationRight&gt;open&lt;/SyndicationRight&gt;
	&lt;AdultContent&gt;false&lt;/AdultContent&gt;
	&lt;Language&gt;de-DE&lt;/Language&gt;
	&lt;OutputEncoding&gt;UTF-8&lt;/OutputEncoding&gt;
	&lt;InputEncoding&gt;UTF-8&lt;/InputEncoding&gt;
&lt;/OpenSearchDescription&gt;
</pre>
<hr /><a href="http://wpplugins.com/plugin/281/snippets" title="More informations about this plugin for WordPress"><img src="http://wpengineer.com/wp-content/themes/wpe-3/images/snippets-125-125.png" height="90" alt="WordPress Snippet Plugin" /></a> <a href="http://xtreme-theme.com"><img src="http://wpengineer.com/wp-content/uploads/feed-banner-2.jpg" alt="Xtreme One WordPress Framework"/></a><br />
&copy; <a href="http://wpengineer.com/">WP Engineer Team</a>, All rights reserved <small>(Digital Fingerprint: WPEngineer-be0254ce2b4972feb4b9cb72034a092d)</small></p>
]]></content:encoded>
			<wfw:commentRss>http://wpengineer.com/239/opensearch-search-field-for-mozilla-and-internet-explorer-with-wordpress/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

