Ingram Braun

WP Tournament Registration is a plugin that provides shortcodes intended for registering players with hobby sport events. As a matter of fact, it was made for the championship of my <a href="https://schach-goettingen.de/" rel="nofollow ugc">local chess club</a>. There are four shortcodes for different views:
<ul>
<li><code>[wptournregedit tournament_id="myID" /]</code> is an editor for the players’ data.</li>
<li><code>[wptournregexport tournament_id="myID"]...[/wptournregexport]</code> is a plain text export filter</li>
<li><code>[wptournregform tournament_id="myID"]...[/wptournregform]</code> is a form where people can register with the competition. It covers some <code>[wptournregfield field="fieldname" /]</code> shortcodes which customize the desired inputs.</li>
<li><code>[wptournreglist tournament_id="myID" /]</code> is a sortable list view of all approved participants.</li>
</ul>
All these shortcodes are customizable through a set of optional attributes.
<h4>Available fields</h4>
<ul>
<li><code>address</code> [text]: self-explanatory.</li>
<li><code>affiliation</code> [text]: club or association.</li>
<li><code>approved</code> [checkbox]: entries become visible in in the list view or through the export filter only afer approved was checked.</li>
<li><code>birthyear</code> [integer]: self-explanatory</li>
<li><code>city</code> [text]: self-explanatory.</li>
<li><code>custom1</code>, <code>custom2</code>, <code>custom3</code>, <code>custom4</code>, <code>custom5</code> [text]: if anything is missing.</li>
<li><code>email</code> [text]: comma-separated list of user names to notify of a new participant.</li>
<li><code>fee_is_paid</code> [checkbox]: self-explanatory.</li>
<li><code>firstname</code> [text]: self-explanatory.</li>
<li><code>id</code> [read-only]: an integer that serves as primary key and is incremented with every registration. Use it to separate entries if people register twice.</li>
<li><code>ip</code> [read-only]: The remote IP of the submitter through <code>wptournregform</code>. May be useful for security checks.</li>
<li><code>lastname</code> [text]: self-explanatory.</li>
<li><code>message</code> [textarea]: self-explanatory</li>
<li><code>phone1</code> [text]: self-explanatory</li>
<li><code>phone2</code> [text]: self-explanatory</li>
<li><code>postcode</code> [integer]: self-explanatory</li>
<li><code>protected</code> [checkbox]: if checked, all contact data of the particiapant are suppressed in list view.</li>
<li><code>rating1</code> [integer]: a rating that is used to calculate ranking lists.</li>
<li><code>rating2</code> [integer]: another rating that is used to calculate ranking lists.</li>
<li><code>time</code> [read-only]: a timestamp that records the exact date and time of submitting. 
It is advisable not to misuse fields since there are some internal checks on the values. Use the custom fields instead. It is hard to say what the length of input fields is in characters as this depends on what is going to. But all are of reasonable length for their purpose.</li>
</ul>
<h4>Attributes</h4>
<pre><code>wptournregedit:
</code></pre>
<ul>
<li><code>tournament_id</code> (required).</li>
<li>
<code>display_fields</code> a comma-separated list of field names in the order of view.
wptournregexport:
</li>
<li>
<code>tournament_id</code> (required).
</li>
<li><code>all</code> if set to any value the list shows all enries, otherwise the ones with a checked <code>approved</code> flag only.</li>
<li><code>class</code> adds a space separated list of custom CSS classes to the form.</li>
<li><code>css</code> adds a style attribute with custom CSS to the form.</li>
<li><code>id</code> adds a custom CSS id to the form.</li>
<li><code>fields_set</code> a comma-separated list of fields which get ignored if empty.</li>
<li><code>filename</code> the name of the export file.</li>
<li>
<code>format</code> a plain text string where all field names preceded by a percent sign (<code>%fieldname</code>) get replaced by the respective field values.
wptournregform:
</li>
<li>
<code>tournament_id</code> (required).
</li>
<li><code>backlink</code> adds a backlink to the plugin’s project page.</li>
<li><code>class</code> adds a space separated list of custom CSS classes to the form.</li>
<li><code>css</code> adds a style attribute with custom CSS to the form.</li>
<li><code>id</code> adds a custom CSS id to the form.</li>
<li><code>disabled</code> submit and reset buttons are disabled if set to any value.</li>
<li>
<code>email</code> a comma-separated list of login names who get an E-mail notification if somebody registeres.
wptournreglist:
</li>
<li>
<code>tournament_id</code> (required).
</li>
<li><code>all</code> if set to any value the list shows all enries, otherwise the ones with a checked <code>approved</code> flag only.</li>
<li><code>backlink</code> adds a backlink to the plugin’s project page if set to any value.</li>
<li><code>class</code> adds a space separated list of custom CSS classes to the form.</li>
<li><code>css</code> adds a style attribute with custom CSS to the form.</li>
<li><code>id</code> adds a custom CSS id to the list.</li>
<li><code>display_fields</code> a comma-separated list of fields on view in that particular order.</li>
<li><code>headings</code> a comma-separated list of column headings in that particular order.</li>
<li><code>protected_fields</code> a comma-separated list of fields that are suppressed if the <code>protected</code> flag is set in the database for a certain user.</li>
<li>
<code>notsortable</code> the columns are sorttable by default. This is suppressed if set to any value.
wptournregfield:
</li>
<li>
<code>checked</code> checks a checkbox if set to any value.
</li>
<li><code>class</code> adds a space separated list of custom CSS classes to the form.</li>
<li><code>css</code> adds a style attribute with custom CSS to the form.</li>
<li><code>id</code> adds a custom CSS id to the form.</li>
<li><code>disabled</code> disables the field if set to any value.</li>
<li><code>field</code> one of the field names (cf. list above).</li>
<li><code>label</code> the label of the field.</li>
<li><code>placeholder</code> the placeholder is shown in an empty field.</li>
<li><code>required</code> if set to any value the field is marked as required.</li>
</ul>
<h4>Usage</h4>
The first example is a registration form. Several <code>wptournregfield</code> shortcodes are wrapped by a <code>wptournregfield</code> one. You can put HTML elements between (fi. fieldsets) in order to design your form:
<pre><code>[wptournregform tournament_id="my_tournament" css_id="my_tournament" email="subscription@example.com"]Red labels indicate required fields!<fieldset><legend>Who you are</legend>[wptournregfield field="lastname" label="Family name" required="1" /][wptournregfield field="firstname" label="Christian name" required="1" /][wptournregfield field="affiliation" label="Club" required="1" placeholder="or 'free agent'" /][wptournregfield field="rating1" label="DWZ" /]</fieldset><fieldset><legend>Your contact data (not to be published)</legend>[wptournregfield field="email" label="E-mail" /][wptournregfield field="phone1" label="Phone 1" required="1" /][wptournregfield field="phone2" label="Phone 2" /]</fieldset>[wptournregfield field="message" label="Your message" placeholder="Whatever you like to tell us." /][/wptournregform]
</code></pre>
The next instance is an editor for the data of the tournament. The non-approved players are highlihted in the selection list:
<pre><code>[wptournregedit tournament_id="my_tournament" display_fields="approved,firstname,lastname,affiliation,email,id,time,ip,rating1,phone1,phone2,protected,custom1,message" /]
</code></pre>
Next is a list view. Normally you will make an password restricted full list for internal use and a small one for the public. Only approved players are on view:
<pre><code>[wptournreglist tournament_id="my_tournament" display_fields="lastname,firstname,affiliation,email,phone1,phone2,message" headings="Last Name,First Name,Club,E-mail,Phone 1, Phone 2, Message" /]
</code></pre>
The next shortcode exports all participants into a csv list which than the is loaded into a tournament manager app (Swiss-Chess in this case). Here also non-approved players get exported. Wrap the field names in sections signs (<code>§</code>) in order to output the respective value.
<pre><code>[wptournregexport tournament_id="my_tournament" all="1" format='"§lastname§, §firstname§";"§affiliation§";"";"";"§rating1§";""' linebreak="1" filename="swiss-chess.txt"]Download Swiss-Chess list[/wptournregexport]
</code></pre>
The following shortcode exports a list of all approved participants who have provided you with a mail address in a way you can directly copy and paste into a mail client. See FAQ for issues with some characters!
<pre><code>[wptournregexport tournament_id="my_tournament" format='"§firstname§ §lastname§" LOWER_THAN§email§>,' fields_set="email" filename="mails.txt"]Download mail list (use BCC!)[/wptournregexport]
</code></pre>

