Àpèjúwe

RTEO Connect pulls live, never-stale schema.org Course structured data from your RTEO workspace and injects it server-side into your course page . It also provides the [rteo_connect embed=table object=…] shortcode to drop the live course instance table (dates, locations, prices, availability, enrol buttons) anywhere on your site. It never authors or stores content in WordPress — it only renders content served by RTEO.

The Course JSON-LD is injected server-side (in wp_head), not via client-side JavaScript, so search engines and AI consumers index it reliably. The plugin transient-caches the fetched JSON-LD so it adds no per-render network cost, and it fetches from RTEOÌtumọ̀ Yorùbá: ’s public, anonymous schema endpoint, storing no secrets.

External services

This plugin relies on the RTEO application — a third-party SaaS platform operated by RTEO — to generate and serve the schema.org Course structured data and the live course instance table for your courses. The plugin only reads and renders content that RTEO produces; it never authors or stores content in WordPress.

By default it connects to the live RTEO service at https://staging.rteo.com.au. This is configurable via the rteo_endpoint_base option, which RTEO sets for you during a remote install (for example, to point at a self-hosted RTEO instance).

What data is sent, and when:

Schema fetch (server-side, on page render). When a page has an RTEO schema token configured, the plugin makes a server-to-server request to the RTEO schema endpoint (https://staging.rteo.com.au/api/schema/) to fetch that pageÌtumọ̀ Yorùbá: ’s Course JSON-LD. The only data sent is the pageÌtumọ̀ Yorùbá: ’s opaque schema token (e.g. sch_xxxx) — no personal data, post content, or site credentials. Responses are cached locally so the request is not repeated on every render.
Embed widget (in the visitorÌtumọ̀ Yorùbá: ’s browser, only when used). When you add the [rteo_connect embed=table] shortcode to a page, the visitorÌtumọ̀ Yorùbá: ’s browser loads the RTEO embed widget script from https://staging.rteo.com.au/dist/rteo-instances.js, which then requests the public, anonymous instance-table data for the pageÌtumọ̀ Yorùbá: ’s token from https://staging.rteo.com.au/api/embed/page/. As with any externally hosted script, the visitorÌtumọ̀ Yorùbá: ’s browser contacts staging.rteo.com.au (sending its IP address and standard request headers) when the table is displayed.

This service is provided by RTEO. Its terms and privacy policy:

Terms & Conditions: https://rteo.com.au/terms-conditions
Privacy Policy: https://rteo.com.au/privacy-policy

Ìgbéwọlẹ̀

Install and activate the plugin (via the WordPress plugin directory, or upload the ZIP via Plugins Add New Upload).
RTEO sets the endpoint base and your page token automatically when you install via RTEO. To configure manually, set the pageÌtumọ̀ Yorùbá: ’s rteo_schema_token meta (or the rteo_default_schema_token option) to the token shown in your RTEO course page editor.

FAQ

Does this send any personal data to RTEO?: No personal data. To fetch a pageÌtumọ̀ Yorùbá: ’s public Course schema the plugin sends only that pageÌtumọ̀ Yorùbá: ’s opaque schema token to RTEOÌtumọ̀ Yorùbá: ’s endpoint. When you use the embed shortcode, visitors’ browsers load the table widget from RTEO. See the “External services” section above for the full disclosure.
Where do I get my page token?: Your RTEO course page editor shows the opaque schema token for each course page. RTEO sets it for you automatically on a remote install; for a manual install, copy it into the pageÌtumọ̀ Yorùbá: ’s rteo_schema_token meta or the site-wide rteo_default_schema_token option.

À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

“RTEO Connect” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí.

rteo

Túmọ̀ “RTEO Connect” 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à

0.5.4

create-and-link-faq: when the FAQ CPT has no ACF answer field, the answer is written to post_content as a paragraph block (rteocm convention).

0.5.3

create-and-link-faq: per-site tag taxonomy (tag_taxonomy param). The publish phase now accepts an optional tag_taxonomy so FAQ post types that register their own tag taxonomy (e.g. rteocm_faq_tag) tag the course into the right taxonomy; absent it defaults to the WordPress core post_tag (backward compatible). An explicitly supplied but unregistered taxonomy returns rteo_taxonomy_not_found rather than mis-tagging.

0.5.2

FAQ route fixes: acf-prefix strip on draft writes, post:title in field-values.

0.5.1

Version bump to supersede pre-release 0.5.0 dev builds installed manually on early sites (identical routes to 0.5.0). Ensures wp.org auto-update delivers the push routes everywhere.
This plugin is in public beta (0.x). 1.0.0 will mark the first stable release.

0.5.0

Added RTEO control-plane content routes (admin-authenticated): GET /wp-json/rteo/v1/field-manifest (enumerate a post typeÌtumọ̀ Yorùbá: ’s ACF field definitions), GET /wp-json/rteo/v1/field-values (read raw unformatted ACF values + Yoast title/metadesc), GET /wp-json/rteo/v1/taxonomy-terms (enumerate a taxonomyÌtumọ̀ Yorùbá: ’s live terms), POST /wp-json/rteo/v1/write-field (write a single ACF field by key or a Yoast slot), and POST /wp-json/rteo/v1/create-and-link-faq (draft/publish/delete FAQ posts and link them to a course relationship field). These power RTEOÌtumọ̀ Yorùbá: ’s gated content push. Read-only for reads; writes are admin-only and never touch credential-looking meta.

0.4.1

Marked tested up to WordPress 7.0. Added listing icon and banner assets. No functional changes.

0.4.0

Public beta. The embed shortcode is [rteo_connect embed=table object=…] (the tag matches the plugin name).
The embed widget is now loaded via wp_enqueue_script() and mounts into a placeholder element, instead of an inline script tag.
Hardened the JSON-LD output escaping; updated the Plugin URI and documented the external services this plugin uses.

0.3.0

RTEO control-plane integration routes (admin-authenticated): POST /wp-json/rteo/v1/page-token wires a course pageÌtumọ̀ Yorùbá: ’s schema token onto the matching post, and GET /wp-json/rteo/v1/instance-tables lets RTEO discover per-location/domain instance-table tabs from your page content.

0.2.0

New [rteo_connect embed=table object=…] shortcode — embed the live course instance table (Shadow-DOM, brand-themed) anywhere on your site, with optional display / rows / sort / dir / theme attributes.

0.1.0

Initial: server-side Course JSON-LD injection + [rteo_content] seam.