<?xml version="1.0" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Forum | WP Events Calendar</title>
	<link>http://www.wp-eventscalendar.com/forum/announcements/</link>
	<description><![CDATA[]]></description>
	<generator>Simple:Press Forum Version 4.2.2</generator>
	<atom:link href="http://www.wp-eventscalendar.com/forum/?announcements&#038;xfeed=forum" rel="self" type="application/rss+xml" />
<item>
	<title>is150 on Events Calendar 6.6 beta is now available</title>
	<link>http://www.wp-eventscalendar.com/forum/announcements/events-calendar-66-beta-is-now-available/#p693</link>
	<category>Announcements</category>
	<guid isPermaLink="true">http://www.wp-eventscalendar.com/forum/announcements/events-calendar-66-beta-is-now-available/#p693</guid>
	<description><![CDATA[<p>will upgrade and get back <img title="Wink" src="/wordpress/wp-content/forum-smileys/sf-wink.gif" alt="Wink" /></p>
]]></description>
	<pubDate>Wed, 09 Sep 2009 03:12:19 +0000</pubDate>
</item>
<item>
	<title>laplix on Events Calendar 6.6 beta is now available</title>
	<link>http://www.wp-eventscalendar.com/forum/announcements/events-calendar-66-beta-is-now-available/#p669</link>
	<category>Announcements</category>
	<guid isPermaLink="true">http://www.wp-eventscalendar.com/forum/announcements/events-calendar-66-beta-is-now-available/#p669</guid>
	<description><![CDATA[<p>The WP Events Calendar Team is happy to announce the release of a beta version of&#160; EC 6.6.</p>
<p>This release fixes many issues that were reported by our users. The major one being the problems people faced with WP 2.8.</p>
<p>EC is now compatible with the most recent version of WordPress, a.k.a WP 2.8.4.</p>
<p><strong>This </strong><strong>is a beta release</strong>. That means that you folks have a job to do: testing this plugin and trying to kill it. And then, when you&#39;ve done the assassination operation, make sure to write a complete report about your exploit in the bug tracker so we can resuscitate the poor thing.</p>
<p>On a more serious note, we have tried to make EC more robust so we can wait for the next generation Heirem is going to provide.</p>
<p>These are the issues we fixed:</p>
<ul>
<li>WPEC is now WP 2.7 and 2.8 ready. This fixes issues #20, #21 and #38.</li>
<li>Fixed issue #16: Larger description in textarea.</li>
<li>Fixed issue #17: Consistency with WP plugin UI conventions</li>
<li>Fixed issue #18: displayLarge uses $options before it is set.</li>
<li>Fixed issue #22: Click for more info not working</li>
<li>Fixed issue #27: Events not showing on widget in public view.</li>
<li>Fixed issue #29: Firefox reported 2 errors.</li>
<li>Fixed issue #31: Start / End Times do not appear to take start / end date into consideration.</li>
<li>Fixed issue #32: Tooltips doesn&#39;t show correctly when there is a large amount of text in the description. This is partly resolved in fact. The tooltip will grow larger depending on the text size but a very large amount of text will still show this problem. I would suggest making a post if you have too much text.</li>
<li>Fixed issue #34: Wrong timezone: US (am/pm) vs. European time.</li>
<li>Fixed issue #37: Ajax character set problems with Spanish language (and other too for sure).</li>
<li>Fixed issue #40: Post titles are incorrect when they contain an &#39;.</li>
<li>Fixed issue #42: Conflict with Register Plus plugin. pluggable.php is a BAD THING! When we start doing reminders and stuff like that, we may need to override some of these functions which will again break compatibility.</li>
<li>Fixed issue #45: Showing incorrect day.</li>
<li>Fixed issue #46: Widget in Sidebar will not change to Calendar view .</li>
<li>Fixed issue #48: WordPress Database Error: invalid SQL syntax.</li>
<li>Fixed issue #52: spacing between line too close.</li>
<li>Fixed issue #56: Thickbox and &#39;moving&#39; WordPress.</li>
<li>Added license file and comments.</li>
<li>Adapted the readme.txt file to the latest spec from wordpress.org</li>
</ul>
<p>We hope you enjoy it. <img title="Laugh" src="/wordpress/wp-content/forum-smileys/sf-laugh.gif" alt="Laugh" /></p>
<p>The EC Team</p>
<div id="_mcePaste" style="overflow: hidden; position: absolute; left: -10000px; top: 173px; width: 1px; height: 1px;">WPEC is now WP 2.7 and 2.8 ready. This fixes issues #20, #21 and #38..<br /> Fixed issue #17: Consistency with WP plugin UI conventions.<br /> Fixed issue #16: Larger description in textarea.<br /> Fixed issue #18: displayLarge uses $options before it is set.<br /> Fixed issue #22: Click for more info not working<br /> Fixed issue #27: Events not showing on widget in public view.<br /> Fixed issue #29: Firefox reported 2 errors.<br /> Fixed issue #31: Start / End Times do not appear to take start / end date into consideration.<br /> Fixed issue #32: Tooltip doesn&#39;t show correctly when there is a large amount of text in the description. This is partly resolved in fact. The tooltip will grow larger depending on the text size but a very large amount of text will still shoow this problem. I would suggest making a post if you have too much text.<br /> Fixed issue #34: Wrong timezone: US (am/pm) vs. European time.<br /> Fixed issue #37: Ajax character set problems with Spanish language (and other too for sure).<br /> Fixed issue #40: Post titles are incorrect when they contain an &#39;.<br /> Fixed issue #42: Conflict with Register Plus plugin. pluggable.php is a BAD THING! When we start doing reminders and stuff like that, we may need to override some of these functions which will again break compatibility.<br /> Fixed issue #45: Showing incorrect day.<br /> Fixed issue #46: Widget in Sidebar will not change to Calendar view .<br /> Fixed issue #48: WordPress Database Error: invalid SQL syntax.<br /> Fixed issue #52: spacing between line too close.<br /> Fixed issue #56: Thickbox and &#39;moving&#39; WordPress.<br /> Added license file and comments.<br /> Adapted the readme.txt file to the latest spec from wordpess.org</div>
]]></description>
	<pubDate>Sat, 05 Sep 2009 16:18:28 +0000</pubDate>
</item>
</channel>
</rss>