WP Tournament Registration

A simple but highly configurable tournament registration form providing shortcodes for form, list, editor and export views.

meinturnierplan

Roman Perevala

MeinTurnierplan allows you to display tournament tables and match schedules from the MeinTurnierplan language-specific service domains on your WordPress site. Perfect for sports clubs, leagues, and tournament organizers who want to showcase standings, rankings, and match schedules on their WordPress website.
<h3>External Services</h3>
MeinTurnierplan Service (Language Mirrors)
This plugin uses language-specific service domains for both displaying tournament content and retrieving tournament configuration data.
Domain selection by language:
<ul>
<li>German (<code>de</code>) -> <code>https://www.meinturnierplan.de</code></li>
<li>English (<code>en</code>) -> <code>https://tournamentbase.com</code></li>
<li>French (<code>fr</code>) -> <code>https://tournoiplus.fr</code></li>
<li>Polish (<code>pl</code>) -> <code>https://turniej.pl</code></li>
<li>Spanish (<code>es</code>) -> <code>https://torneo.es</code></li>
<li>Italian (<code>it</code>) -> <code>https://torneo.it</code></li>
<li>Slovenian (<code>sl</code>) -> fallback <code>https://www.meinturnierplan.de</code></li>
<li>Croatian (<code>hr</code>) -> fallback <code>https://www.meinturnierplan.de</code></li>
<li>Turkish (<code>tr</code>) -> fallback <code>https://www.meinturnierplan.de</code></li>
</ul>
What it does:
<ol>
<li>
Frontend Display (Public-Facing):
<ul>
<li>Displays tournament tables and match schedules to site visitors via iframe embeds</li>
<li>Endpoints Used:</li>
<li><code>https://{language-domain}/displayTable.php</code> (for tournament standings)</li>
<li><code>https://{language-domain}/displayMatches.php</code> (for match schedules)</li>
<li>When: When a visitor loads a page with tournament content (shortcode, block, or widget)</li>
</ul>
</li>
<li>
Admin Configuration (Admin Area Only):
<ul>
<li>Provides tournament structure data via JSON API to help administrators configure displays</li>
<li>Endpoint Used:</li>
<li><code>https://{language-domain}/json/json.php</code> (tournament structure data)</li>
<li>When: Only in WordPress admin area when:
<ul>
<li>Administrator enters a Tournament ID in settings</li>
<li>Administrator clicks “Refresh Groups” or similar refresh buttons</li>
<li>Admin preview is loaded or refreshed</li>
</ul>
</li>
<li>What it retrieves:
<ul>
<li>Tournament groups/divisions structure</li>
<li>Team lists and names</li>
<li>Tournament options (showCourts, showGroups, showReferees, finalMatches)</li>
</ul>
</li>
<li>Purpose:
<ul>
<li>Auto-populate group selection dropdowns in admin interface</li>
<li>Determine which features are available for the tournament</li>
<li>Provide better admin user experience with automatic configuration</li>
</ul>
</li>
<li>Data cached: Retrieved data is cached for 15 minutes to minimize API calls</li>
<li>NOT used on frontend: JSON API is only contacted from WordPress admin area, never from public-facing pages</li>
</ul>
</li>
</ol>
<ul>
<li>Data Sent: Tournament ID only (no personal data, no user information)</li>
<li>Privacy Policy and Terms are available on the selected language domain under <code>/legal.php</code>, e.g. <code>https://www.meinturnierplan.de/legal.php</code></li>
</ul>
What the Embedded Widgets Collect:
The embedded widgets:
<ul>
<li>NO tracking scripts – The embedded widgets do not use Google Analytics or any other analytics services</li>
<li>NO cookies – The widgets do not set any cookies in users’ browsers</li>
<li>NO third-party resources – The widgets only load CSS styling from the selected service domain (no Google Fonts, AdSense, or other external services)</li>
<li>Communication: The widgets only use JavaScript to send iframe dimensions to your page for proper display sizing (via postMessage API)</li>
</ul>
What Data May Be Collected:
When users view embedded tournament content, the selected service domain’s web server may automatically log:
<ul>
<li>IP addresses (standard web server logs)</li>
<li>Browser type and version (from User-Agent header)</li>
<li>Referrer URL (your website where the widget is embedded)</li>
<li>Access timestamp</li>
</ul>
This is standard web server logging and does not involve cookies, tracking scripts, or persistent user identification.
<h3>Privacy Notice</h3>
This plugin itself does not:
<ul>
<li>Track users</li>
<li>Collect personal data</li>
<li>Use cookies or localStorage</li>
<li>Send personal or sensitive data to any server</li>
</ul>
Data Transmission: 
The only data sent by this plugin is the Tournament ID to the selected service domain when you explicitly add tournament content (via shortcode, block, or widget) to display on your pages.
Embedded Widget Behavior: 
The embedded widgets from the selected service domain:
<ul>
<li>Do NOT use tracking scripts (no Google Analytics in widgets)</li>
<li>Do NOT set cookies</li>
<li>Do NOT load third-party services (no Google Fonts, AdSense, etc.)</li>
<li>Only communicate iframe dimensions back to your page for proper display</li>
</ul>
Standard Web Server Logging: 
Like any web resource, the selected service domain’s servers may log standard HTTP request data (IP address, browser type, referrer, timestamp) when serving the embedded content. This is standard practice for all web servers and does not involve user tracking or cookies.
No Consent Required: 
Because the embedded widgets do not use cookies, tracking scripts, or persistent user identification, no additional cookie consent is required beyond standard web server logging disclosure in your privacy policy.
<h4>Available Languages</h4>
The plugin is available in the following languages:
<ul>
<li>English</li>
<li>German (Deutsch)</li>
<li>Spanish (Español)</li>
<li>French (Français)</li>
<li>Italian (Italiano)</li>
<li>Polish (Polski)</li>
<li>Croatian (Hrvatski)</li>
<li>Slovenian (Slovenščina)</li>
<li>Turkish (Türkçe)</li>
</ul>
<h4>Key Features</h4>
Two Custom Post Types:
<ul>
<li>Tournament Tables – Display standings, rankings, and statistics</li>
<li>Match Lists – Display scheduled matches and results</li>
</ul>
Multiple Display Methods:
<ul>
<li>Gutenberg Blocks – Native block editor support for both tables and matches</li>
<li>Shortcodes – <code>[mtrn-table]</code> and <code>[mtrn-matches]</code> with extensive customization options</li>
<li>Widgets – Legacy widget support for both content types</li>
</ul>
Extensive Customization:
<ul>
<li>Control colors, fonts, borders, and spacing</li>
<li>Toggle visibility of specific columns (wins, losses, logos, etc.)</li>
<li>Customize styling options (colors, fonts, spacing)</li>
<li>Real-time preview while editing in the admin area</li>
</ul>
Additional Features:
<ul>
<li>External integration with tournament management systems via IDs</li>
<li>Responsive design – Mobile-friendly styling with automatic adjustments</li>
<li>AJAX-powered live preview in admin area</li>
<li>Automatic display on single custom post type pages</li>
</ul>
<h4>Usage</h4>
After activation, navigate to Tournament Tables or Tournament Match Lists in the admin menu to create your first content. You can then display your content using:
<ol>
<li>Gutenberg Blocks – Add the Tournament Table or Tournament Match List block to any post or page</li>
<li>Shortcodes – Use <code>[mtrn-table id="123"]</code> or <code>[mtrn-matches id="456"]</code></li>
<li>Widgets – Add the Tournament Table or Tournament Match List widget to any widget area</li>
<li>Automatic Display – Visit single tournament table or match list pages directly</li>
</ol>
<h4>Shortcode Examples</h4>
Tournament Table:
<ul>
<li><code>[mtrn-table id="external-id"]</code></li>
<li><code>[mtrn-table post_id="123"]</code></li>
<li><code>[mtrn-table id="external-id" lang="de" group="A"]</code></li>
</ul>
Matches:
<ul>
<li><code>[mtrn-matches id="external-id"]</code></li>
<li><code>[mtrn-matches post_id="456"]</code></li>
<li><code>[mtrn-matches id="external-id" lang="de" group="A"]</code></li>
</ul>
<h4>Links</h4>
<ul>
<li><a href="https://github.com/AL1337/meinturnierplan" rel="nofollow ugc">GitHub Repository</a></li>
<li><a href="https://www.meinturnierplan.de" rel="nofollow ugc">Plugin Website</a></li>
</ul>
<h3>Development</h3>
The plugin follows WordPress coding standards and best practices:
<ul>
<li>Security – Proper sanitization, validation, and nonce verification</li>
<li>Internationalization – Full i18n support with text domain <code>meinturnierplan</code></li>
<li>Modern WordPress – Support for Gutenberg blocks and REST API</li>
<li>Clean Architecture – Separation of concerns with dedicated classes for each feature</li>
<li>Object-Oriented – Class-based structure with singleton pattern</li>
<li>AJAX Integration – Real-time preview functionality</li>
</ul>
<h3>Support</h3>
For issues, feature requests, and contributions, please visit: 
<a href="https://github.com/AL1337/meinturnierplan" rel="nofollow ugc">GitHub Repository</a>

MeinTurnierplan


Macht was es soll und zeigt Tabellen und/oder Ergebnislisten live auf der Seite an. Sehr einfach zu bedienen, man braucht nur die Turnier-ID die man von MeinTurnierplan hat. Easy!


MeinTurnierplan macht was es soll!

Display tournament tables and match lists using custom post types, supporting Gutenberg blocks, widgets, and shortcodes.

WP Tournament Registration vs MeinTurnierplan