== 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.

function xovi_includeHighcharts() {
wp_enqueue_script( 'highcharts', "http://code.highcharts.com/highcharts.js", false );
wp_enqueue_script( 'highchartsExport', "http://code.highcharts.com/modules/exporting.js", false );
wp_enqueue_script( 'highchartsOptions', plugins_url("javascript/highchart_options.js", __FILE__ ), false);
}
add_action('admin_enqueue_scripts','xovi_includeHighcharts');

HighCharts should be included in your plugin code, however it's not compatible with the GPL license structure, so you can't use it at all. Please remove it and replace it with something else. http://shop.highsoft.com/highcharts.html

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.