<?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>DocuView - document management system &#187; wordpress</title>
	<atom:link href="http://docuview.co.uk/index.php/tag/wordpress/feed/" rel="self" type="application/rss+xml" />
	<link>http://docuview.co.uk</link>
	<description>revolutionary web 2.0 document management system</description>
	<lastBuildDate>Fri, 25 Jun 2010 00:50:53 +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>WordPress 3.0 on nginx &#8211; expires headers micro-optimisations :)</title>
		<link>http://docuview.co.uk/index.php/2010/06/wordpress-3-0-on-nginx-expires-headers-micro-optimisations/</link>
		<comments>http://docuview.co.uk/index.php/2010/06/wordpress-3-0-on-nginx-expires-headers-micro-optimisations/#comments</comments>
		<pubDate>Wed, 23 Jun 2010 14:43:27 +0000</pubDate>
		<dc:creator>Martin Korych</dc:creator>
				<category><![CDATA[news]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[expires]]></category>
		<category><![CDATA[headers]]></category>
		<category><![CDATA[js]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[plugin]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://docuview.co.uk/?p=401</guid>
		<description><![CDATA[Set expires headers in nginx to cater for WordPress plugins' static files (such as CSS and JS)]]></description>
			<content:encoded><![CDATA[<p>I must say I didn&#8217;t particularly pay attention to caching/server performance before, I have always (wrongly) thought the stronger the hardware the less issues one is going to encounter, but since I got introduced to nginx&#8230; I am blown away.</p>
<p>WordPress 3.0 does some rather (positively) aggressive caching itself, but with nginx behind it we have witnessed our page-load times to be up to 4× faster!</p>
<p><span id="more-401"></span>Chasing YSlow and PageSpeed rankings we needed to update the nginx expires headers condition to cater for our plugins&#8217; static files (CSS and JS). Again, not that I have ever particularly noticed but not all plugins reference the latest version of their CSS&#8217; the same way. One comes across:</p>
<ul>
<li>.css</li>
<li>.css?<strong>1278974243</strong> (UNIX timestamp)</li>
<li>.css?<strong>ver=2</strong> (variable followed by an integer ONLY)</li>
<li>.css?<strong>ver=absd234</strong> (variable followed by mixed characters)</li>
<li>.css?<strong>version=2.2alpha</strong> (variable of any length followed by mixed characters including <strong>&#8220;.&#8221;</strong>)</li>
</ul>
<p>You see where I&#8217;m going with this. So after picking up a useful rewrite from <a title="nginx expires headers on static assets" href="http://stackoverflow.com/questions/873235/nginx-not-setting-expires-headers-on-rails-static-assets">StackOverflow</a> &#8211; which catered beautifully for <a title="Redmine" href="http://www.redmine.org/">Redmine</a>, we were faced with variations in WP we didn&#8217;t encounter originally and the script didn&#8217;t cover either. Digging deeper into the issue we came up with this, which now fully caches all 0f the above mentioned variations:</p>
<pre class="brush: plain;">if ($request_uri ~* \.(ico|css|js|gif|jpe?g|png|pdf|rar|swf|zip)(\?[0-9]+)?.*$) {
 expires 1M;
 break;
}</pre>
<p>This should go into your config file in <strong>&#8220;/etc/nginx/sites-available/whatever-your-config-file-is-called&#8221;</strong>.</p>
<p>Hope it helps <img src='http://docuview.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://docuview.co.uk/index.php/2010/06/wordpress-3-0-on-nginx-expires-headers-micro-optimisations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>customise the default size of avatars in WordPress 2.8+</title>
		<link>http://docuview.co.uk/index.php/2009/08/customise-the-default-size-of-avatars-in-wordpress-2-8/</link>
		<comments>http://docuview.co.uk/index.php/2009/08/customise-the-default-size-of-avatars-in-wordpress-2-8/#comments</comments>
		<pubDate>Mon, 31 Aug 2009 17:59:03 +0000</pubDate>
		<dc:creator>Martin Korych</dc:creator>
				<category><![CDATA[development]]></category>
		<category><![CDATA[troubleshooting]]></category>
		<category><![CDATA[avatar]]></category>
		<category><![CDATA[core]]></category>
		<category><![CDATA[docuview]]></category>
		<category><![CDATA[excerpt]]></category>
		<category><![CDATA[gravatar]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[icons]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[recent posts]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[widget]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://docuview.co.uk/?p=329</guid>
		<description><![CDATA[Customise your WordPress Avatar, gravatar or whichever icon you're using, in comments. Few easy steps.]]></description>
			<content:encoded><![CDATA[<p>You know the drill: backup, upgrade WordPress, check plugin compatibility, verify everything is up and running and&#8230; reapply your hacks to the core of WP. I have talked about <a title="post excerpt in wordpress recent posts widget" href="http://docuview.co.uk/index.php/2009/07/display-post-excerpt-in-recent-posts-widget-in-wordpress/">displaying the post excerpt in the recent posts widget</a> few weeks ago, today I&#8217;m going to talk about resizing the Avatar image file displayed in comments.</p>
<p><span id="more-329"></span>So you&#8217;ve just finished upgrading, everything went smooth and you now have some time to amend the core of WordPress to accommodate for the hacks and workarounds you have implemented over the time. You have styled, laid out and customised your comments, you have changed the default size of Gravatar, Avatar or any other user pictures you display only to find them going back to default (32px × 32px) as soon as you upgrade.</p>
<p>Worry not! In order to change it back to what it was, head to: &#8220;wp-includes/comment-template&#8221;, locate line #1322 (function wp_list_comments()) and change the defaults array value (&#8220;avatar_size&#8221;) from 32 to anything you like (we use 50px), so the result will read:</p>
<pre class="brush: php;">$defaults = array('walker' =&gt; null, 'max_depth' =&gt; '', 'style' =&gt; 'ul', 'callback' =&gt; null, 'end-callback' =&gt; null, 'type' =&gt; 'all',
'page' =&gt; '', 'per_page' =&gt; '', 'avatar_size' =&gt; 50, 'reverse_top_level' =&gt; null, 'reverse_children' =&gt; '');</pre>
<p>And zet is zit. Save and refresh your comments page and enjoy, your user icons and images are exactly big (or small) as intended.</p>
<p>Helpful? Drop me a line here.</p>
]]></content:encoded>
			<wfw:commentRss>http://docuview.co.uk/index.php/2009/08/customise-the-default-size-of-avatars-in-wordpress-2-8/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Display post excerpt in recent posts widget in WordPress &#8211; UPDATED June 2010</title>
		<link>http://docuview.co.uk/index.php/2009/07/display-post-excerpt-in-recent-posts-widget-in-wordpress/</link>
		<comments>http://docuview.co.uk/index.php/2009/07/display-post-excerpt-in-recent-posts-widget-in-wordpress/#comments</comments>
		<pubDate>Thu, 16 Jul 2009 12:08:13 +0000</pubDate>
		<dc:creator>Martin Korych</dc:creator>
				<category><![CDATA[development]]></category>
		<category><![CDATA[troubleshooting]]></category>
		<category><![CDATA[excerpt]]></category>
		<category><![CDATA[latest]]></category>
		<category><![CDATA[latest version]]></category>
		<category><![CDATA[link]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[recent posts]]></category>
		<category><![CDATA[upgrade]]></category>
		<category><![CDATA[widget]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://docuview.co.uk/?p=318</guid>
		<description><![CDATA[Enable the excerpt in WordPress (<= 3.0) "Recent Posts" widget in four easy steps.]]></description>
			<content:encoded><![CDATA[<p>Everytime we upgrade to the latest version of WordPress (currently <span style="text-decoration: line-through;">2.8.1</span> 3.0) we lose a bit of customising. Whether it&#8217;s the value of the search button in the search widget (hidden because of IE6&#8242;s and IE7&#8242;s disability to apply text-indent to form buttons) or the excerpt of our posts displayed in the widget on most of the pages disappears. For future reference and for people who don&#8217;t want to be searching for widgets to do that for them I&#8217;ve decided to describe how to quickly and easily get the job done &#8211; yourself!</p>
<p><span id="more-318"></span>First of all: the following only applies to <span style="text-decoration: line-through;">WordPress 2.8 and later</span> <strong>every WordPress</strong> installation we came across since 2.8 (including the most <strong>current 3.0</strong>).</p>
<ol>
<li>Open the <strong>default-widgets.php</strong> (to be found in the &#8220;<strong>wp-includes</strong>&#8221; folder of your blog)</li>
<li>Insert &#8220;<strong>&lt;?php    the_excerpt();    ?&gt;</strong>&#8221; on <strong>line 553</strong> (straight after
<pre class="brush: php;">&lt;li&gt;&lt;a href=&quot;&lt;?php the_permalink() ?&gt;&quot; title=&quot;&lt;?php echo esc_attr(get_the_title() ? get_the_title() : get_the_ID()); ?&gt;&quot;&gt;&lt;?php if ( get_the_title() ) the_title(); else the_ID(); ?&gt; &lt;/a&gt;&lt;/li&gt;</pre>
</li>
<li>Save</li>
<li>Refresh a page with the widget displayed</li>
</ol>
<p>Whilst I did look into installing a widget that would do this for me automatically I couldn&#8217;t find one that&#8217;d satisfy me. If you are using one please let me know which one, I&#8217;d love to consider automating the process. The reason I wrote this post is also because Google didn&#8217;t offer accurate enough or up-to-date results.</p>
<p>Helpful? Drop me a line&#8230; <img src='http://docuview.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://docuview.co.uk/index.php/2009/07/display-post-excerpt-in-recent-posts-widget-in-wordpress/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>WordPress spellcheck error/problem</title>
		<link>http://docuview.co.uk/index.php/2009/06/wordpress-spellcheck-error-problem/</link>
		<comments>http://docuview.co.uk/index.php/2009/06/wordpress-spellcheck-error-problem/#comments</comments>
		<pubDate>Sun, 14 Jun 2009 10:45:11 +0000</pubDate>
		<dc:creator>Martin Korych</dc:creator>
				<category><![CDATA[development]]></category>
		<category><![CDATA[troubleshooting]]></category>
		<category><![CDATA[alternative]]></category>
		<category><![CDATA[connection]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[solved]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://docuview.co.uk/blog/?p=119</guid>
		<description><![CDATA[Enable WordPress spellchecking by enabling a library in php.ini.]]></description>
			<content:encoded><![CDATA[<p>Are you getting this:</p>
<pre>Error response: &lt;br /&gt; &lt;b&gt;Warning&lt;/b&gt;: fsockopen() [&lt;a href='function.fsockopen'&gt;function.fsockopen&lt;/a&gt;]: unable to connect to ssl://www.google.com:443 (Unable to find the socket transport &amp;quot;ssl&amp;quot; - did you forget to enable it when you configured PHP?) in &lt;b&gt;D:\websites\*******\wp-includes\js\tinymce\plugins\spellchecker\classes\GoogleSpell.php&lt;/b&gt; on line &lt;b&gt;86&lt;/b&gt;&lt;br /&gt; Could not open SSL connection to google.{"id":null,"result":[],"error":null?</pre>
<p><span id="more-119"></span>There is a way hot to solve it: enable the php_curl extension in your php.ini. Just delete the &#8220;;&#8221; (semicolon) in front of this line: ;extension=php_curl.dll and you&#8217;re done. WordPress will now be able to check your spelling and suggest correct alternatives!</p>
<p>Any problems let me know.</p>
<p>BTW &#8211; it has nothing to do with any other library, simply just php_curl.dll library.</p>
]]></content:encoded>
			<wfw:commentRss>http://docuview.co.uk/index.php/2009/06/wordpress-spellcheck-error-problem/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
