<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.1" -->
<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"
		>
	<channel>
		<title>WordPress Plugins &#187; Tag: events - Recent Posts</title>
		<link>http://wordpress.org/plugins/tags/events</link>
		<description>WordPress Plugins &#187; Tag: events - Recent Posts</description>
		<language>en-US</language>
		<pubDate>Thu, 23 May 2013 23:59:38 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.1</generator>
				<atom:link href="http://wordpress.org/plugins/rss/tags/events" rel="self" type="application/rss+xml" />

		<item>
			<title>AM Events</title>
			<link>http://wordpress.org/plugins/am-events/#post-52916</link>
			<pubDate>Sun, 05 May 2013 17:54:04 +0000</pubDate>
			<dc:creator>Atte Moisio</dc:creator>
			<guid isPermaLink="false">52916@http://wordpress.org/plugins/</guid>
			<description><![CDATA[Adds an additional interface for events similar to normal posts. Also includes a widget for upcoming events.]]></description>
					</item>
		<item>
			<title>Events Handler</title>
			<link>http://wordpress.org/plugins/events-handler/#post-52850</link>
			<pubDate>Fri, 03 May 2013 16:34:12 +0000</pubDate>
			<dc:creator>wp-chd-developer</dc:creator>
			<guid isPermaLink="false">52850@http://wordpress.org/plugins/</guid>
			<description><![CDATA[Events Handler enables to manage events and future happenings and show them on your wordpress site.]]></description>
					</item>
		<item>
			<title>Event Organiser Google Checkout</title>
			<link>http://wordpress.org/plugins/event-organiser-google-checkout/#post-52277</link>
			<pubDate>Fri, 19 Apr 2013 14:10:14 +0000</pubDate>
			<dc:creator>Stephen Harris</dc:creator>
			<guid isPermaLink="false">52277@http://wordpress.org/plugins/</guid>
			<description><![CDATA[Sell event tickets through Google Checkout. Requries Event Organiser &#38; Event Organiser Pro]]></description>
					</item>
		<item>
			<title>Klipspringer</title>
			<link>http://wordpress.org/plugins/klipspringer/#post-52008</link>
			<pubDate>Sun, 14 Apr 2013 05:05:15 +0000</pubDate>
			<dc:creator>Ipstenu (Mika Epstein)</dc:creator>
			<guid isPermaLink="false">52008@http://wordpress.org/plugins/</guid>
			<description><![CDATA[<p>Emailed Author: Your plugin is incomplete and is missing a valid readme.txt file. Please create one based on this:<br />
<a href="http://wordpress.org/extend/plugins/about/readme.txt" rel="nofollow">http://wordpress.org/extend/plugins/about/readme.txt</a> </p>
<p>Alternately, you can use this tool to generate one:<br />
<a href="http://tools.trepmal.com/wp-readme-generator/" rel="nofollow">http://tools.trepmal.com/wp-readme-generator/</a> </p>
<p>A readme.txt is needed so your plugin will display correctly in our repository, but also so we can make sure you're providing the users with all the information they need before they install your plugin. Our goal with this is to make sure everyone knows what they're installing and what they need to do before they install it. No surprises :)</p>
<p>This is especially important if your plugin is making calls back to your own servers. For the most part, we do not permit offloading of images or code, however in the case where you are providing a service (like Disqus or Akismet or Twitter), we permit it. The catch is you have to actually explain this to the layman in your readme, so they know where data is going.</p>
<p>Keep in mind, a readme.MD is not the same as a readme.TXT - the formatting for markup is different.</p>
<p>Please send a link so the completed plugin can be downloaded. Alternately you can reply to this and send a .zip or .rar file. As this is for a new plugin request, please reply within seven days of this email or we will reject your plugin.
</p>]]></description>
					</item>
		<item>
			<title>Klipspringer</title>
			<link>http://wordpress.org/plugins/klipspringer/#post-51974</link>
			<pubDate>Sat, 13 Apr 2013 06:05:39 +0000</pubDate>
			<dc:creator>stacigh</dc:creator>
			<guid isPermaLink="false">51974@http://wordpress.org/plugins/</guid>
			<description><![CDATA[A slide-down widgetized area for your WordPress website which can be used for anything from shopping carts to a contact form to displaying tweets.]]></description>
					</item>
		<item>
			<title>GA Link Tracker</title>
			<link>http://wordpress.org/plugins/ga-link-tracker/#post-51566</link>
			<pubDate>Fri, 05 Apr 2013 01:25:16 +0000</pubDate>
			<dc:creator>Ipstenu (Mika Epstein)</dc:creator>
			<guid isPermaLink="false">51566@http://wordpress.org/plugins/</guid>
			<description><![CDATA[<p>Emailed Author: Your plugin is incomplete and is missing a valid readme.txt file. Please create one based on this:<br />
<a href="http://wordpress.org/extend/plugins/about/readme.txt" rel="nofollow">http://wordpress.org/extend/plugins/about/readme.txt</a> </p>
<p>Alternately, you can use this tool to generate one:<br />
<a href="http://tools.trepmal.com/wp-readme-generator/" rel="nofollow">http://tools.trepmal.com/wp-readme-generator/</a> </p>
<p>A readme.txt is needed so your plugin will display correctly in our repository, but also so we can make sure you're providing the users with all the information they need before they install your plugin. Our goal with this is to make sure everyone knows what they're installing and what they need to do before they install it. No surprises :)</p>
<p>This is especially important if your plugin is making calls back to your own servers. For the most part, we do not permit offloading of images or code, however in the case where you are providing a service (like Disqus or Akismet or Twitter), we permit it. The catch is you have to actually explain this to the layman in your readme, so they know where data is going.</p>
<p>Keep in mind, a readme.MD is not the same as a readme.TXT - the formatting for markup is different.</p>
<p>Please send a link so the completed plugin can be downloaded. Alternately you can reply to this and send a .zip or .rar file. As this is for a new plugin request, please reply within seven days of this email or we will reject your plugin.
</p>]]></description>
					</item>
		<item>
			<title>GA Link Tracker</title>
			<link>http://wordpress.org/plugins/ga-link-tracker/#post-51453</link>
			<pubDate>Tue, 02 Apr 2013 21:01:25 +0000</pubDate>
			<dc:creator>project107</dc:creator>
			<guid isPermaLink="false">51453@http://wordpress.org/plugins/</guid>
			<description><![CDATA[A tiny WordPress plugin to track events of link clicks in the main content area of the site.]]></description>
					</item>
		<item>
			<title>DeMomentSomTres Facebook Events List</title>
			<link>http://wordpress.org/plugins/demomentsomtres-facebook-events-list/#post-51050</link>
			<pubDate>Fri, 22 Mar 2013 12:29:01 +0000</pubDate>
			<dc:creator>Marc Queralt i Bassa</dc:creator>
			<guid isPermaLink="false">51050@http://wordpress.org/plugins/</guid>
			<description><![CDATA[A plugin to generate a list of events from a Facebook fan page using a shortcode.]]></description>
					</item>
		<item>
			<title>Future</title>
			<link>http://wordpress.org/plugins/future/#post-50889</link>
			<pubDate>Tue, 19 Mar 2013 00:10:10 +0000</pubDate>
			<dc:creator>mordauk</dc:creator>
			<guid isPermaLink="false">50889@http://wordpress.org/plugins/</guid>
			<description><![CDATA[<p>Emailed Author: In order to approve your plugin, you will need to make a few improvements.</p>
<p>Currently you have very generic function names that are likely to conflict with functions from other plugins or themes.</p>
<p>Every function in your plugin should be prefixed with a prefix that is unique to your plugin.</p>
<p>For example, if your plugin is called "Easy Custom Post Types", then you might prefix your functions with ecpt_{your function name here}.</p>
<p>When you have updated your plugin code, respond to this email with the new code for us to review again.
</p>]]></description>
					</item>
		<item>
			<title>Future</title>
			<link>http://wordpress.org/plugins/future/#post-50871</link>
			<pubDate>Mon, 18 Mar 2013 03:59:03 +0000</pubDate>
			<dc:creator>msudvarg</dc:creator>
			<guid isPermaLink="false">50871@http://wordpress.org/plugins/</guid>
			<description><![CDATA[Integrates future-dated posts into your blog. Adds future posts and category selection to Wordpress&#039;s built-in calendar widget.]]></description>
					</item>
		<item>
			<title>WPArtists</title>
			<link>http://wordpress.org/plugins/wp-artists-lite/#post-50719</link>
			<pubDate>Thu, 14 Mar 2013 15:31:08 +0000</pubDate>
			<dc:creator>b4ucode</dc:creator>
			<guid isPermaLink="false">50719@http://wordpress.org/plugins/</guid>
			<description><![CDATA[WP Artists Lite is a  Music solution for WordPress. Perfect for a Band or Label Directory website.]]></description>
					</item>
		<item>
			<title>WPSupervisor Client</title>
			<link>http://wordpress.org/plugins/wpsupervisor-client/#post-50643</link>
			<pubDate>Tue, 12 Mar 2013 19:21:38 +0000</pubDate>
			<dc:creator>mordauk</dc:creator>
			<guid isPermaLink="false">50643@http://wordpress.org/plugins/</guid>
			<description><![CDATA[<p>Emailed Author: Including your own plugin update script is not permitted if you want to host your plugin on WordPress.org. Unless you remove the updater from WP Supervisor Client, we cannot approve your plugin.
</p>]]></description>
					</item>
		<item>
			<title>WPSupervisor Client</title>
			<link>http://wordpress.org/plugins/wpsupervisor-client/#post-50621</link>
			<pubDate>Tue, 12 Mar 2013 07:12:57 +0000</pubDate>
			<dc:creator>Profit Marketer</dc:creator>
			<guid isPermaLink="false">50621@http://wordpress.org/plugins/</guid>
			<description><![CDATA[Install this plugin on unlimited sites and manage them all from a central dashboard.
This plugin communicates with your WPSupervisor Admin Panel.]]></description>
					</item>
		<item>
			<title>WEeventscalendar</title>
			<link>http://wordpress.org/plugins/weeventscalendar/#post-50083</link>
			<pubDate>Wed, 27 Feb 2013 16:31:51 +0000</pubDate>
			<dc:creator>weabers</dc:creator>
			<guid isPermaLink="false">50083@http://wordpress.org/plugins/</guid>
			<description><![CDATA[Create, and manage a new type of content, the events, also setup a shortcodes for event calendar and a list year-month-day of events.]]></description>
					</item>
		<item>
			<title>Full Calendar Js</title>
			<link>http://wordpress.org/plugins/full-calendar-js/#post-49931</link>
			<pubDate>Sun, 24 Feb 2013 20:56:15 +0000</pubDate>
			<dc:creator>mordauk</dc:creator>
			<guid isPermaLink="false">49931@http://wordpress.org/plugins/</guid>
			<description><![CDATA[<p>Emailed Author: WordPress includes its own version of jquery, which has been rigorously tested with WP and many of the most common plugins. In order to provide the best compatibility and experience for our users, we ask that you not package your own (especially not an older version) and instead use wp_enqueue_script() to pull in WordPress’s version.</p>
<p>Please review <a href="http://codex.wordpress.org/Function_Reference/wp_enqueue_script" rel="nofollow">http://codex.wordpress.org/Function_Reference/wp_enqueue_script</a> and update your plugin accordingly.</p>
<p>Keep in mind: Offloading the default jquery and other scripts to Google is similarly disallowed. If your code doesn't work with the built-in jQuery, it's most likely a noconflict issue. If you can't guess, we -really- want you to use our jquery, and if you can't, we need to know why so we can fix things for everyone.</p>
<p>When you've corrected your code, reply to this email with the updated code attached, or provide a link to the new code.
</p>]]></description>
					</item>

	</channel>
</rss>
