This plugin allows you to setup a series of dates to count to or from in terms of years, months, weeks, days, hours, minutes, and/or seconds.
Prioritized issue groups from the latest Plugin Check scan
Security
141
4 issue groups
I18n
137
3 issue groups
Maintainability
46
12 issue groups
Repo Compliance
3
3 issue groups
Sample message
Mismatched text domain. Expected 'countdown-timer' but got "fergcorp_countdownTimer".
Sample message
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"fergcorp_countdownTimer_oneTimeEvent[{$event_count}][date]"'.
Sample message
All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.
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
date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.
Sample message
Sanitization missing for register_setting().
Sample message
Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "GMT_Admin_Fergcorp_Countdown_Timer_Test".
Sample message
Use of a direct database call is discouraged.
Sample message
Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().
Sample message
var_export() found. Debug code should not normally be used in production.
Sample message
PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;
Sample message
The use of function wp_get_sidebars_widgets() is forbidden
Sample message
Offloading images, js, css, and other scripts to your servers or any remote service is disallowed.
Sample message
Using date_default_timezone_set() and similar isn't allowed, instead use WP internal timezone support.
Sample message
Using __FILE__ for menu slugs risks exposing filesystem structure.
Sample message
rand() is discouraged. Use the far less predictable wp_rand() instead.
Sample message
strip_tags() is discouraged. Use the more comprehensive wp_strip_all_tags() instead.
Sample message
In footer ($in_footer) is not set explicitly wp_register_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
Multiple placeholders in translatable strings should be ordered. Expected "%1\$s, %2\$s", but got "%s, %s" in "If you want to insert the Countdown Timer into a page or post, you can use the following <abbr %s %s>shortcodes</abbr> to return all or a limited number of Countdown Timers, respectively:".
Sample message
Hidden files are not permitted.
Sample message
Tested up to: 5.1 < 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
Missing "License" in Plugin Header. Please update your Plugin Header with a valid GPLv2 (or later) compatible license.
Sample message
One or more tags were ignored. Please limit your plugin to 5 tags.
Potential connections found in static code analysis.
Outbound calls
22
External assets
1
Incoming endpoints
0
No public endpoints detected.
First score snapshot
v3.0.7
33
Latest
| Scan | Score | Findings | Errors | Warnings | Plugin | Check |
|---|---|---|---|---|---|---|
| Latest | 33 | 328 | 311 | 17 | v3.0.7 | 2.0.0 |
Author, categories, issues, domains, and nearby plugins.