<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Recent Mood Issues</title>
	<atom:link href="http://kccricket.net/archives/recent-mood-issues/feed" rel="self" type="application/rss+xml" />
	<link>http://kccricket.net/archives/recent-mood-issues</link>
	<description>A stream of text from the +5 keyboard of insightfulness.</description>
	<lastBuildDate>Mon, 26 Jul 2010 21:04:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Cricket Moods version 3.2 : Losing it[1]</title>
		<link>http://kccricket.net/archives/recent-mood-issues/comment-page-1#comment-1174</link>
		<dc:creator>Cricket Moods version 3.2 : Losing it[1]</dc:creator>
		<pubDate>Sun, 17 Dec 2006 14:51:28 +0000</pubDate>
		<guid isPermaLink="false">http://kccricket.net/archives/19#comment-1174</guid>
		<description>[...] I had a quick look at those lines in the plugin and was immediately reminded that I am not a coder. Obviously something was broken, but I had no idea what. After some random searching, I eventually found this post on the author&#8217;s site, in which he noted that he was aware that there was a problem, and that he&#8217;d fix it as soon as he could. OK, I was relieved that it wasn&#8217;t just my site being broken, but I really wanted to make the error go away. [...]</description>
		<content:encoded><![CDATA[<p>[...] I had a quick look at those lines in the plugin and was immediately reminded that I am not a coder. Obviously something was broken, but I had no idea what. After some random searching, I eventually found this post on the author&#8217;s site, in which he noted that he was aware that there was a problem, and that he&#8217;d fix it as soon as he could. OK, I was relieved that it wasn&#8217;t just my site being broken, but I really wanted to make the error go away. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kccricket</title>
		<link>http://kccricket.net/archives/recent-mood-issues/comment-page-1#comment-1171</link>
		<dc:creator>kccricket</dc:creator>
		<pubDate>Sun, 17 Dec 2006 01:36:40 +0000</pubDate>
		<guid isPermaLink="false">http://kccricket.net/archives/19#comment-1171</guid>
		<description>&lt;b&gt;!!blue&lt;/b&gt;:

The same error is actually occurring for you, the error just isn&#039;t showing up.  I experienced the same behavior testing with a WP 2.1 alpha.</description>
		<content:encoded><![CDATA[<p><b>!!blue</b>:</p>
<p>The same error is actually occurring for you, the error just isn&#8217;t showing up.  I experienced the same behavior testing with a WP 2.1 alpha.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kccricket</title>
		<link>http://kccricket.net/archives/recent-mood-issues/comment-page-1#comment-1170</link>
		<dc:creator>kccricket</dc:creator>
		<pubDate>Sat, 16 Dec 2006 19:18:08 +0000</pubDate>
		<guid isPermaLink="false">http://kccricket.net/archives/19#comment-1170</guid>
		<description>Les:

Yep, that will definately fix the error.  However, keep in mind that moods used in posts by the user may not match up with the default list of moods.

With the rudimentary testing I&#039;ve been able to do over dial-up on my &lt;acronym=&quot;Piece of Shit&quot;&gt;POS&lt;/acronym&gt; laptop, it appears that the WP get_usermeta function is not un-serializing the serialized user-mood array in the database.  I should be able to give this more attention on Monday evening.

It appears that I don&#039;t need to be serializing and escaping the array before passing it to update_usermeta.</description>
		<content:encoded><![CDATA[<p>Les:</p>
<p>Yep, that will definately fix the error.  However, keep in mind that moods used in posts by the user may not match up with the default list of moods.</p>
<p>With the rudimentary testing I&#8217;ve been able to do over dial-up on my <acronym ="Piece of Shit">POS</acronym> laptop, it appears that the WP get_usermeta function is not un-serializing the serialized user-mood array in the database.  I should be able to give this more attention on Monday evening.</p>
<p>It appears that I don&#8217;t need to be serializing and escaping the array before passing it to update_usermeta.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Les</title>
		<link>http://kccricket.net/archives/recent-mood-issues/comment-page-1#comment-1169</link>
		<dc:creator>Les</dc:creator>
		<pubDate>Sat, 16 Dec 2006 10:51:48 +0000</pubDate>
		<guid isPermaLink="false">http://kccricket.net/archives/19#comment-1169</guid>
		<description>OK - a quick work around. Take life in hands, make sure you have a backup, etc, etc.

Using phpMyAdmin or your personal choice of database editing too, go into the wp_usermeta table. Delete the two fields relating to Cricket Moods for each affected user. (I have one user, so this was easy)

Removing the fields resets the user to the default moods. My added mood is present and correct, and the nasty error is gone. Hope this helps someone :)</description>
		<content:encoded><![CDATA[<p>OK &#8211; a quick work around. Take life in hands, make sure you have a backup, etc, etc.</p>
<p>Using phpMyAdmin or your personal choice of database editing too, go into the wp_usermeta table. Delete the two fields relating to Cricket Moods for each affected user. (I have one user, so this was easy)</p>
<p>Removing the fields resets the user to the default moods. My added mood is present and correct, and the nasty error is gone. Hope this helps someone <img src='http://kccricket.net/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Les</title>
		<link>http://kccricket.net/archives/recent-mood-issues/comment-page-1#comment-1168</link>
		<dc:creator>Les</dc:creator>
		<pubDate>Sat, 16 Dec 2006 10:43:15 +0000</pubDate>
		<guid isPermaLink="false">http://kccricket.net/archives/19#comment-1168</guid>
		<description>This error just bit me this morning. Hope a fix can be sorted out soon :)</description>
		<content:encoded><![CDATA[<p>This error just bit me this morning. Hope a fix can be sorted out soon <img src='http://kccricket.net/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: !!blue</title>
		<link>http://kccricket.net/archives/recent-mood-issues/comment-page-1#comment-1163</link>
		<dc:creator>!!blue</dc:creator>
		<pubDate>Thu, 14 Dec 2006 19:02:36 +0000</pubDate>
		<guid isPermaLink="false">http://kccricket.net/archives/19#comment-1163</guid>
		<description>I look forward to a fix for this issue. :) I don&#039;t receive the error above, what happens to me is that the default and newly added fields disappear and I get 5 blank fields starting with ID #21.</description>
		<content:encoded><![CDATA[<p>I look forward to a fix for this issue. <img src='http://kccricket.net/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  I don&#8217;t receive the error above, what happens to me is that the default and newly added fields disappear and I get 5 blank fields starting with ID #21.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

