Simply include a favicon.ico and a favicon.gif in your active theme.
Prioritized issue groups from the latest Plugin Check scan
Maintainability
12
4 issue groups
I18n
11
5 issue groups
Security
9
3 issue groups
Repo Compliance
2
2 issue groups
Sample message
The $domain parameter must be a single text string literal. Found: WPF_DOMAIN
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
Global constants defined by a theme/plugin should start with the theme/plugin prefix. Found: "WPF_DOMAIN".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '__'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
Sample message
The plugin name includes a restricted term. Your chosen plugin name - "WP Favicon" - contains the restricted term "wp" which cannot be used at all in your plugin name.
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
Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "set_plugin_meta".
Sample message
Using __FILE__ for menu slugs risks exposing filesystem structure.
Sample message
Missing $domain parameter in function call to __().
Sample message
A function call to __() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.
Sample message
The $text parameter must be a single text string literal. Found: 'Due to the famous web browser from Redmond.' .\r\n ' The best approach is to have 2 separates favicon files located at the site root directory.' . '<br>' .\r\n '1. The first favicon file (favicon.ico) is either a <strong>16x16</strong> or a <strong>32x32</strong> icon. Nowadays, all modern browser supports both size.' . '<br>' .\r\n '2. The second favicon file (favicon.gif) is a (reasonable) free size, and can be an animated GIF too!' . '<br>' .\r\n 'The .gif version have precedence over the .ico. So, if the browser support <strong>animated</strong> favicon,' . '<br>' .\r\n 'the animated will be displayed, else the static .ico will be used instead.' . '<br>' .\r\n '<u>Note</u> that both <strong>favicon.ico</strong> and <strong>favicon.gif</strong> can be <strong>different</strong> pictures.'
Sample message
The plugin readme.txt does not exist.
Sample message
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
Potential connections found in static code analysis.
Outbound calls
2
External assets
0
Incoming endpoints
0
No external asset domains detected.
No public endpoints detected.
First score snapshot
v0.1
68
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 68 | 34 | 25 | 9 | v0.1 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.