Emailed Author: There are issues with your plugin code. Please read this ENTIRE email, address all listed issues, and reply to this email with your corrected code attached. It is required for you to read and reply to these emails, and failure to do so will result in your plugin being rejected.
## Calling images remotely
Offloading images to your own server is disallowed.
http://upscalethought.com/usts-products/images/banner-772x250.jpg
http://www.abdullahmamun.com/usts/products/docs/wp-nexgen-gallery-search/documentation/images/Nexgen-Gallery-Images.jpg
and so on
Please include all images needed for your plugin locally.
## Calling files remotely
http://cdn.jsdelivr.net/hammerjs/2.0.3/hammer.min.js
Offloading images, js, css, cgi, and other scripts to Google (or jquery.com or anywhere else frankly) is disallowed because you're introducing an unnecessary dependency on another site. If the file you're trying to use isn't a part of WordPress Core, then you should include it -locally- in your plugin, not remotely. If the file IS included in WordPress core, please call that instead.
The one exception to this rule is if your plugin is performing a service. We will permit this on a case by case basis, however since this can be confusing, we have some examples of what are not permitted:
* Offloading jquery CSS files to Google - You should include the CSS in your plugin.
* Inserting an iframe with a help doc - A link, or including the docs in your plugin is preferred.
* Calling images from your own domain - They should be included in your plugin.
Here are some examples of what we would permit:
* Calling font families from Google or their approved CDN (if GPL compatible)
* API calls back to your server to process possible spam comments (like Akismet)
* Offloading comments to your own servers (like Disqus)
* oEmbed calls to a service provider (like Twitter or YouTube)
Please remove this dependency from your plugin and, if possible, include all files within the plugin (that is not called remotely). If instead you feel you ARE providing a service, please re-write your readme.txt in a manner that explains the service, the servers being called, and if any account is needed to connect.
## Including jquery files (or calling them remotely)
http://code.jquery.com/jquery-latest.min.js AND you have your own JS in the /assets/js/ folder
WordPress includes its own version of jquery and many other similar JS files, which have all 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. You need to both change your code to use our jquery as well as remove the unused files. Remember! Keeping unused files out of your plugins makes them smaller and less potentially vulnerable! if you have any jquery files included in your plugin that WP core has, just delete them.
Offloading jquery js, css, and other scripts to Google (or jquery.com or anywhere else frankly) is similarly disallowed for the same reasons, but also because you're introducing an unnecessary dependency on another site. If the file you're trying to use isn't a part of WordPress Core, then you should include it -locally- in your plugin, not remotely.
If your code doesn't work with the built-in versions of jquery, it's most likely a no conflict issue. If you can't guess, we -really- want you to use our JS files, and if you can't, we need to know why so we can fix things for everyone. If you're just including it because you want to support old versions of WP, or because you think they may not have jquery, please don't. If they don't have the default jquery, a lot more than your plugin will break. And if they're on older versions of WordPress, they need to upgrade, and we don't recommend you support anything except the most recent version of WP and one release back.
## Please use wp_enqueue commands
Your plugin is using <style> and/or <link> tags to insert CSS/JS
<link type="text/css" media="all" rel="stylesheet" href="'.GEN_USTS_NGGS_PHOTOCRATI_PLUGIN_URL.'/assets/css/style.css" />
You should be using the built in functions for this:
https://codex.wordpress.org/Function_Reference/wp_enqueue_script
https://codex.wordpress.org/Function_Reference/wp_enqueue_style
If you're trying to enqueue on the admin pages you'll want to use the admin enqueues
https://codex.wordpress.org/Plugin_API/Action_Reference/admin_enqueue_scripts
https://codex.wordpress.org/Plugin_API/Action_Reference/admin_print_scripts
https://codex.wordpress.org/Plugin_API/Action_Reference/admin_print_styles
## Using Fancybox 2.0
It's required that all code be compatible with GPL to be included in our repository.
"'.GEN_USTS_NGGS_PHOTOCRATI_PLUGIN_URL.'/includes/fancybox/jquery.fancybox.js?v=2.1.5
FancyBox v2 and up is not GPL compatible, as it has been licensed Creative Commons.
Please remove FancyBox and alter the plugin so it is not required. If you cannot alter the code, we suggest you find alternate code that is GPL compatible and use that instead. For more information on what types of licenses are compatible with GPL, please review the following links:
http://www.gnu.org/licenses/license-list.html
http://www.gnu.org/licenses/gpl-faq.html#AllCompatibility
----
Please make sure you've addressed ALL issues brought up in this email. When you've corrected your code, reply to this email with the updated code attached as a zip, or provide a link to the new code for us to review. If you have questions, concerns, or need clarification, please reply to this email and just ask us.