New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Load JSON data via API, display it on your WordPress site, and auto-refresh it at custom intervals — without reloading the page. | You have to log in to add a translation. | Details |
Original untranslated
Load JSON data via API, display it on your WordPress site, and auto-refresh it at custom intervals — without reloading the page.
You have to log in to edit this translation. |
|||
| ↑ | Live Data Display | You have to log in to add a translation. | Details |
Original untranslated |
|||
| No. Settings are stored in the WordPress database and survive updates. A migration routine automatically converts the old single-slot format from versions before 1.3.0. | You have to log in to add a translation. | Details | |
Original untranslated
No. Settings are stored in the WordPress database and survive updates. A migration routine automatically converts the old single-slot format from versions before 1.3.0.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If an <em>Error text</em> is configured for the slot, it is displayed in place of the value. Otherwise the last successfully loaded value remains visible. | You have to log in to add a translation. | Details | |
Original untranslated
If an <em>Error text</em> is configured for the slot, it is displayed in place of the value. Otherwise the last successfully loaded value remains visible.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| <strong>In practice:</strong> for most live production sites the <strong>admin-ajax</strong> method is the safer and more compatible choice. The REST API proxy is the right pick for local development setups or when an admin-ajax conflict forces you to look for an alternative. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>In practice:</strong> for most live production sites the <strong>admin-ajax</strong> method is the safer and more compatible choice. The REST API proxy is the right pick for local development setups or when an admin-ajax conflict forces you to look for an alternative.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| <strong>REST API proxy</strong> (<code>/wp-json/araa/v1/geturl</code>)↵ - The browser sends a GET request to a WordPress REST endpoint. The external URL is included in the request as a query parameter, signed with an HMAC-SHA256 key to prevent tampering. The WordPress server then fetches the external URL and returns the result.↵ - Access to the endpoint is restricted to requests originating from the same server (localhost / server IP), so it is suited to local development environments or setups where WordPress makes internal loopback requests.↵ - Requires the WordPress REST API to be accessible.↵ - <strong>Choose this when</strong> you are running WordPress locally or in a controlled environment where loopback requests are used, and you prefer the modern REST API transport. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>REST API proxy</strong> (<code>/wp-json/araa/v1/geturl</code>)↵
- The browser sends a GET request to a WordPress REST endpoint. The external URL is included in the request as a query parameter, signed with an HMAC-SHA256 key to prevent tampering. The WordPress server then fetches the external URL and returns the result.↵
- Access to the endpoint is restricted to requests originating from the same server (localhost / server IP), so it is suited to local development environments or setups where WordPress makes internal loopback requests.↵
- Requires the WordPress REST API to be accessible.↵
- <strong>Choose this when</strong> you are running WordPress locally or in a controlled environment where loopback requests are used, and you prefer the modern REST API transport.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| <strong>admin-ajax</strong> (<code>/wp-admin/admin-ajax.php</code>)↵ - The browser sends a POST request containing only the slot ID and a WordPress nonce. The external URL is never transmitted to the browser — it stays entirely on the server.↵ - Secured with a WordPress nonce (CSRF protection) and server-side URL validation.↵ - Works on every WordPress installation, including environments where the REST API is disabled by a security plugin or by the hosting provider.↵ - <strong>Choose this when</strong> you want to keep the external URL (and any parameters or tokens embedded in it) hidden from the browser, or when the REST API is unavailable. | You have to log in to add a translation. | Details | |
Original untranslated
<strong>admin-ajax</strong> (<code>/wp-admin/admin-ajax.php</code>)↵
- The browser sends a POST request containing only the slot ID and a WordPress nonce. The external URL is never transmitted to the browser — it stays entirely on the server.↵
- Secured with a WordPress nonce (CSRF protection) and server-side URL validation.↵
- Works on every WordPress installation, including environments where the REST API is disabled by a security plugin or by the hosting provider.↵
- <strong>Choose this when</strong> you want to keep the external URL (and any parameters or tokens embedded in it) hidden from the browser, or when the REST API is unavailable.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Both methods let the WordPress server fetch an external JSON URL on behalf of the browser, bypassing CORS restrictions. They differ in how the browser communicates with WordPress: | You have to log in to add a translation. | Details | |
Original untranslated
Both methods let the WordPress server fetch an external JSON URL on behalf of the browser, bypassing CORS restrictions. They differ in how the browser communicates with WordPress:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| All endpoints are publicly accessible (no authentication required) and return JSON. | You have to log in to add a translation. | Details | |
Original untranslated
All endpoints are publicly accessible (no authentication required) and return JSON.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The plugin ships with six optional REST API endpoints under the namespace <code>araa/v1/api/</code>. All are <strong>disabled by default</strong> and must be activated individually under <em>Settings → Live Data Display → API</em>. | You have to log in to add a translation. | Details | |
Original untranslated
The plugin ships with six optional REST API endpoints under the namespace <code>araa/v1/api/</code>. All are <strong>disabled by default</strong> and must be activated individually under <em>Settings → Live Data Display → API</em>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| No. The frontend script depends on jQuery, which is bundled with WordPress. | You have to log in to add a translation. | Details | |
Original untranslated
No. The frontend script depends on jQuery, which is bundled with WordPress.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| 500 ms. Values below 500 ms are clamped to 500 ms automatically. | You have to log in to add a translation. | Details | |
Original untranslated
500 ms. Values below 500 ms are clamped to 500 ms automatically.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If the API requires authorisation headers, use the companion plugin <a href="https://json-content-importer.com" title="JSON Content Importer">JSON Content Importer</a> to create an authenticated feed and point this plugin at the result. | You have to log in to add a translation. | Details | |
Original untranslated
If the API requires authorisation headers, use the companion plugin <a href="https://json-content-importer.com" title="JSON Content Importer">JSON Content Importer</a> to create an authenticated feed and point this plugin at the result.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| <a href="https://kux.de" title="Example: See the date and time in the right column">Example on kux.de</a>. | You have to log in to add a translation. | Details | |
Original untranslated
<a href="https://kux.de" title="Example: See the date and time in the right column">Example on kux.de</a>.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Will my settings be lost when I update the plugin? | You have to log in to add a translation. | Details | |
Original untranslated
Will my settings be lost when I update the plugin?
CommentFound in faq header. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.