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.
## Too Many Tags
Your plugin is using too many tags. We ask that users limit tags in their plugins to no more than 12, with some exceptions. Any time your plugin has a high number of tags, you're seen as trying to game the system.
Tags: custom login, login, login page,admin login, author, author profile, Avatar, avatar upload, builder, captcha, custom field registration, custom fields, custom login, custom password reset, custom redirects, custom registration, custom registration form, custom registration page, custom user profile, customize profile, customize registration email, edit profile, email confirmation, extra user fields, Facebook Login, file uploads, form builder, front end, front-end edit profile, front-end login, front-end profile, front-end register, front-end registration, front-end user listing, front-end user registration, frontend, github, github login, google, Google Login, gravatar, hide wp-admin, linkedin, linkedin login, log in, login, login redirect, login widget, member directory, members, minimum password length, minimum password strength, multiple registration forms, password reset, password strength meter, profile, profile builder, recaptcha, register, register form, registration, registration page, shortcode, shortcodes, sidebar, sidebar login, social, social login, tab widget, twitter, twitter login, user, user approval, user custom fields, user email, user listing, user login, user profile, user profile page, User Registration, user registration form, user-fields, users, widget, wordpress login, custom, e-mail, gravatar, log in, login, redirection, register, registration, sidebar, theme, widget, extra css, theme, theme colors, Theme customization, theme styles, theme tweaking, child theme, child theme creator, child theme generator, child-themes, CSS, css editor, customize theme, customizer, responsive, stylesheet,chandrakesh kumar,chand giri,chandrakeshkumar,chandgiri
Remove any 'common misspellings' from your tag list (as they aren't beneficial), as well as any duplicates. Duplicate words do not help your results in our search engine, as it only considers them once. As much as some people like to think, "tags" are not the same as "search terms" in our system, so including lots of them doesn't really benefit you much.
If you're looking to improve your search rankings, we suggest improving the parts of the readme intended for human beings to read. The short and long descriptions should be clear and useful. Addressing common problems in the "FAQ" section helps too. The entire contents of the readme file is considered for the search, and tags are really only a small part of that. Removing irrelevant pieces such as lists of languages (like links) or feature bullet points may help a lot as well, to reduce the overall length and to help eliminate irrelevant information about the plugin.
Make the readme for people, not for machines, and it will help you rank higher in the search results. People actually search for solutions to their problems, not simply for keywords.
## Generic function (and/or define) names
All plugins should have unique function names, defines, and classnames. This will prevent your plugin from conflicting with other plugins or themes.
For example, if your plugin is called "Easy Custom Post Types", then you might prefix your functions with ecpt_{your function name here}. Similarly a define of LICENSE would be better done as ECPT_LICENSE.
Please update your plugin to use more unique names.
define('blog_name',get_bloginfo('name'));
define('site_url',get_site_url());
define('plugin_url',plugins_url( '/', __FILE__ ));
Those are all not very unique.
Also two are totally redundant.
## Please use wp_enqueue commands
Your plugin is using <style> and/or <link> tags to insert CSS/JS
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
## Calling core loading files 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
For other possibilities, or to better understand why we disallow this, read this: http://ottopress.com/2010/dont-include-wp-load-please/
If you're trying to use it because you need to access WordPress functions outside of WordPress, we'd actually much rather you didn't do that at all. Your plugin should be inside WordPress, only accessible to people who are logged in and authorized, if it needs that kind of access. Your plugin's pages should be called via the dashboard like all the other settings panels, and in that way, they'll always have access to WordPress functions.
----
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.