WordPress.WP.I18n.NonSingularStringLiteralText
Non Singular String Literal Text
A translation or text-domain pattern does not match WordPress internationalization expectations.
Why It Shows Up
Plugin Check found missing text domains, mismatched domains, missing translator comments, variable-only strings, placeholder issues, or deprecated translation loading patterns.
Why It Matters
Translation issues make the plugin harder to localize and can break strings for non-English WordPress users.
How to Fix
- Use the plugin slug as the text domain unless the plugin intentionally declares a different one.
- Keep translatable strings literal and move variables into placeholders.
- Add translator comments before strings with placeholders or ambiguous context.
References
Affected Plugins
| Rank | Plugin | Score | Errors | Warnings | Installs | Added | Updated | Top Issue |
|---|---|---|---|---|---|---|---|---|
| #2001 | Custom Fee Woocommerce | 97 | 24 | 3 | 400 | Text Domain Mismatch | ||
| #2002 | Advanced Posts Listing – Show Post List Easily | 98 | 31 | 5 | 3k+ | Missing Arg Domain | ||
| #2003 | ProvenExpert | 98 | 8 | 10 | 900 | wp function not compatible with requires wp | ||
| #2004 | Tablentor – Smart Table Builder for Elementor | 98 | 6 | 7 | 1k+ | Post Not In exclude | ||
| #2005 | Custom Post Type Widgets | 99 | 7 | 3 | 10k+ | Non Singular String Literal Text | ||
| #2006 | Gravity Forms Block Email Domains | 99 | 5 | 2 | 1k+ | Text Domain Mismatch |
