<?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>fuzzymargins &#187; WordPress</title>
	<atom:link href="http://www.fuzzymargins.com/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fuzzymargins.com</link>
	<description>Life is full of code</description>
	<lastBuildDate>Sun, 07 Mar 2010 14:21:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Move the WordPress pages to the header &#8211; revisited</title>
		<link>http://www.fuzzymargins.com/2010/01/move-the-wordpress-pages-to-the-header-revisited/</link>
		<comments>http://www.fuzzymargins.com/2010/01/move-the-wordpress-pages-to-the-header-revisited/#comments</comments>
		<pubDate>Mon, 25 Jan 2010 20:42:26 +0000</pubDate>
		<dc:creator>jamespiggot</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[HTML]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://www.fuzzymargins.com/?p=332</guid>
		<description><![CDATA[This updated article describes how to use the page widget to build a page menu in the WordPress header. For the background to this see the previous post Move the WordPress page links to the header that described a simple way of listing the page links on the header. This method makes use of the [...]]]></description>
			<content:encoded><![CDATA[<p>This updated article describes how to use the page widget to build a page menu in the WordPress header. For the background to this see the previous post <a href="http://www.fuzzymargins.com/2009/04/move-the-wordpress-page-links-to-the-header/">Move the WordPress page links to the header</a> that described a simple way of listing the page links on the header.<br />
<span id="more-332"></span><br />
This method makes use of the Pages widget which allows pages to be excluded from the menu and also allows the sort order of the pages to be specified. To view this from the dashboard expand Appearance in the left-hand sidebar then select Widgets. You can then use the Widget to set up a list of page links in the sidebar.</p>
<p><img src="http://www.fuzzymargins.com/wp-content/uploads/2010/01/Widgets_Pages.gif" alt="WordPress Pages widget" title="WordPress Pages widget" width="252" height="243" class="alignnone size-full wp-image-195" /></p>
<p>The first thing is to find the path to the theme that you are using, for the default theme the path is:</p>
<p class="highlight">&frasl;wordpress&frasl;wp-content&frasl;themes&frasl;default</p>
<p>For other themes the path will vary so make sure you have identified the correct one for the theme you have in use. </p>
<p>Then using your favourite text editor open up the following files:</p>
<ul>
<li><strong>functions.php</strong></li>
<li><strong>header.php</strong></li>
</ul>
<p class="note"><strong>Note:</strong> Before you make any changes to these files make sure you have a backup</p>
<p>In functions.php add the following code in an appropriate place. </p>
<pre><code>function list_pages($pages) {
$options = get_option( 'widget_pages' );
foreach ($options as $key=&gt;$value) {
        if ( $pages == $options[$key]['title'])	{
			$sortby = $options[$key]['sortby'];
			$exclude = $options[$key]['exclude'];
        	if ( $sortby == 'menu_order' ) {
				$sortby = 'menu_order, post_title';
				}
			$out = wp_list_pages( apply_filters('widget_pages_args',
					array('title_li' =&gt; '',
					'echo' =&gt; 0,
					'sort_column' =&gt; $sortby,
					'exclude' =&gt; $exclude) ) );
        	if ( !empty( $out ) ) {
				?&gt;
				&lt;li&gt;&lt;?php echo $out; ?&gt;&lt;/li&gt;
				&lt;?php
				}
        	}
		}
}</code></pre>
<p>Then add the following line of code in the <em>header.php</em> file. The correct location will vary by theme but generally it will be within the <em>header div</em>.</p>
<pre><code>&lt;ul&gt;&lt;?php list_pages('Header1'); ?&gt;&lt;/ul&gt;</code>
</pre>
<p>The effect of this will be to list the pages defined by the Pages widget that has a title of <em>Header1</em>, you can edit the the parameter above for list_pages to match the one you are already using. This should work with WordPress 2.8 onwards but probably will not work with previous versions to that.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fuzzymargins.com/2010/01/move-the-wordpress-pages-to-the-header-revisited/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Warning &#8211; backup before updating to WordPress 2.8</title>
		<link>http://www.fuzzymargins.com/2009/06/warning-backup-before-updating-to-wordpress-2-8/</link>
		<comments>http://www.fuzzymargins.com/2009/06/warning-backup-before-updating-to-wordpress-2-8/#comments</comments>
		<pubDate>Mon, 22 Jun 2009 20:41:39 +0000</pubDate>
		<dc:creator>jamespiggot</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://www.fuzzymargins.com/?p=301</guid>
		<description><![CDATA[The first problem with updating to WordPress version 2.8 was with the automatic update facility, the new version comes with it&#8217;s own automatic updater built in. This means the WordPress Automatic Update plugin is no longer required and should be disabled. The actual error message will vary according to the Theme that is in use [...]]]></description>
			<content:encoded><![CDATA[<p>The first problem with updating to WordPress version 2.8 was with the automatic update facility, the new version comes with it&#8217;s own automatic updater built in. This means the WordPress Automatic Update plugin is no longer required and should be disabled. The actual error message will vary according to the Theme that is in use on your site but will start with:</p>
<blockquote><p>Fatal error: Cannot redeclare pclziputilpathreduction() </p></blockquote>
<p>After disabling the WordPress Automatic Update plugin and clicking on the Automatic Update link on the dashboard again the update worked correctly. So that is easily dealt with and not a major problem.</p>
<p>The second problem was more serious, the automatic updates had overwritten the contents of the default theme with the original Kubrick design. If like me you have updated the default or the classic themes but never bothered to create a new theme then WordPress will replace your changed files with the originals.</p>
<p><span id="more-301"></span><br />
Luckily in my case there was a backup that I could restore my changes from as I use SVN to store changes to code.</p>
<p>There is a message on the dashboard telling you to backup your files and database before doing the automatic update but many people will ignore this, I know I did!</p>
<p>I guess the moral of this story is to always make sure you have backups of your work before making changes, however tempted you may be to skip this annoying step, and also to create your own theme in WordPress rather than relying on making changes to the default or classic themes as WordPress obviously considers these fair game for overwriting without warning (something the old automatic updates plugin did not do).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fuzzymargins.com/2009/06/warning-backup-before-updating-to-wordpress-2-8/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Move the WordPress page links to the header</title>
		<link>http://www.fuzzymargins.com/2009/04/move-the-wordpress-page-links-to-the-header/</link>
		<comments>http://www.fuzzymargins.com/2009/04/move-the-wordpress-page-links-to-the-header/#comments</comments>
		<pubDate>Mon, 27 Apr 2009 13:30:36 +0000</pubDate>
		<dc:creator>jamespiggot</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[HTML]]></category>

		<guid isPermaLink="false">http://www.fuzzymargins.com/?p=289</guid>
		<description><![CDATA[The default theme for WordPress places the links to pages in the sidebar. Moving them to the header is relatively easy to do if you&#8217;re comfortable making minor changes to the code. The first thing is to find the path to the theme that you are using, for the default theme the path is: &#8260;wordpress&#8260;wp-content&#8260;themes&#8260;default [...]]]></description>
			<content:encoded><![CDATA[<p>The default theme for WordPress places the links to pages in the sidebar. Moving them to the header is relatively easy to do if you&#8217;re comfortable making minor changes to the code.<br />
The first thing is to find the path to the theme that you are using, for the default theme the path is:</p>
<p class="highlight">&frasl;wordpress&frasl;wp-content&frasl;themes&frasl;default</p>
<p>For other themes the path will vary so make sure you have identified the correct one for the theme you have in use. </p>
<p>Then using your favourite text editor open up the following files:</p>
<ul>
<li><strong>sidebar.php</strong></li>
<li><strong>header.php</strong></li>
</ul>
<p class="note"><strong>Note:</strong> Before you make any changes to these files make sure you have a backup</p>
<p>Next look for the following code fragment in sidebar.php which is used by WordPress to generate the list of page links.</p>
<p><span id="more-289"></span></p>
<pre><code>&lt;ul&gt;&lt;?php wp_list_pages('title_li='); ?&gt;&lt;/ul&gt;</code>
</pre>
<p>Copy the line of code above from the <em>sidebar.php</em> file and paste it in to the <em>header.php</em> file</p>
<p>This will copy the page links from the sidebar to the header. The end result may look strange because of the CSS styles in use. To get the result seen above in the header of this blog I changed the stylesheet to make the page links float right, where you place them  is down to personal preferences.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fuzzymargins.com/2009/04/move-the-wordpress-page-links-to-the-header/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>Move the WordPress search box to the header</title>
		<link>http://www.fuzzymargins.com/2009/04/move-the-wordpress-search-box-to-the-header/</link>
		<comments>http://www.fuzzymargins.com/2009/04/move-the-wordpress-search-box-to-the-header/#comments</comments>
		<pubDate>Thu, 02 Apr 2009 17:14:02 +0000</pubDate>
		<dc:creator>jamespiggot</dc:creator>
				<category><![CDATA[Design]]></category>
		<category><![CDATA[WordPress]]></category>
		<category><![CDATA[CSS]]></category>
		<category><![CDATA[HTML]]></category>

		<guid isPermaLink="false">http://www.fuzzymargins.com/?p=237</guid>
		<description><![CDATA[The default theme in WordPress places the search box in the sidebar. Moving it to the header is relatively easy to do if you&#8217;re comfortable making minor changes to the code. The first thing is to find the path to the theme that you are using, for the default theme the path is: &#8260;wordpress&#8260;wp-content&#8260;themes&#8260;default Then [...]]]></description>
			<content:encoded><![CDATA[<p>The default theme in WordPress places the search box in the sidebar. Moving it to the header is relatively easy to do if you&#8217;re comfortable making minor changes to the code. The first thing is to find the path to the theme that you are using, for the default theme the path is:</p>
<p class="highlight">&frasl;wordpress&frasl;wp-content&frasl;themes&frasl;default</p>
<p>Then using your favourite text editor open up the following files:</p>
<ul>
<li><strong>sidebar.php</strong></li>
<li><strong>header.php</strong></li>
</ul>
<p class="note"><strong>Note:</strong> Before you make any changes to these files make sure you have a backup</p>
<p>Next look for the following code fragment in sidebar.php which is used by WordPress to generate the search box (What this code does is to insert the contents of the <em>searchform.php </em>file at this point in the page. The <em>searchform.php</em> file contains the code to produce the search box and the search button).</p>
<p><span id="more-237"></span></p>
<pre><code>&lt;?php include (TEMPLATEPATH . '/searchform.php'); ?&gt;</code>
</pre>
<p>Cut the line of code above from the <em>sidebar.php</em> file and paste it in an appropriate location in the header.php file.</p>
<p>This will move the search form from the sidebar to the header. The end result may look strange because of the CSS styles in use. To get the result seen above in the header of this blog I changed the stylesheet to make the title float left and the search form float right, where you place the search form is down to personal preferences.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fuzzymargins.com/2009/04/move-the-wordpress-search-box-to-the-header/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Fuzzy Images with WordPress</title>
		<link>http://www.fuzzymargins.com/2009/01/fuzzy-images-with-wordpress/</link>
		<comments>http://www.fuzzymargins.com/2009/01/fuzzy-images-with-wordpress/#comments</comments>
		<pubDate>Sat, 31 Jan 2009 19:35:58 +0000</pubDate>
		<dc:creator>jamespiggot</dc:creator>
				<category><![CDATA[WordPress]]></category>
		<category><![CDATA[HTML]]></category>

		<guid isPermaLink="false">http://www.fuzzymargins.com/?p=161</guid>
		<description><![CDATA[Uploaded Images &#8216;Blurry&#8217; with WordPress Being new to WordPress I have been using the standard image upload facilities.  After upgrading to WordPress version 2.7 the Flash uploader stopped working so I resorted to using the browser based version. This was annoying but not annoying enough to make me do something about it. Then I noticed [...]]]></description>
			<content:encoded><![CDATA[<h3>Uploaded Images &#8216;Blurry&#8217; with WordPress</h3>
<p>Being new to WordPress I have been using the standard image upload facilities.  After upgrading to WordPress version 2.7 the Flash uploader stopped working so I resorted to using the browser based version. This was annoying but not annoying enough to make me do something about it. Then I noticed that images which were fine when captured looked fuzzy when viewing the published article, specially when using Internet Explorer.</p>
<p>So what was going on? Well, for one selecting anything other than full size meant the images were being re-sized by the uploader and that reduced the image quality, you notice the difference in quality compared to re-sizing the images yourself in Photoshop.</p>
<p><span id="more-161"></span></p>
<p>The other thing is that if you select to insert the image at full-size then it will be uploaded at whatever size it is; if that is too wide then the browser will helpfully scale the image to fit within the column. This creates a passable image in FireFox but a pretty blurred image in Internet Explorer.</p>
<p>As an example, the image below has been scaled to fit, in FireFox you can still more or less read the text in the image, in Internet Explorer the image is pretty much unreadable</p>
<p><img src="http://www.fuzzymargins.com/wp-content/uploads/2009/01/people-and-works1.jpg" alt="people-and-works1" title="people-and-works1" width="596" height="246" class="alignnone size-full wp-image-195" /></p>
<p>Right-clicking on the image in FireFox and selecting properties opens the image properties dialog which will show in the Image Dimensions line (highlighted in the image below) that the image has been re-sized</p>
<p><img src="http://www.fuzzymargins.com/wp-content/uploads/2009/01/ff-scale-image.jpg" alt="Firefox image properties" title="Firefox image properties" width="449" height="254" class="alignnone size-full wp-image-195" /></p>
<p>The answer for me was to revert to sizing the images using Photoshop then uploading the images via FTP to the same location as the uploader. Then there is a choice of selecting the image from a URL using the WordPress uploader or just typing in the URL directly to the post. Personally my chosen route is now to do the all the HTML myself, gives me a feeling of being back in control.</p>
<p>The other issue is the number of different images the uploader creates in the WordPress &#47;uploads directory, it seems to create three images at least for every image that is uploaded, hand-rolling the process means you have one image per image in the post and you have control over the process. If you&#39;re like me and you keep altering and uploading the image repeatedly then WordPress creates a whole lot of images which become difficult to control and take up loads of space.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fuzzymargins.com/2009/01/fuzzy-images-with-wordpress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
