WordPress.DB.DirectDatabaseQuery.NoCaching
No Caching
The plugin runs a direct database query instead of using a higher-level WordPress API or cache-aware pattern.
Why It Shows Up
Plugin Check found `$wpdb` access that queries the database directly, changes schema, or bypasses normal caching expectations.
Why It Matters
Direct queries can be correct, but they are easier to make unsafe, slower at scale, and harder for WordPress to cache or filter.
How to Fix
- Use WordPress APIs such as post, term, metadata, option, or user functions when they fit the task.
- If direct SQL is necessary, prepare dynamic values and add a clear caching strategy for repeated reads.
- Keep schema changes in activation or upgrade routines and make them idempotent.
References
Affected Plugins
| Rank | Plugin | Score | Errors | Warnings | Installs | Added | Updated | Top Issue |
|---|---|---|---|---|---|---|---|---|
| #3451 | Machete | 99 | 7 | 7k+ | Direct Query | |||
| #3452 | Ogp Plus | 99 | 1 | 6 | 500 | Non-prefixed global variable | ||
| #3453 | Simple Ticker | 99 | 1 | 7 | 500 | Non-prefixed global variable | ||
| #3454 | Statify Filter | 99 | 6 | 2k+ | Direct Query | |||
| #3455 | Unique Submissions for Elementor Forms | 99 | 1 | 2 | 500 | No Caching | ||
| #3456 | VS Meta Description | 99 | 1 | 3 | 3k+ | Direct Query |
