<?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>Grantovich.net &#187; theming</title>
	<atom:link href="http://grantovich.net/posts/tag/theming/feed/" rel="self" type="application/rss+xml" />
	<link>http://grantovich.net</link>
	<description>Updated with astounding infrequency</description>
	<lastBuildDate>Tue, 29 Jun 2010 01:38:03 +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>Fresh Styles and WordPress 2.8</title>
		<link>http://grantovich.net/posts/2009/06/fresh-styles-and-wordpress-2-8/</link>
		<comments>http://grantovich.net/posts/2009/06/fresh-styles-and-wordpress-2-8/#comments</comments>
		<pubDate>Fri, 19 Jun 2009 22:19:41 +0000</pubDate>
		<dc:creator>Grantovich</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[bloggery]]></category>
		<category><![CDATA[theming]]></category>
		<category><![CDATA[webs]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://grantovich.net/?p=320</guid>
		<description><![CDATA[About a week ago I whacked the auto-upgrade button on my admin interface to take me up to WordPress 2.8. It is really nice how you can upgrade even the core system in a single click, right in the browser, without fiddling around on the server. Unfortunately, after the upgrade, every other form submission on the backend was giving me [...]]]></description>
			<content:encoded><![CDATA[<p>About a week ago I whacked the auto-upgrade button on my admin interface to take me up to WordPress 2.8. It is <em>really</em> nice how you can upgrade even the core system in a single click, right in the browser, without fiddling around on the server.</p>
<p>Unfortunately, after the upgrade, every other form submission on the backend was giving me blank pages and error messages, and I determined that my outdated theme was likely to blame. What&#8217;s more, I had foolishly made several customizations to the theme&#8217;s CSS, which of course would not be preserved when I upgraded it. Since I always thought that theme was a bit dull, anyway, I figured it would be as good a time as any to search around for a new one. As a side note, the new theme browser/installer in 2.8 made this task incredibly easier than it had been before.</p>
<p>So now we&#8217;re rolling along error-free with a new theme and all my customizations safely stashed in the <a href="http://wordpress.org/extend/plugins/custom-user-css/">Custom User CSS</a> plugin. I&#8217;m still not totally satisfied with this theme (especially the weird fadey drop-down menus) and will probably change it again in the future, but that&#8217;s life. On the positive side, the main content area is now just wide enough to squeak a 640-pixel-wide image into.</p>
<p>One of the non-CSS customizations I had made to my old theme was to add several lines of PHP that would prevent my content from being &#8220;texturized&#8221; &#8211; straight quotes replaced with smart quotes, doubled hyphens replaced with real dashes, etc. When I enabled the new theme and the texturization returned, I was surprised to notice that the one thing about it that really annoyed me had apparently been fixed: Straight quotes inside &lt;code&gt; blocks are no longer converted into smart quotes. I&#8217;m not sure if this is a fix on the part of the theme or WordPress 2.8 (I don&#8217;t see anything in the changelog about it), but either way I&#8217;m happy enough to leave the feature turned on.</p>
<p>The one thing that really impressed me about 2.8 is the new syntax-highlighting, line-numbering, generally awesome-looking code editor. This is the first time I&#8217;ve seen anything like this, though in retrospect it seems like an obvious idea: If we can already do WYSIWYG editing for normal content, why not apply some nice formatting and colors to code-editing as well? If you&#8217;re curious to see what this looks like, <a href="http://wordpress.org/development/2009/06/wordpress-28/">the WordPress 2.8 release announcement</a> has a slick video overview that touches on the code editor and various other new features (I recommend watching it, if only to witness the incredibly high production values for it being <em>an announcement of a point release</em>).</p>
]]></content:encoded>
			<wfw:commentRss>http://grantovich.net/posts/2009/06/fresh-styles-and-wordpress-2-8/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
