by apunker
0 (0 reviews)
Jabali Cache
Persistent Redis object cache for WordPress. Zero-config on the Jabali panel, works without the phpredis extension, and always fails safe.
Compatible with WP 7.0.2
v1.1.0
Current Version v1.1.0
Updated 4 days ago
Last Update on 21 Jul, 2026
Refreshed 12 hours ago
Last Refreshed on
Rank
#59,757
—
No change
Active Installs
0+
—
No change
KW Avg Position
143.5
+0.5 better
Downloads
286
+1 today
Support Resolved
0%
—
No change
Rating
0%
Review 0 out of 5
0
(0 reviews)
Next Milestone 10
0+
10+
23,005
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 9 more installs to reach 10+
Rank Changes
Current
#59,757
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
0.0
0 reviews
Overall
0%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 2 of 2| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| redis | 106 | — | Tag | 1 day ago |
| object cache | 181 | — | Tag | 1 day ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.1.0
- Last Updated
- Jul 21, 2026
- Requires WP
- 5.6+
- Tested Up To
- 7.0.2
- PHP Version
- 7.4 or higher
- Author
- apunker
Support & Rating
- Rating
- ☆ ☆ ☆ ☆ ☆ 0
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
7K+ installs
#2,730
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#988
LiteSpeed Cache
7M+ installs
#5
Wordfence Security - Firewall, Malware Scan, and Login Security
5M+ installs
#11
Hostinger Tools
3M+ installs
#20
Frequently Asked Questions
Common questions about Jabali Cache
On the Jabali panel, socket access is set up when you enable caching for the site (Applications → cache toggle). If the status still shows Not reachable, re-run that toggle. On a standalone host, the site's PHP-FPM user needs two things for a unix socket: open_basedir must allow the socket's directory — add /run/redis (or wherever your socket lives) to the pool's open_basedir. Read/write access to the socket for the PHP-FPM user. Until that is in place the plugin runs as a normal per-request cache and the site is completely unaffected — caching just isn't persistent yet.
No. It auto-detects phpredis and uses it when available; otherwise it uses a built-in pure-PHP client. You get persistent caching either way.
Define overrides in wp-config.php. With none of these set, it defaults to the Jabali socket and a per-site prefix. define( 'JABALI_CACHE_SOCKET', '/path/to/redis.sock' ); — unix socket, or: define( 'JABALI_CACHE_HOST', '127.0.0.1' ); define( 'JABALI_CACHE_PORT', 6379 ); Optional: define( 'JABALI_CACHE_DB', 1 ); — logical database number define( 'JABALI_CACHE_PASSWORD', '...' ); — Redis AUTH password define( 'JABALI_CACHE_PREFIX', 'mysite' ); — key prefix (auto-derived per site if unset) define( 'JABALI_CACHE_DISABLED', true ); — force off without deactivating
Yes. Each install uses a unique key prefix, so reads, writes, and flushes are scoped to your site only. One site cannot see or clear another's cache, even though they may share the same Redis database.
Yes. The expected policy is allkeys-lru — Redis evicts least-recently-used keys when full. Every read in this plugin is best-effort, so an evicted key just rebuilds from the database. There is no error path that can break the site under memory pressure.
Yes. Per-site cache data is namespaced per blog, while truly global cache groups are shared across the network as WordPress expects.
Only if your host does not already have one. On Jabali, nginx serves a FastCGI microcache at the edge, which is faster than caching in PHP — so the WordPress page cache stays off by default to avoid double-caching. Off Jabali, you can enable it from the settings screen.
wp jabali-cache status # connection, driver, prefix, key count, page-cache state wp jabali-cache flush # flush this site's object cache wp jabali-cache flush --pages # also purge page-cache entries wp jabali-cache enable # enable caching wp jabali-cache disable # disable caching wp jabali-cache update-dropins # (re)install the wp-content drop-ins wp jabali-cache remove-dropins # remove the drop-ins wp jabali-cache diagnose # full connectivity + environment report
Deactivating removes the object-cache.php drop-in cleanly, so WordPress reverts to its built-in non-persistent cache. Uninstalling removes the plugin's options. Your Redis data is just a cache and is safe to discard.