== Calling wp-load.php in a file ==

Including wp-config.php, wp-blog-header.php, wp-load.php, or pretty much any other WordPress core file that you have to call directly via an include is not a good idea and we cannot approve a plugin that does so unless it has a very good reason to load the file(s). It is prone to failure since not all WordPress installs have the exact same file structure.

Usually plugins will include wp-config.php or wp-load.php in order to gain access to core WordPress functions, but there are much better ways to do this.

It's best if you tie your processing functions (the ones that need but don't have access to core functions) into an action hook, such as "init" or "admin_init".

Please consult the Plugins API reference for more information: http://codex.wordpress.org/Plugin_API

If you're trying to use AJAX, please read this: http://codex.wordpress.org/AJAX_in_Plugins

== Missing a readme ==

Your plugin is incomplete and is missing a valid readme.txt file. Please create one based on this:
http://wordpress.org/extend/plugins/about/readme.txt

Alternately, you can use this tool to generate one:
http://tools.trepmal.com/wp-readme-generator/

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 :)

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.

Keep in mind, a readme.MD is not the same as a readme.TXT - the formatting for markup is different.

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.

All plugins are expected to be submitted with the code complete and ready to go, including a valid readme.txt file. Either you did not include a direct link to your code with your submission, or the link you provided was invalid/inaccessible. Could you please reply with a link so the plugin can be downloaded? Alternately you can reply to this and attach your .zip or .rar file.

Note: Please DO NOT just send the same link. We probably had issues getting your site to load, so sending the same link will likely get you the same reply.

If your plugin is not complete, and you need a place to version control your code while you work on it, you can use GitHub to safely host your code while you're developing. We do not accept incomplete/non-functional plugins.

Please reply with 7 days. If a reply is not received the submission will be rejected and you will have to submit the plugin again, with code, should you want your plugin hosted.

Thanks.

Also put in a real donate URL (not example.com) or remove the line.

When you've done that, 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.

The files for retrieving social network counts, ajax-cube3x-gplus-count.php for example, all have vulnerabilities in them. You are accepting a callback via $_GET['callback'] but there is no sanitation going on, meaning that someone could easily inject a script via the callback and take control of the site.

You need to ensure you have validated the request before anything is processed.

Once you've fixed the issues, respond to this email and attach the updated version for re-review.

Pippin