About this plugin
eu. eu, so standings and schedules do not have to be maintained twice.
0 provides:
- a dynamic Gutenberg block with standings and schedule variations;
- the [turnierplan] shortcode for the Classic Editor and page builders;
- reusable presets managed in WordPress;
- filters for groups, participants, match numbers, and dates;
- light, dark, and automatic themes plus comfortable or compact density;
- responsive iframe sizing and accessible local error messages;
- separate WordPress interface and tournament output languages;
- German and English plugin interface text.
eu. eu, create sample content, or enable public frames.
com/pixel33-eu/turnierplan_eu. Z source tag.
Block and shortcode guide
The block is the recommended editor experience. Its sidebar contains the tournament reference, view, filters, appearance, visible columns, language, and height limits. The editor preview uses the same validated configuration as the published page.
Basic shortcode examples:
[turnierplan tournament="400" view="standings"]
[turnierplan tournament="summer-cup" view="matches" lang="de" theme="auto" density="compact"]
[turnierplan tournament="400" view="matches" match_from="1" match_to="12" date_from="2026-06-01" date_to="2026-06-02"]
[turnierplan preset="87"]
Supported inline attributes are tournament, view, lang, group, participant, match_from, match_to, date_from, date_to, theme, density, accent, branding, links, min_height, max_height, show, and date. A preset shortcode must contain only the preset ID.
view accepts `standings` or `matches`; `theme` accepts `auto`, `light`, or `dark`; and `density` accepts `comfortable` or `compact`. <h3>External services</h3>
eu to resolve a public tournament and display its public tournament view.
After an administrator enables the service and an editor configures an embed, the WordPress server requests small tournament metadata for validation, choices, and editor previews. These requests contain the requested public tournament reference and output language. eu also receives the WordPress server’s IP address, request time, and standard HTTP request data.
The plugin explicitly sends no WordPress cookies or login credentials with these server-side requests.
eu. eu can therefore receive the visitor’s IP address, request time, referrer, browser data, tournament reference, selected view, language, and display filters. eu are governed by the visitor’s browser and privacy settings.
php
php
Privacy
The plugin stores its settings and optional reusable embed presets in the WordPress database. It does not copy tournament results into WordPress.
Successful metadata is cached for five minutes. A validated response may be kept for up to 24 hours as a temporary fallback during a service problem. An authoritative not-found response is cached for one minute.
Revoking service approval clears the plugin’s metadata cache and stops new metadata requests and iframe output.
The plugin adds suggested text to WordPress’s Privacy Policy Guide. Site owners remain responsible for adapting that text to their site, legal requirements, consent setup, and actual use of the service.