HiveKit External API Page Content
| 开发者 | corradofiore |
|---|---|
| 更新时间 | 2026年10月14日 01:06 |
| PHP版本: | 8.3 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- an optional administrative label
- a WordPress page
- an external API URL
- payload format: auto-detect, HTML, or Markdown
- its own cache TTL
- optional HTTP request headers, entered one per line
- enabled/disabled status
- Repeatable mappings: add or remove as many mappings as needed.
- Uses the WordPress HTTP API (
wp_safe_remote_get). - Auto-detects HTML vs Markdown, or lets you force the format per mapping.
- Sanitizes output before rendering.
- Caches successful responses with a configurable TTL per mapping.
- Keeps the last successful API response per mapping as an outage fallback.
- Falls back to the original WordPress editor content if the API has never succeeded.
- Does not read PHP constants and does not store secrets, so it cannot be used to send
wp-config.phpvalues such as database credentials to a remote server. - Includes a per-mapping Test API button that shows the raw response payload, HTTP status, content type, size, and detected format without changing the cache.
- Supports per-mapping request headers using a simple
Header-Name: valuetextarea. - Offers filters for advanced request/header customization.
安装:
- Upload and activate the plugin.
- Go to External API Content in the admin menu.
- Click Add mapping.
- Select a WordPress page and enter its API URL.
- Choose Auto-detect, HTML, or Markdown.
- Optionally add request headers, one per line in
Header-Name: valueformat. - Set the mapping's cache TTL.
- Optionally click Test API to inspect the endpoint response before saving.
- Save settings.
常见问题:
What happens when the external API is unavailable?
The last successful response for that mapping is served instead. If the API has never returned a usable response, the normal WordPress page content is shown unchanged.
How do I authenticate to the API?
Add an Authorization header with the hivekit_eapc_request_args filter, so the token stays in your own code and never reaches the database. If you instead type a header into a mapping's Request headers field, its value is stored in the site options table. The plugin never reads PHP constants, so it cannot expose wp-config.php secrets.
Does this plugin send data to the plugin author?
No. Requests go only to the API URLs you configure yourself.
Can several pages use the same API?
Yes. Every mapping is independent and keeps its own cache TTL, request headers and payload format.
Which Markdown features are supported?
Headings, paragraphs, blockquotes, horizontal rules, fenced code blocks, ordered and unordered lists, links, inline code, bold, emphasis and strikethrough. Tables and nested lists are not supported; see the Markdown support section above.
Does it work on multisite?
Settings are stored per site. After a network activation, configure each site through the External API Content screen.
更新日志:
- Renamed the plugin to HiveKit External API Page Content. Every option, hook, filter and constant now uses the
hivekit_eapc_prefix, and settings saved by earlier versions are migrated automatically. - Removed the per-mapping Bearer token constant setting. The plugin no longer reads any PHP constant, so an administrator cannot use it to send
wp-config.phpvalues such as database credentials to a remote URL. Add an Authorization header with thehivekit_eapc_request_argsfilter instead. - Added per-mapping HTTP request headers textarea.
- Headers use one
Header-Name: valueentry per line and apply to both live fetches and Test API requests. - Explicit mapping headers override the plugin's default headers when names conflict.
- Header changes are included in cache/fallback identity to avoid reusing content from a different request context.
- Added a per-mapping Test API button to inspect the raw API payload.
- Test results include HTTP status, Content-Type, response size, and resolved HTML/Markdown format.
- Tests use the current unsaved mapping values and do not populate or alter the normal content cache.
- Non-2xx responses still display their returned payload for diagnostics.
- Replaced the fixed page slots with an arbitrary repeatable mapping list.
- Added per-mapping labels, cache TTL, enabled status, and configurable Bearer-token constant names.
- Generalized cache/fallback storage and filter context around stable mapping IDs.
- Added automatic migration from version 1.0 settings.
- Initial release.