<?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>Michael Welford&#187; problems Archives  &#8211; Michael Welford . com</title>
	<atom:link href="http://www.michaelwelford.com/blog/tag/problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.michaelwelford.com</link>
	<description>Subjective meets the objective</description>
	<lastBuildDate>Tue, 03 Mar 2009 11:16:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Problems Encountered Building This Site</title>
		<link>http://www.michaelwelford.com/blog/problems-encountered-building-this-site/</link>
		<comments>http://www.michaelwelford.com/blog/problems-encountered-building-this-site/#comments</comments>
		<pubDate>Tue, 27 Jan 2009 13:27:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Web Development]]></category>
		<category><![CDATA[problems]]></category>
		<category><![CDATA[themes]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://mw001/?p=173</guid>
		<description><![CDATA[This site is built on Wordpress (version 2.7 at the time of writing) and the following is a dump of the problems I came across when putting together this site. If you have similar problems and need more detailed solutions drop me a line.
Here we go:
1. The wp-typogrify setting that adds extra  &#38;nbsp;s breaks nextgen [...]]]></description>
			<content:encoded><![CDATA[<p>This site is built on Wordpress (version 2.7 at the time of writing) and the following is a dump of the problems I came across when putting together this site. If you have similar problems and need more detailed solutions drop me a line.</p>
<p>Here we go:</p>
<h5>1. The wp-typogrify setting that adds extra  &amp;nbsp;s breaks nextgen gallery when you have more than one gallery on a page<strong><br />
</strong></h5>
<p>Solution: It&#8217;s not a big deal so I disabled the wp-typogrify setting. Otherwise it would be hackery into the wp-typogrify module.</p>
<h5>2. Getting pixel pattern transparent gifs to line up!</h5>
<p>Solution: Gah! Had to create slightly different images that are offset by a pixel, and, well it doesn&#8217;t always work the same across all browsers. Good grief to think that I was thinking of a more crazy theme with more complex patterns instead of the chosen differing &#8220;transparencies&#8221;. Come to think of it I may end up trying to implement that&#8230; also I had to use tables for certain parts of the design - yeah, yeah, if table-cell was better supported I would be doing it that way.</p>
<h5>3. The pager doesn&#8217;t work properly if you shift the main blog posts to something else like /blog/</h5>
<p>Solution: It&#8217;s a bug! Patch can be found <a href="http://trac.wordpress.org/ticket/6603" target="_blank">here. </a>Hopefully this will fixed in Wordpress 2.8.<a href="http://trac.wordpress.org/ticket/6603" target="_blank"><br />
</a></p>
<h5>4. WP Super Cache didn&#8217;t work out of the box</h5>
<p>Solution: Had to step through the FAQ suggestions. I would say it was to do with permissions on the wp-content directory at time of installing the plugin.</p>
<h5>5. Hacked modules stopped working when upgraded.</h5>
<p>Solution: Well duh - how embarrassing! Don&#8217;t hack the modules themselves. Just work around it in the theme. Move along - nothing to see here!</p>
<h5>6. Getting background images that work</h5>
<p>Solution: I originally thought that most backgrounds would work with the faux transparency, however, backgrounds that are very bright, very dark or have dithering of their own look rubbish. So I just had to put an hour into selecting background images instead of 5 minutes.</p>
<h5>7. Need at least 5 posts to make front page look ok.</h5>
<p>Solution: Get busy, don&#8217;t tell anyone about website until more than 5 posts!<br />
<strong></strong></p>
<h5><strong>8. Getting the latest image thumbs to perfectly align left and right in three columns</strong></h5>
<p>Solution: Wrap the output from nextgen in a table. Again, if only table-cell was better supported. *sigh*</p>
<h5>9. No spacing in Twittter Tools output</h5>
<p>Solution: Well you can either hack or regex. In this case a hack was more suitable.</p>
<h5>9. Tags and long headings went over the edge of the design</h5>
<p>Solutions: Oops. Thankfully that heading really was too long and the tags mostly useless. Style : 1, F orm : 0</p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelwelford.com/blog/problems-encountered-building-this-site/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
