<?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>Event Calendar &#187; Documentation</title>
	<atom:link href="http://wpcal.firetree.net/category/documentation/feed/" rel="self" type="application/rss+xml" />
	<link>http://wpcal.firetree.net</link>
	<description>plugin for wordpress</description>
	<lastBuildDate>Thu, 23 Apr 2009 16:44:37 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.1.1</generator>
	<item>
		<title>ec3_the_schedule()</title>
		<link>http://wpcal.firetree.net/2007/10/25/ec3_the_schedule/</link>
		<comments>http://wpcal.firetree.net/2007/10/25/ec3_the_schedule/#comments</comments>
		<pubDate>Thu, 25 Oct 2007 11:47:14 +0000</pubDate>
		<dc:creator><![CDATA[mark]]></dc:creator>
				<category><![CDATA[Documentation]]></category>

		<guid isPermaLink="false">http://wpcal.firetree.net/2007/10/25/ec3_the_schedule/</guid>
		<description><![CDATA[Formats the schedule for the current post. If you want to echo the result directly onto the page, This is the call you want. For HTML as a string use ec3_get_schedule() Overview ec3_the_schedule() is useful to produce a controllable (different &#8230; <a href="http://wpcal.firetree.net/2007/10/25/ec3_the_schedule/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>Formats the schedule for the current post. If you want to echo the result directly onto the page, This is the call you want. For HTML as a string use ec3_get_schedule()</p>
<h3>Overview</h3>
<p>ec3_the_schedule() is useful to produce a controllable (different from default) HTML output for use within a post, especially when you wish to style the output using div&#8217;s instead of tables. The command takes the form of</p>
<p>ec3_the_schedule(&#8216;<strong>$format_single</strong>&#8216;,&#8217;<strong>$format_range</strong>&#8216;,&#8217;<strong>$format_wrapper</strong><br />
&#8216;);</p>
<p>all of the parameters above are optional, and are explained below</p>
<h3>Parameters</h3>
<p><strong>$format_single</strong> (OPTIONAL)</p>
<p>DEFAULT=’&lt;tr&gt;&lt;td colspan=”3″&gt;%s&lt;/td&gt;&lt;/tr&gt;’<br />
Events that only have a start time (no duration) are generated using this template. %s is a placeholder for the time.<br />
<strong>$format_range (OPTIONAL)</p>
<p>DEFAULT=’&lt;tr&gt;&lt;td class=”ec3_start”&gt;%1$s&lt;/td&gt;’<br />
  . ‘&lt;td class=”ec3_to”&gt;%3$s&lt;/td&gt;&lt;td class=”ec3_end”&gt;%2$s&lt;/td&gt;&lt;/tr&gt;’<br />
Events that have a start and end time are generated using this template. %1$s is a placeholder for the start, and %2$s is a placeholder for the end time. %3$s is a placeholder for the word “to”, which may be translated if you are using a localised version of EventCalendar.</p>
<p></strong><strong>$format_wrapper</strong> (OPTIONAL)</p>
<p>DEFAULT=’&lt;tableclass=”ec3_schedule”&gt;%s&lt;/table&gt;’<br />
A template for the whole result. The default generates a table, but you may prefer to have it generate a div, or leave it blank. %s is a placeholder.<br />
<strong>Examples</p>
<p><code>&lt;?php ec3_the_schedule('%1$s ');?&gt;   </code><br />
This fragment will generate output in the form<br />
&#8220;(Event date) (Event Start Time)&#8221; ie December 9, 2007 9:00 am</p>
<p></strong><code>&lt;?php ec3_the_schedule('%1$s ','','&lt;div class="ec3_the_schedule" &gt;%s &lt;/div&gt;');?&gt;   </code><br />
This fragment will generate output in the form<br />
<code>&lt;div class="ec3_the_schedule"&gt;December 9, 2007 9:00 am  &lt;/div&gt;</code></p>
]]></content:encoded>
			<wfw:commentRss>http://wpcal.firetree.net/2007/10/25/ec3_the_schedule/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>To www or not to www?</title>
		<link>http://wpcal.firetree.net/2007/02/24/to-www-or-not-to-www/</link>
		<comments>http://wpcal.firetree.net/2007/02/24/to-www-or-not-to-www/#comments</comments>
		<pubDate>Fri, 23 Feb 2007 23:58:51 +0000</pubDate>
		<dc:creator><![CDATA[alex]]></dc:creator>
				<category><![CDATA[Documentation]]></category>

		<guid isPermaLink="false">http://wpcal.firetree.net/2007/02/24/to-www-or-not-to-www/</guid>
		<description><![CDATA[Thanks to Rusty Smith for answering this question on the mailing list. I&#8217;ve added a shorter version to the FAQ. To get to my url, the user doesn&#8217;t have to type the &#8220;www&#8221; as part of the url name so &#8230; <a href="http://wpcal.firetree.net/2007/02/24/to-www-or-not-to-www/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p><i>Thanks to Rusty Smith for answering this question on the mailing list. I&#8217;ve added a shorter version to the FAQ.</i></p>
<blockquote><p>To get to my url, the user doesn&#8217;t have to type the &#8220;www&#8221; as part of the url name so I had the name listed without it. However, most Internet users still generally type in the &#8220;www&#8221; as part of the web address. I was hoping that the plugin would work whether the &#8220;www&#8221; was listed in the url or not. Guess I will make sure the &#8220;www&#8221; is listed in the WordPress configuration since that is what would generally be typed in.</p>
<p>Is this something that might be fixed in a future release? Whether the url has the &#8220;www&#8221; in the name should be invisible to the end user and hopefully shouldn&#8217;t impact how a plugin works.</p></blockquote>
<p>Brian and others that run into this problem:<br />
This is NOT an EventCalendar problem, it actually breaks WordPress, but most people do not realize it. If you want to see how it breaks WordPress, log in to your blog at www.yourblog.com and then go to yourblog.com (or vice versus) and you will see that you are no longer logged in. You should decide whether you want www or not (I have no dog in the fight, but you may want to check out no-www.org to hear from folks that do). Then you paste the following lines into your .htaccess file, changing the domain name to match that of your site:</p>
<pre>RewriteEngine On
RewriteCond %{HTTP_HOST} ^www\\.domain\\.com$ [NC]
RewriteRule ^(.*)$ http://domain.com/$1 [R=301,L]</pre>
<p>This should silently redirect any call to www.yoursite.com to yoursite.com without the www. An added benefit is that any inbound link to your site will redirect as well, which makes the searchbots see your site as one instead of two, which should theoretically increase your popularity for those that worry about such things.</p>
<p>The above works on apache servers, but if you are installed on a windows IIS machine you may have to install any of the <a href="http://www.justinshattuck.com/wordpress-www-redirect-plugin/">various</a> <a href="http://photomatt.net/2006/06/13/wordpress-no-www/">plugins</a> that do a similar redirect. I have not tried them, but give them a shot and report back. They may only work on apache servers as well. IIS probably has some sort of redirect capabilities, maybe someone knows how to do that?</p>
]]></content:encoded>
			<wfw:commentRss>http://wpcal.firetree.net/2007/02/24/to-www-or-not-to-www/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
