<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Fastspot Presents: Find your leaf in Carroll Park!</title>
	<link>http://bmore-urbanforestproject.org/blog/baltimore/fastspot-presents-find-your-leaf-in-carroll-park/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 02:15:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Aimee</title>
		<link>http://bmore-urbanforestproject.org/blog/baltimore/fastspot-presents-find-your-leaf-in-carroll-park/#comment-592</link>
		<dc:creator>Aimee</dc:creator>
		<pubDate>Thu, 12 Jun 2008 04:15:08 +0000</pubDate>
		<guid>http://bmore-urbanforestproject.org/blog/baltimore/fastspot-presents-find-your-leaf-in-carroll-park/#comment-592</guid>
		<description>Hey, I am having the same AJAX WP-Polls problem. &lt;blockquote&gt;

I thought it was me from editing the poll template...guess not. I checked to see if it was from using FireFox 3 RC2 by using a different browser - definitely isn't that.

I deleted the plugin, emptied the MYSQL poll databases, then I re-downloaded the plugin, and re-activated - not that either.

I restored the default templates - not that either. (Otherwise, we wouldn't have invalid markup.) My custom template was validated as XHTML as well.

And I just found out this problem occurred today...this is irking me.&lt;/blockquote&gt;

Let me know if you get it fixed.</description>
		<content:encoded><![CDATA[<p>Hey, I am having the same AJAX WP-Polls problem.<br />
<blockquote>
<p>I thought it was me from editing the poll template&#8230;guess not. I checked to see if it was from using FireFox 3 RC2 by using a different browser - definitely isn&#8217;t that.</p>
<p>I deleted the plugin, emptied the MYSQL poll databases, then I re-downloaded the plugin, and re-activated - not that either.</p>
<p>I restored the default templates - not that either. (Otherwise, we wouldn&#8217;t have invalid markup.) My custom template was validated as XHTML as well.</p>
<p>And I just found out this problem occurred today&#8230;this is irking me.</p></blockquote>
<p>Let me know if you get it fixed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
