<?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: site preloader - Recent Posts</title>
		<link>http://wordpress.org/plugins/tags/site-preloader</link>
		<description>WordPress Plugins &#187; Tag: site preloader - Recent Posts</description>
		<language>en-US</language>
		<pubDate>Wed, 22 May 2013 19:54:02 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.1</generator>
				<atom:link href="http://wordpress.org/plugins/rss/tags/site-preloader" rel="self" type="application/rss+xml" />

		<item>
			<title>Ultimate Preloader</title>
			<link>http://wordpress.org/plugins/ultimate-preloader/#post-49428</link>
			<pubDate>Tue, 12 Feb 2013 01:58:15 +0000</pubDate>
			<dc:creator>Ipstenu (Mika Epstein)</dc:creator>
			<guid isPermaLink="false">49428@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>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>Ultimate Preloader</title>
			<link>http://wordpress.org/plugins/ultimate-preloader/#post-49370</link>
			<pubDate>Sun, 10 Feb 2013 19:46:58 +0000</pubDate>
			<dc:creator>enid.colic</dc:creator>
			<guid isPermaLink="false">49370@http://wordpress.org/plugins/</guid>
			<description><![CDATA[Ultimate Preloader will create a preloading screen for your website before all your images (including the images in CSS) are fully loaded.]]></description>
					</item>

	</channel>
</rss>
