Àpèjúwe
beeVisible Ìtumọ̀ Yorùbá: – Admin HTTP Cache monitors and caches external HTTP requests made by plugins in the WordPress admin area. Many plugins make repeated HTTP requests on every page load (update checks, license verification, API calls) which significantly slow down the backend.
Key Features:
- Auto-Cache Ìtumọ̀ Yorùbá: – Automatically enables caching for frequently requested domains (3+ requests)
- Auto-Blacklist Ìtumọ̀ Yorùbá: – Temporarily blocks faulty domains (403, 404, timeouts, server errors)
- Request Monitoring Ìtumọ̀ Yorùbá: – Overview of all HTTP requests made by plugins
- Full Control Ìtumọ̀ Yorùbá: – Manually enable/disable caching per domain
- Configurable Cache Times Ìtumọ̀ Yorùbá: – Set cache duration per domain (from 5 minutes to 24 hours)
- Debug Mode Ìtumọ̀ Yorùbá: – Detailed cache performance analysis with hit/miss tracking
- Clean Uninstall Ìtumọ̀ Yorùbá: – Removes all data when deleted
Àwọn àwòrán ìbòjú
Ìgbéwọlẹ̀
- Upload the
beevisible-admin-http-cachefolder to the/wp-content/plugins/directory. - Activate the plugin through the ‘Plugins’ menu in WordPress.
- The plugin starts working immediately with Auto-Cache enabled.
- Optional: Go to Settings > beeVisible Ìtumọ̀ Yorùbá: – Admin HTTP Cache to configure cache times and monitor requests.
FAQ
-
Does this plugin work automatically?
-
Yes. Once activated, beeVisible Ìtumọ̀ Yorùbá: – Admin HTTP Cache automatically monitors HTTP requests and enables caching for domains that are requested 3 or more times. No configuration required.
-
What happens when a domain returns errors?
-
Domains returning 403, 404, 500+ errors or timeouts are automatically blacklisted for 1 hour. After that, they are retested automatically. You can also manually unblock them.
-
Can I disable caching for specific domains?
-
Yes. In the HTTP Requests tab, you can disable caching for any domain. Explicitly disabled domains will not be re-enabled by Auto-Cache.
-
Does this affect the frontend?
-
No. beeVisible Ìtumọ̀ Yorùbá: – Admin HTTP Cache only caches requests made in the WordPress admin area. Frontend requests are not affected.
-
What data is stored?
-
beeVisible Ìtumọ̀ Yorùbá: – Admin HTTP Cache stores request statistics, cache settings, and cached HTTP responses as WordPress transients. All data is removed when the plugin is deleted.
Àwọn àgbéyẹ̀wò
Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.
Àwọn Olùkópa & Olùgbéejáde
“beeVisible Ìtumọ̀ Yorùbá: – Admin HTTP Cache” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.
Àwọn OlùkópaTúmọ̀ “beeVisible Ìtumọ̀ Yorùbá: – Admin HTTP Cache” sí èdè rẹ.
Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?
Ṣàwárí koodu, ṣàyẹ̀wò ibi ìpamọ́ SVN, tàbí ṣe àgbékalẹ̀ sí àkọsílẹ̀ ìdàgbàsókè nípasẹ̀ RSS.
Àkọsílẹ̀ àwọn àyípadà
2.1.0
- Added configurable default cache time for Auto-Cache
- Added plugin reset functionality
- Improved cache key generation
- Added cache debug logging
2.0.0
- Renamed to “beeVisible Ìtumọ̀ Yorùbá: – Admin HTTP Cache”
- Added Auto-Cache feature
- Added Auto-Blacklist for faulty domains
- Optimized cache keys
- Added plugin reset function
- Added log size limitation
1.0.0
- Initial release
- HTTP request monitoring
- Manual caching per domain


