Live Data Display

FAQ

Where can I see a live example?

Example on kux.de.

Can I display data from a protected API (with authentication)?

If the API requires authorisation headers, use the companion plugin JSON Content Importer to create an authenticated feed and point this plugin at the result.

What is the minimum refresh interval?

500 ms. Values below 500 ms are clamped to 500 ms automatically.

Does the plugin work without jQuery?

No. The frontend script depends on jQuery, which is bundled with WordPress.

What built-in API endpoints does the plugin provide?

The plugin ships with six optional REST API endpoints under the namespace araa/v1/api/. All are disabled by default and must be activated individually under Settings → Live Data Display → API.

Endpoint
Description
Optional parameters

/wp-json/araa/v1/api/time
Current server time, date, weekday, and timezone
—

/wp-json/araa/v1/api/countdown
Countdown to a target date (days, hours, minutes, seconds)
to=YYYY-MM-DD (default: next New Year)

/wp-json/araa/v1/api/random
Random integer in a configurable range
min=1&max=100

All endpoints are publicly accessible (no authentication required) and return JSON.

When should I use “admin-ajax” and when “REST API” as the proxy method?

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:

admin-ajax (/wp-admin/admin-ajax.php)
– 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.
– Choose this when 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.

REST API proxy (/wp-json/araa/v1/geturl)
– 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.
– Choose this when you are running WordPress locally or in a controlled environment where loopback requests are used, and you prefer the modern REST API transport.

In practice: for most live production sites the admin-ajax 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.

What happens when a slot’s API request fails?

If an Error text is configured for the slot, it is displayed in place of the value. Otherwise the last successfully loaded value remains visible.

Will my settings be lost when I update the plugin?

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.