| 开发者 | pixel33 |
|---|---|
| 更新时间 | 2026年10月21日 11:14 |
| PHP版本: | 8.3 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[turnierplan] shortcode for the Classic Editor and page builders;vX.Y.Z source tag.
turnierplan-eu-X.Y.Z.zip release file, install it, and activate the plugin.[turnierplan tournament="400" view="standings"].Visitors do not need an account. The tournament must already exist on Turnierplan.eu and be published for public embedding. Managing a tournament remains a Turnierplan.eu task.
The block and shortcode accept a public numeric ID, slug, canonical public reference, or a supported Turnierplan.eu tournament URL. Arbitrary remote URLs are rejected.
Yes. Depending on the view, you can filter by group, participant, match-number range, or date range and choose which supported columns are visible.
The public frame shows live service data. Small metadata used in the WordPress editor is normally refreshed after five minutes. During a temporary service problem, the editor may use the last validated metadata for up to 24 hours.
The plugin shows a local, translated error state instead of exposing raw service errors. Existing page content remains intact. Editor metadata may temporarily use a validated cached response.
The plugin contains no analytics or advertising tracker. Its server-side metadata requests explicitly omit WordPress cookies and credentials. A published iframe is a direct browser request to Turnierplan.eu, so browser cookie and consent behavior depends on the visitor's settings and the site owner's consent configuration. Review the service privacy policy before enabling embeds.
Yes. Each block, shortcode, and preset gets its own isolated frame and resize channel.
Deactivation stops plugin behavior but keeps settings and presets. By default, uninstall also keeps them. To remove all plugin-owned settings, caches, capabilities, and presets during uninstall, enable the deletion option under Settings > Turnierplan.eu before deleting the plugin.
For reproducible bugs and feature requests, use the GitHub issue tracker. Do not publish passwords, private tournament information, or exploitable security details in an issue. Security reports can be sent privately to info@pixel33.eu.