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 significant delays with your plugin being accepted.
## Hardcoded plugin folder name
Your plugin won’t work via our directory because you hardcoded in the plugin’s folder. You’ve defined your plugin name in the plugins_url() function like this:
plugin_dir_url( ‘spinkx-content-marketing’ ) . ‘spinkx-content-marketing/assets/images/spinkx-ico.svg’
Please read http://codex.wordpress.org/Function_Reference/plugins_url – you’ll notice how we have a __FILE__ parameter used in most examples. If you change your plugin to use that, it will work no matter what the folder name is.
It should be this:
plugins_url( ‘assets/images/spinkx-ico.svg’, __FILE__ )
## Calling file locations poorly
The way your plugin is referencing other files is not going to work with all setups of WordPress.
When you hardcode in paths, or assume that everyone has WordPress in the root of their domain, you cause anyone using ‘Giving WordPress it’s own directory’ (a VERY common setup) to break. In addition, WordPress allows users to change the name of wp-content, so you would break anyone who choses to do so.
Please review http://codex.wordpress.org/Determining_Plugin_and_Content_Directories and update your plugin accordingly. And don’t worry about supporting WordPress 2.x or lower. We don’t encourage it nor expect you to do so, so save yourself some time and energy.
wp_enqueue_script( ‘pixel-js’, $ ajxrequrl . ‘/wp-content/plugins/spinkx-server/assets/js/spinkxut.js’ );
wp_enqueue_script( ‘pixel-js’, plugins_url( ‘assets/js/spinkxut.js’ , __FILE__ ) );
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.
(While we have tried to make this review as exhaustive as possible we, like you, are humans and may have missed things. As such, we will re-review the ENTIRE plugin when you send it back to us. We appreciate your patience and understanding in this.)