Custom Login Page made easy! Customize the logo, background image, colors, fonts and more on your login page and see your changes in realtime!
Prioritized issue groups from the latest Plugin Check scan
Security
325
8 issue groups
Maintainability
121
11 issue groups
I18n
8
4 issue groups
Repo Compliance
1
1 issue group
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '" /> $v"'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$ajax_url".
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Processing form data without nonce verification.
Sample message
Scripts must be registered/enqueued via wp_enqueue_script()
Sample message
Detected usage of a non-sanitized input variable: $_GET['d']
Sample message
$_GET['d'] not unslashed before sanitization. Use wp_unslash() or similar
Sample message
Stylesheets must be registered/enqueued via wp_enqueue_style()
Sample message
Detected usage of a possibly undefined superglobal array index: $_POST['option_page']. Check that the array index exists before using it.
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"$msg: $loc"'.
Sample message
Mismatched text domain. Expected 'custom-login-page-wp' but got 'coming-soon'.
Sample message
Processing form data without nonce verification.
Sample message
In footer ($in_footer) is not set explicitly wp_enqueue_script; It is recommended to load scripts in the footer. Please set this value to `true` to load it in the footer, or explicitly `false` if it should be loaded in the header.
Sample message
Offloading images, js, css, and other scripts to your servers or any remote service is disallowed.
Sample message
Missing $domain parameter in function call to __().
Sample message
Library files that are already in the WordPress core are not permitted.
Sample message
load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed.
Sample message
Resource version not set in call to wp_enqueue_script(). This means new versions of the script may not always be loaded due to browser caching.
Sample message
Version parameter is not explicitly set or has been set to an equivalent of "false" for wp_enqueue_script; This means that the WordPress core version will be used which is not recommended for plugin or theme development.
Sample message
The $text text string should have translatable content. Found: ""
Sample message
Plugin name header in your readme is missing or invalid. Please update your readme with a valid plugin name header. Eg: "=== Example Name ==="
Sample message
Tested up to: 4.9 < 7.0. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.
Sample message
The plugin slug includes a restricted term. Your plugin slug - "custom-login-page-wp" - contains the restricted term "wp" which cannot be used at all in your plugin slug.
Potential connections found in static code analysis.
Outbound calls
42
External assets
3
Incoming endpoints
1
No public endpoints detected.
wp_ajax
First score snapshot
v1.0.3
34
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 34 | 455 | 330 | 125 | v1.0.3 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.