== Calling wp-load.php directly ==

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

== Calling your own version of jquery (and not using wp_enequeue_scripts() ==

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.

Please review http://codex.wordpress.org/Function_Reference/wp_enqueue_script and update your plugin accordingly.

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.

You need to remove all jquery files from your plugin if they're included in WP core. Please check all your resources, as there are multiple instances in some of your 3rd party locations.

==Encrypted/Obfuscated code ==

eval(function(p,a,c,k,e,d) is found in one of your jquery files.

Using encryption methods like base64() or p,a,c,k,e,r to hide your code or otherwise make it human-unreadable is in violation of the repository guidelines, found at: http://wordpress.org/extend/plugins/about/guidelines/

In specific, the fourth guideline, which reads: "4. No obfuscated code."

It's fine to compress your code and minify, but it's not okay to hide it. All code must be human readable for inclusion in this repository.

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.

Currently you have very generic function names that are likely to conflict with functions from other plugins or themes.

Every function in your plugin should be prefixed with a prefix that is unique to your plugin.

For example, if your plugin is called "Easy Custom Post Types", then you might prefix your functions with ecpt_{your function name here}.

When you have updated your plugin code, respond to this email with the new code for us to review again.

All plugins are expected to be submitted with the code complete and ready to go, including a valid readme.txt file. 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.

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.