<?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>Neatly Sliced &#187; WordPress</title>
	<atom:link href="http://blog.neatlysliced.com/category/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.neatlysliced.com</link>
	<description>Bread was overrated.</description>
	<lastBuildDate>Thu, 30 Apr 2009 17:53:31 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>WordPress 2.5</title>
		<link>http://blog.neatlysliced.com/2008/04/wordpress-25/</link>
		<comments>http://blog.neatlysliced.com/2008/04/wordpress-25/#comments</comments>
		<pubDate>Wed, 09 Apr 2008 11:29:36 +0000</pubDate>
		<dc:creator>Jennifer</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.neatlysliced.com/?p=220</guid>
		<description><![CDATA[Mere days after upgrading to WordPress 2.3.3, I&#8217;ve now upgraded to WordPress 2.5. Sean brought out that due to a security vulnerability, Technorati stopped indexing compromised blogs and strongly encouraged all 2.3.3 users to upgrade to 2.5. Say what! 
The new 2.5 Dashboard is a lot slicker and web 2.0ish. Lots of Ajax and/or Javascript [...]]]></description>
			<content:encoded><![CDATA[<p>Mere days after upgrading to WordPress 2.3.3, I&#8217;ve now upgraded to <a href="http://wordpress.org/download/">WordPress 2.5</a>. <a href="http://seanblog.com">Sean</a> <a href="http://blog.neatlysliced.com/2008/03/wordpress-233/#comment-10287">brought out</a> that due to a security vulnerability, <a href="http://technorati.com/weblog/2008/04/424.html">Technorati stopped indexing compromised blogs</a> and strongly encouraged all 2.3.3 users to upgrade to 2.5. Say what! </p>
<p>The new 2.5 Dashboard is a lot slicker and web 2.0ish. Lots of Ajax and/or Javascript integration, which is nice. Things are moved around a bit which will get a bit of getting used to.</p>
<p>I&#8217;m totally psyched about the improvements to the editor area. I hated how it would mess with HTML code. I will hastily update the food blog, as this was one major reason why I never posted there; every post was a headache to format properly.</p>
<p><a href="http://sw-guide.de/wordpress/plugins/maintenance-mode/">Maintenance Mode plug in</a> broke on the update for me &#8211; I was logged in yet I kept getting the maintenance mode screen (which ought only to appear when <em>not</em> logged in). I had to delete the poor pansy. Perhaps a new rev is in store.</p>
<img src="http://blog.neatlysliced.com/?ak_action=api_record_view&id=220&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blog.neatlysliced.com/2008/04/wordpress-25/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Slivers</title>
		<link>http://blog.neatlysliced.com/2008/02/slivers/</link>
		<comments>http://blog.neatlysliced.com/2008/02/slivers/#comments</comments>
		<pubDate>Mon, 25 Feb 2008 17:08:00 +0000</pubDate>
		<dc:creator>Jennifer</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.neatlysliced.com/2008/02/slivers/</guid>
		<description><![CDATA[I have this slivers category which essentially mimes Kottke&#8217;s remaindered links.  Often a title is moot, so I leave it blank, which left this design all wonky. I altered the template by hard coding some UGly if in_category() checks in the template pages. Ultimately, down the road, I&#8217;d like to write a plug-in that [...]]]></description>
			<content:encoded><![CDATA[<p>I have this <a href="/category/links/">slivers category</a> which essentially mimes <a href="http://www.kottke.org">Kottke&#8217;s remaindered links</a>.  Often a title is moot, so I leave it blank, which left this design all wonky. I altered the template by hard coding some UGly if in_category() checks in the template pages. Ultimately, down the road, I&#8217;d like to write a plug-in that will handle this through the CMS. </p>
<p>In any vein, I&#8217;m no designer, so I made it look halfway decentish without having to put much forethought into the rigamarole. I may care more if I had an actual design that I built the front end for, but this is a rip off WP template. So, again, any savvy designers who would like a web design on their resumé, submit a pdf, png, of jpg to me through the email on <a href="/about/">my about page</a>. If you can&#8217;t figure out my email from there, then it&#8217;s the survival of the smartest in the web world, my friends, and you will soon perish. The rest of you, good job for reading.</p>
<p>The ultimate point, slivers are restyled on single and home pages (category page is still a headache because I am short on patience with this design that I don&#8217;t even love). You will all now rejoice.</p>
<p>PS: Gripe of the moment? I would also like to figure out how to use this &#8220;more&#8221; tag and not chop off the RSS feed.</p>
<img src="http://blog.neatlysliced.com/?ak_action=api_record_view&id=204&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blog.neatlysliced.com/2008/02/slivers/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Resolve issue with cache.php</title>
		<link>http://blog.neatlysliced.com/2006/11/resolve-issue-with-cachephp/</link>
		<comments>http://blog.neatlysliced.com/2006/11/resolve-issue-with-cachephp/#comments</comments>
		<pubDate>Fri, 10 Nov 2006 00:00:00 +0000</pubDate>
		<dc:creator>Jennifer</dc:creator>
				<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.neatlysliced.com/2006/11/resolve-issue-with-cachephp/</guid>
		<description><![CDATA[According to this discussion forum, a site with the following error message has a cache issue:

Fatal error: Maximum execution time of 60 seconds exceeded in c:\your-site-path\wp-includes\cache.php on line 344

To resolve the issue, disable caching in wp-config.php. Add the following line: define('DISABLE_CACHE', true);
]]></description>
			<content:encoded><![CDATA[<p>According to this <a href="http://wordpress.org/support/topic/52452">discussion forum</a>, a site with the following error message has a cache issue:<br />
<code><br />
Fatal error: Maximum execution time of 60 seconds exceeded in c:\your-site-path\wp-includes\cache.php on line 344<br />
</code><br />
To resolve the issue, disable caching in wp-config.php. Add the following line: <code>define('DISABLE_CACHE', true);</code></p>
<img src="http://blog.neatlysliced.com/?ak_action=api_record_view&id=69&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://blog.neatlysliced.com/2006/11/resolve-issue-with-cachephp/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
	</channel>
</rss>
