<?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>Onn Raves &#187; duh</title>
	<atom:link href="http://www.onnraves.com/category/duh/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.onnraves.com</link>
	<description>an Oracle consultant raves about P2ES, Python, Wordpress, photography and other things that he does on his Dell in Asia</description>
	<lastBuildDate>Tue, 03 Jan 2012 08:28:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>TypeError: not all arguments converted during string formatting</title>
		<link>http://www.onnraves.com/2009/01/08/typeerror-not-all-arguments-converted-during-string-formatting/</link>
		<comments>http://www.onnraves.com/2009/01/08/typeerror-not-all-arguments-converted-during-string-formatting/#comments</comments>
		<pubDate>Thu, 08 Jan 2009 07:39:04 +0000</pubDate>
		<dc:creator>Siew Kam Onn</dc:creator>
				<category><![CDATA[duh]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://onnraves.com/2009/01/08/typeerror-not-all-arguments-converted-during-string-formatting/</guid>
		<description><![CDATA[I hit this error with some python code: TypeError: not all arguments converted during string formatting I took a long time to finally trace it to this: output = 'inserting %s report centers for ' % (number_of_segments, column_set_name) It means I provided 2 values to replace (number_of_segments, column_set_name) but only provided one place holder (%s). &#8230; <a href="http://www.onnraves.com/2009/01/08/typeerror-not-all-arguments-converted-during-string-formatting/" class="more-link" >read on <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I hit this error with some python code:</p>
<p><strong>TypeError: not all arguments converted during string formatting</strong></p>
<p>I took a long time to finally trace it to this:</p>
<div>
<div style="padding-right: 0px; padding-left: 0px; font-size: 8pt; padding-bottom: 0px; overflow: visible; width: 100%; color: black; border-top-style: none; line-height: 12pt; padding-top: 0px; font-family: consolas, 'Courier New', courier, monospace; border-right-style: none; border-left-style: none; background-color: #f4f4f4; border-bottom-style: none">
<pre style="padding-right: 0px; padding-left: 0px; font-size: 8pt; padding-bottom: 0px; margin: 0em; overflow: visible; width: 100%; color: black; border-top-style: none; line-height: 12pt; padding-top: 0px; font-family: consolas, 'Courier New', courier, monospace; border-right-style: none; border-left-style: none; background-color: white; border-bottom-style: none">output = <span style="color: #006080">'inserting %s report centers for '</span> % (number_of_segments, column_set_name)</pre>
</div>
</div>
<p>It means I provided 2 values to replace (number_of_segments, column_set_name) but only provided one place holder (%s).</p>
<p>This is the correct code:</p>
<div>
<div style="padding-right: 0px; padding-left: 0px; font-size: 8pt; padding-bottom: 0px; overflow: visible; width: 100%; color: black; border-top-style: none; line-height: 12pt; padding-top: 0px; font-family: consolas, 'Courier New', courier, monospace; border-right-style: none; border-left-style: none; background-color: #f4f4f4; border-bottom-style: none">
<pre style="padding-right: 0px; padding-left: 0px; font-size: 8pt; padding-bottom: 0px; margin: 0em; overflow: visible; width: 100%; color: black; border-top-style: none; line-height: 12pt; padding-top: 0px; font-family: consolas, 'Courier New', courier, monospace; border-right-style: none; border-left-style: none; background-color: white; border-bottom-style: none">output = <span style="color: #006080">'inserting %s report centers for %s'</span> % (number_of_segments, column_set_name)</pre>
</div>
</div>
<p>&nbsp;</p>
<div class="wlWriterSmartContent" id="scid:0767317B-992E-4b12-91E0-4F059A8CECA8:f5271d4c-f35c-4df4-a71d-6aaadcdbce33" style="padding-right: 0px; display: inline; padding-left: 0px; padding-bottom: 0px; margin: 0px; padding-top: 0px">Technorati tags: <a href="http://technorati.com/tags/python" rel="tag">python</a>, <a href="http://technorati.com/tags/TypeError" rel="tag">TypeError</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.onnraves.com/2009/01/08/typeerror-not-all-arguments-converted-during-string-formatting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>After upgrade WordPress, get xmlrpc invalid response error</title>
		<link>http://www.onnraves.com/2008/06/14/after-upgrade-wordpress-get-xmlrpc-invalid-response-error/</link>
		<comments>http://www.onnraves.com/2008/06/14/after-upgrade-wordpress-get-xmlrpc-invalid-response-error/#comments</comments>
		<pubDate>Sat, 14 Jun 2008 06:22:28 +0000</pubDate>
		<dc:creator>Siew Kam Onn</dc:creator>
				<category><![CDATA[duh]]></category>
		<category><![CDATA[wordpress]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://onnraves.com/2008/06/14/after-upgrade-wordpress-get-xmlrpc-invalid-response-error/</guid>
		<description><![CDATA[&#160; If anything has gone wrong the first thing to do is go through all the steps in our extended upgrade instructions. That page also has information about some of the most common problems we see. Upgrading WordPress « WordPress Codex I recently upgraded WordPress manually following the instructions at Upgrading WordPress « WordPress Codex. &#8230; <a href="http://www.onnraves.com/2008/06/14/after-upgrade-wordpress-get-xmlrpc-invalid-response-error/" class="more-link" >read on <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<blockquote><p>If anything has gone wrong the first thing to do is go through all the steps in our <a href="http://codex.wordpress.org/Upgrading_WordPress_Extended">extended upgrade instructions</a>. That page also has information about some of the most common problems we see.</p></blockquote>
<p><a href="http://codex.wordpress.org/Upgrading_WordPress">Upgrading WordPress « WordPress Codex</a> </p>
<p>I recently upgraded WordPress manually following the instructions at <a href="http://codex.wordpress.org/Upgrading_WordPress">Upgrading WordPress « WordPress Codex</a>. Soon after, when I tried to post using Windows Live Writer, I received the xmlrpc.php invalid response error. This does not happen if I upgrade using Fantastico.</p>
<p><a href="http://wordpress.org/support/topic/166314">WordPress support forum</a> led me to think that the problem was with my blog client, Windows Live Writer.</p>
<p>It seems I am not alone, Joe Cheng at Microsoft received a lot of complaints about Live Writer not working after upgrading&nbsp; WordPress.</p>
<p>Actually, the problem is not with Windows Live Writer, it&#8217;s with the WordPress upgrade instructions.</p>
<p>Briefly, <a href="http://codex.wordpress.org/Upgrading_WordPress">Upgrading WordPress « WordPress Codex</a>&nbsp; says:</p>
<p>copy contents of downloaded zip file to:</p>
<p>1. wp-admin directory</p>
<p>2. wp-includes directory</p>
<p>3. wp-contents directory</p>
<p><a href="http://onnraves.beventure.com/wp-content/uploads/2008/06/upgrade-wordpress.png"><img style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px" height="178" alt="upgrade wordpress" src="http://onnraves.beventure.com/wp-content/uploads/2008/06/upgrade-wordpress-thumb.png" width="244" align="right" border="0"></a>But it neglects to tell you to also overwrite the contents of the root directory with the files from the zip file.</p>
<p>This screen capture shows some of the files at the root directory. </p>
<p>As it turned out, one of the files in the root is xmlrpc.php.</p>
<p>After I overwrote the root files, Windows Live Writer posts fine to my blog.</p>
<p>&nbsp;</p>
<div class="wlWriterSmartContent" id="scid:0767317B-992E-4b12-91E0-4F059A8CECA8:40e8c6e8-0d50-438b-8266-42c17d2e9530" style="padding-right: 0px; display: inline; padding-left: 0px; padding-bottom: 0px; margin: 0px; padding-top: 0px">Technorati tags: <a href="http://technorati.com/tags/wordpress" rel="tag">wordpress</a>, <a href="http://technorati.com/tags/upgrade" rel="tag">upgrade</a>, <a href="http://technorati.com/tags/xmlrpc" rel="tag">xmlrpc</a>, <a href="http://technorati.com/tags/error" rel="tag">error</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.onnraves.com/2008/06/14/after-upgrade-wordpress-get-xmlrpc-invalid-response-error/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

