Translation ready (Slovak translation included)<\/li>\n<\/ul>\n\nShortcodes<\/h4>\n\n
Replace 123<\/code> with the ID of the event (shown in the \u201cAvailable shortcodes\u201d box when editing the event).<\/p>\n\n\n[blyzer_tournament id=\"123\"]<\/code> \u2013 the whole event with tabs<\/li>\n[blyzer_event id=\"123\"]<\/code> \u2013 event info<\/li>\n[blyzer_groups id=\"123\"]<\/code><\/li>\n[blyzer_playoff_rounds id=\"123\"]<\/code><\/li>\n[blyzer_matches id=\"123\"]<\/code><\/li>\n[blyzer_teams id=\"123\"]<\/code><\/li>\n[blyzer_players id=\"123\"]<\/code><\/li>\n[blyzer_race_stages id=\"123\"]<\/code><\/li>\n[blyzer_race_standings id=\"123\"]<\/code><\/li>\n<\/ul>\n\nOptional attributes:<\/p>\n\n
\ntheme=\"dark\"<\/code>, theme=\"light\"<\/code> or theme=\"auto\"<\/code> \u2013 colour scheme (all shortcodes, default from the settings, dark unless changed)<\/li>\nlimit=\"10\"<\/code> \u2013 show only the first N items; blyzer_players<\/code> shows the top 10 by default, limit=\"0\"<\/code> shows all players<\/li>\nupcoming=\"3\"<\/code> and recent=\"3\"<\/code> \u2013 blyzer_matches<\/code> shows all live matches, the next 3 and the last 3 by default; upcoming=\"all\"<\/code> (or limit<\/code>, or status<\/code>) shows the full schedule as before<\/li>\ngroup=\"A\"<\/code> \u2013 only the given group (blyzer_matches<\/code>, blyzer_groups<\/code>)<\/li>\nstatus=\"played\"<\/code>, status=\"upcoming\"<\/code> or status=\"live\"<\/code> \u2013 filter matches (blyzer_matches<\/code>)<\/li>\nphase=\"groups\"<\/code>, phase=\"playoff\"<\/code> or phase=\"friendly\"<\/code> \u2013 filter matches by phase (blyzer_matches<\/code>)<\/li>\nteam=\"45\"<\/code> \u2013 only matches or players of the team with this Blyzer ID (blyzer_matches<\/code>, blyzer_players<\/code>)<\/li>\ngroup_by=\"round\"<\/code>, \"group\"<\/code>, \"day\"<\/code> or \"none\"<\/code> \u2013 how matches are grouped; by default a league is grouped by round and a tournament by group and playoff round (blyzer_matches<\/code>)<\/li>\norder=\"desc\"<\/code> \u2013 newest matches first (blyzer_matches<\/code>)<\/li>\nform=\"yes|no\"<\/code>, extra=\"yes|no\"<\/code>, diff=\"yes|no\"<\/code> \u2013 show or hide the form, overtime and goal difference columns; by default they are shown when the data has them (blyzer_groups<\/code>)<\/li>\nextend=\"0\"<\/code> or extend=\"1\"<\/code> \u2013 only the main or only the additional groups \/ playoff (blyzer_groups<\/code>, blyzer_playoff_rounds<\/code>)<\/li>\nsort=\"sum\"<\/code>, sort=\"name\"<\/code> or the label of a statistic, e.g. sort=\"g\"<\/code> \u2013 order players (blyzer_players<\/code>)<\/li>\nsections=\"groups,playoff,matches\"<\/code> \u2013 which tabs to show (blyzer_tournament<\/code>; also extra<\/code>, teams<\/code>, players<\/code>, standings<\/code>, stages<\/code>)<\/li>\nheader=\"no\"<\/code> \u2013 hide the event info above the tabs (blyzer_tournament<\/code>)<\/li>\nlive=\"no\"<\/code> \u2013 do not refresh this shortcode automatically while the event is in progress (all shortcodes)<\/li>\napply=\"no\"<\/code> \u2013 hide the \u201cRegister a team\u201d button (blyzer_event<\/code>, blyzer_tournament<\/code>)<\/li>\n<\/ul>\n\nBlock and Elementor widget<\/h4>\n\n
In the block editor add the \u201cBlyzer event\u201d block, in Elementor the \u201cBlyzer event\u201d widget. Choose the event (\u2713 means the connection works, \u26a0 means the API key needs checking), what to show and optional settings. They show exactly the same as the shortcodes.<\/p>\n\n
Live updates<\/h4>\n\n
When an event is in progress (Blyzer.net marks it as live, or a match is live), the results on the page refresh automatically. The page asks your own WordPress site for the new results, never Blyzer.net directly, and only while the browser tab is visible. The interval (60 seconds by default, at least 30) and turning it off for the whole site are in Blyzer Events \u2192 Settings; a single shortcode can turn it off with live=\"no\"<\/code>.<\/p>\n\nExamples \u2013 top 10 scorers: [blyzer_players id=\"123\" sort=\"g\" limit=\"10\"]<\/code>, next five matches: [blyzer_matches id=\"123\" status=\"upcoming\" limit=\"5\" group_by=\"none\"]<\/code><\/p>\n\nTemplates<\/h4>\n\n
Every shortcode (except blyzer_tournament<\/code>) uses a built-in template unless you set your own in Blyzer Events \u2192 Settings \u2192 Templates, or for a single event in the event editor.<\/p>\n\n\n{{title}}<\/code> \u2013 prints a value (HTML is escaped)<\/li>\n{{totalStatistics.g}}<\/code> \u2013 prints a nested value<\/li>\n{{#items}} \u2026 {{\/items}}<\/code> \u2013 repeats the block for every item; for non-list values shows the block when the value is not empty<\/li>\n{{^items}} \u2026 {{\/items}}<\/code> \u2013 shows the block when the value is empty<\/li>\n{{@index}}<\/code> \u2013 order of the item in a list, starting at 1<\/li>\n{{count}}<\/code> \u2013 number of items<\/li>\n<\/ul>\n\nBesides the fields from Blyzer.net the plugin adds ready-made fields, so templates need no logic \u2013 for example statusLabel<\/code>, isLive<\/code>, isWinnerHome<\/code>, home.name<\/code>, initials<\/code>, playedAtDate<\/code>, diffLabel<\/code> or formItems<\/code>. The full list for each shortcode is shown next to the template editor.<\/p>\n\nStyling<\/h4>\n\n
The widgets always use the Blyzer.net look (colours, hexagons, the Rajdhani font). Developers can still adjust details with CSS custom properties on .blyzer-events<\/code>, for example --blyzer-surface<\/code>, --blyzer-text<\/code>, --blyzer-border<\/code>, --blyzer-radius<\/code> or --blyzer-font<\/code>. All built-in elements use classes starting with bze-<\/code>.<\/p>\n\nExternal services<\/h3>\n\n
This plugin connects to the Blyzer.net API to load the data of your events. Without it the plugin cannot display anything.<\/p>\n\n
\n- Service: Blyzer.net API, operated by the Blyzer.net platform. Endpoints:
https:\/\/www.blyzer.net\/api\/event\/all<\/code> (all data of the event in one request, used first). When it is not available (HTTP 404), the plugin remembers that for a day and uses up to eight requests instead: https:\/\/www.blyzer.net\/api\/event<\/code>, \/api\/event\/teams<\/code>, \/api\/event\/groups<\/code>, \/api\/event\/playoff-rounds<\/code>, \/api\/event\/matches<\/code>, \/api\/event\/players<\/code>, \/api\/event\/race-stages<\/code> and \/api\/event\/race-standings<\/code>.<\/li>\n- What is sent: the API key of the event you entered in the event editor, in the
X-Auth-Token<\/code> HTTP header, and the standard technical headers of an HTTP request. The User-Agent is BlyzerEvents\/<version>; WordPress<\/code> \u2013 it does not contain the address of your site. As with any internet request, Blyzer.net sees the IP address of your web server. No data about your site visitors is sent. The key is never shown on your site, in the block or in any response of your site.<\/li>\n- When: from your server, when a page with a Blyzer block, widget or shortcode is displayed (or refreshed during a live event) and the cached data has expired \u2013 at most one request per event per cache period, no matter how many visitors there are. With the cache duration set to 0 a request is made on every page view (live updates still use at least a 10-second cache). Also when an event is saved or opened in the editor (connection check) and when you click \u201cVerify API\u201d in the list of events. When Blyzer.net asks the plugin to slow down (HTTP 429 with Retry-After) no requests are sent for that time.<\/li>\n
- Terms of service: https:\/\/www.blyzer.net\/sk\/obchodne-podmienky<\/li>\n
- Privacy policy: https:\/\/www.blyzer.net\/sk\/ochrana-osobnych-udajov<\/li>\n<\/ul>\n\n
Stream links from the API are shown only when they point to YouTube, Twitch or Facebook (https). All other links point only to www.blyzer.net, blyzer.net or cdn.www.blyzer.net.<\/p>\n\n
The Rajdhani font and the Blyzer.net logo are bundled with the plugin and loaded from your own site \u2013 no request goes to Google Fonts or to Blyzer.net for them.<\/p>\n\n
Images (event and team logos, player photos, flags, sport icons) returned by the API are loaded by the visitor\u2019s browser directly from Blyzer.net servers (https:\/\/cdn.www.blyzer.net<\/code> and other blyzer.net subdomains), so the visitor\u2019s IP address and browser information reach those servers. Only HTTPS addresses on blyzer.net and its subdomains are used. Live updates are loaded by the visitor\u2019s browser from your own site (\/wp-json\/blyzer-events\/v1\/render<\/code>), not from Blyzer.net.<\/p>\n\nCredits<\/h3>\n\n\n- Rajdhani font by Indian Type Foundry, licensed under the SIL Open Font License 1.1 (
assets\/fonts\/OFL.txt<\/code>). Bundled as a Latin subset in WOFF2.<\/li>\n- Blyzer.net logo and name are trademarks of Blyzer.net, the author of this plugin.<\/li>\n<\/ul>\n\n\n
\n- Install and activate the plugin from Plugins \u2192 Add New, or upload the
blyzer-events<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n- On Blyzer.net open your event \u2192 Detailed settings \u2192 API keys \u2192 \u201c+\u201d and copy the key.<\/li>\n
- In WordPress go to Blyzer Events \u2192 Add New, paste the key and publish (the name is filled in from Blyzer.net when you leave it empty). The editor shows whether the connection works and offers a preview.<\/li>\n
- Add the \u201cBlyzer event\u201d block (or the Elementor widget) to any page and choose the event \u2013 or copy a shortcode from the \u201cAvailable shortcodes\u201d box.<\/li>\n<\/ol>\n\n\n
\nWhere do I find the API key?<\/h3><\/dt>\nOn Blyzer.net open your event \u2192 Detailed settings \u2192 API keys \u2192 \u201c+\u201d. You need to be the organiser of the event.<\/p><\/dd>\n
The shortcode shows nothing \/ \u201cNo data yet.\u201d<\/h3><\/dt>\nCheck the \u201cAPI status\u201d column in Blyzer Events. 200 means the key works, any other code means Blyzer.net did not accept the request. The column shows the last known result; click \u201cVerify API\u201d to check it again. Make sure the event in WordPress is published \u2013 unpublished events show the message from the settings instead.<\/p><\/dd>\n
How often is the data refreshed?<\/h3><\/dt>\nBy default every 300 seconds. You can change it in Blyzer Events \u2192 Settings. 0 disables caching (not recommended on busy sites). Saving an event clears its cache immediately.<\/p><\/dd>\n
Can I change how it looks?<\/h3><\/dt>\nThe widgets are meant to look like Blyzer.net, so the colours and the font are fixed. You can choose the dark (default), light or automatic colour scheme in Blyzer Events \u2192 Settings or per shortcode, developers can override the CSS custom properties (see Styling), and you can write your own HTML templates. Custom templates made for version 1.4 keep working and keep their look; the accent colour setting was removed in 1.6.0.<\/p><\/dd>\n
Why do the widgets link to Blyzer.net?<\/h3><\/dt>\nThe plugin is a window to your event, Blyzer.net is the place with everything else. Matches show the nearest and latest ones and players the top 10, with buttons to the full schedule and statistics on Blyzer.net. Every link is part of the content (the event, a match, a team or a player) and opens in a new tab. The \u201cResults from Blyzer.net\u201d logo is optional and off by default \u2013 you can turn it on in Blyzer Events \u2192 Settings.<\/p><\/dd>\n
What happens when Blyzer.net is down?<\/h3><\/dt>\nThe plugin waits at most 8 seconds once, then shows the last successfully loaded data and does not try again for a minute, so your pages stay fast. When Blyzer.net answers \u201ctoo many requests\u201d, the plugin waits as long as Blyzer.net asks (at most 10 minutes) and shows the last loaded data meanwhile. Live updates on open pages simply wait longer and try again.<\/p><\/dd>\n
How do live updates work and do they slow down my site?<\/h3><\/dt>\nOnly widgets of an event that is in progress refresh, every 60 seconds by default plus a small random delay, and only while the browser tab is visible. The browser asks your site, which answers from a short cache, so even many visitors cause at most one request to Blyzer.net per event per cache period. Refresh requests that would need new data from Blyzer.net are limited to 60 per minute per IP address (IPv6 per \/64 network); answers from the cache are not limited (with a persistent object cache, up to 600 per minute). You can change the interval or turn live updates off in Blyzer Events \u2192 Settings, or for one shortcode with live=\"no\"<\/code>.<\/p><\/dd>\nMy site is behind Cloudflare or another proxy \/ CDN<\/h3><\/dt>\nThe plugin takes the visitor\u2019s IP address only from REMOTE_ADDR<\/code>, because other headers can be faked. Behind a CDN or reverse proxy all visitors may share the proxy\u2019s address and share the limit. If your server knows the real address, return it with the blyzer_events_client_ip<\/code> filter, for example:<\/p>\n\nadd_filter( 'blyzer_events_client_ip', function ( $ip ) { return $_SERVER['HTTP_CF_CONNECTING_IP'] ?? $ip; } );\n<\/code><\/pre>\n\nOnly do this when the proxy always sets the header, otherwise visitors could fake it. The limits can be changed with the blyzer_events_rest_rate_limit<\/code> and blyzer_events_rest_rate_limit_cached<\/code> filters.<\/p><\/dd>\nDoes it work with caching plugins?<\/h3><\/dt>\nYes. Pages can be cached as usual; live updates are loaded through the WordPress REST API, which page caches do not store. If a security plugin blocks the REST API for visitors, live updates are silently skipped and the page still shows the results from the time it was loaded.<\/p><\/dd>\n
What happens to my data when I delete the plugin?<\/h3><\/dt>\nEvents and settings are deleted, unless you tick \u201cKeep data on uninstall\u201d in the settings. Deactivating the plugin never deletes anything.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.6.0<\/h4>\n\n\n- New: always looks like Blyzer.net \u2013 Blyzer colours, hexagon crests and the bundled Rajdhani font; dark colour scheme by default. The accent colour setting was removed.<\/li>\n
- New: matches show live matches, the next 3 and the last 3 with a \u201cFull schedule on Blyzer.net\u201d button (
upcoming<\/code>, recent<\/code>; upcoming=\"all\"<\/code> for everything); players show the top 10 with \u201cAll statistics on Blyzer.net\u201d; every match row, team and player links to Blyzer.net in a new tab; \u201cWatch live\u201d label on live matches; \u201cFollow on Blyzer.net\u201d button in the event header.<\/li>\n- New: optional \u201cResults from Blyzer.net\u201d logo under each widget (off by default, Settings or the setup guide).<\/li>\n
- New: stream links to YouTube, Twitch and Facebook are allowed.<\/li>\n
- New: \u201cBlyzer event\u201d block for the block editor with a live preview, and a \u201cBlyzer event\u201d widget for Elementor (only loaded when Elementor is active).<\/li>\n
- New: live updates \u2013 while an event is in progress the results refresh without reloading the page, only when the tab is visible, with a random delay and a longer pause after errors; the active tab and scroll position are kept. Setting for the interval (default 60 s, minimum 30 s) and to turn it off, shortcode attribute
live=\"no\"<\/code>.<\/li>\n- New: countdown to the start of the event and a \u201cRegister a team\u201d button while registration is open (
apply=\"no\"<\/code> hides it).<\/li>\n- New: a 3-step guide for new users, a connection check with a clear message right after the key is saved, a preview of the whole event, and the event name is filled in from Blyzer.net.<\/li>\n
- Improved: all data of an event is loaded with one request (
\/api\/event\/all<\/code>) and shared by all widgets on the page; falls back to the separate endpoints when it is not available.<\/li>\n- Improved: when Blyzer.net answers HTTP 429 the plugin respects Retry-After (at most 10 minutes) and shows the last loaded data; only one request per event is made at a time.<\/li>\n
- Security: the live update endpoint is read-only, validates every parameter against an allow-list, returns only what the public shortcode shows, caches the result in memory (not in the database) and limits requests that need new data per IP address.<\/li>\n
- Security: events use their own capabilities (
edit_blyzer_events<\/code> \u2026), given to administrators on activation and update; filter blyzer_events_capability_roles<\/code>.<\/li>\n- Security: links from Blyzer.net data may point only to www.blyzer.net, blyzer.net and cdn.www.blyzer.net; requests do not send the site address in the User-Agent and refuse compressed responses.<\/li>\n
- Improved: uninstalling removes events in every status, all cached data and the capabilities.<\/li>\n
- Requires WordPress 6.3 or newer.<\/li>\n<\/ul>\n\n
1.5.0<\/h4>\n\n\n- New: completely redesigned built-in templates in the Blyzer.net style \u2013 light, dark and automatic colour scheme (
theme<\/code> attribute and setting), accent colour setting.<\/li>\n- New:
[blyzer_tournament]<\/code> \u2013 the whole event with tabs, shows only sections with data; works without JavaScript.<\/li>\n- New:
[blyzer_event]<\/code> \u2013 event info with logo, sport, status, LIVE indicator, dates, venue and counts.<\/li>\n- New:
[blyzer_race_stages]<\/code> and [blyzer_race_standings]<\/code> for races, including DNS \/ DNF \/ DSQ.<\/li>\n- New: playoff bracket with connecting lines, winners, byes, double elimination and additional playoff; swipeable rounds on phones.<\/li>\n
- New: matches grouped by round, group or day (
group_by<\/code>), live \/ final \/ upcoming state, new filters phase<\/code>, team<\/code>, order<\/code>, status=\"live\"<\/code>.<\/li>\n- New: standings with played, overtime, goal difference and form columns (
form<\/code>, extra<\/code>, diff<\/code>), sticky team column on phones.<\/li>\n- New: player statistics columns follow the statistics of the event.<\/li>\n
- New: many ready-made template fields (
statusLabel<\/code>, isWinnerHome<\/code>, home.name<\/code>, initials<\/code> \u2026); dates use the site time zone and formats.<\/li>\n- Improved: when Blyzer.net is not reachable the last loaded data is shown, errors are remembered for 60 seconds and requests time out after 8 seconds.<\/li>\n
- Improved: the list of events no longer contacts Blyzer.net; API status is updated when data is loaded or when you click \u201cVerify API\u201d.<\/li>\n
- Security: only HTTPS images and links from blyzer.net are used, built-in templates use a strict HTML allow-list, the API key field is hidden and validated, shortcode attributes are validated, responses are limited to 5 MB.<\/li>\n
- Styles are isolated from the theme; styles and scripts load only on pages with a shortcode.<\/li>\n<\/ul>\n\n
1.4.0<\/h4>\n\n\n- New: built-in templates for all shortcodes, so they work without writing any HTML.<\/li>\n
- New: shortcode attributes
limit<\/code>, group<\/code>, status<\/code> and sort<\/code>.<\/li>\n- New: templates support nested values (
{{totalStatistics.g}}<\/code>), empty blocks (