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.

Marco Belemmi

Chess Podium helps chess clubs organize tournaments directly from WordPress. Create tournaments, add players, generate Swiss pairings, enter results, and publish standings—all without spreadsheets.
Free plan includes: 
* Up to 10 players per tournament 
* Swiss pairing 
* Round Robin and Double Round Robin 
* Results and standings 
* Public tournament page 
* CSV export 
* FIDE ID import
Upgrade to Pro for unlimited players, advanced exports, PGN pages, and more. <a href="https://chesspodium.com/pricing/" rel="nofollow ugc">Get Chess Podium Pro →</a>
<h3>Terms of Service and Privacy Policy</h3>
This plugin may link to the plugin website’s legal pages. Ensure these URLs are valid and publicly accessible: 
* Terms of Service: https://chesspodium.com/terms-of-service/ 
* Privacy Policy: https://chesspodium.com/privacy-policy/
If your site uses different paths, create the corresponding pages and update the links where the plugin references them.
<h3>External services</h3>
This plugin relies on the following third-party services to provide core functionality:
<ol>
<li>
Chess Podium Pairing API (http://89.167.56.28): Used to calculate tournament pairings (Swiss System and Round Robin). The plugin sends tournament data (player names, ratings, and results) to this server to generate the next round’s pairings.
<ul>
<li>Service provided by: Chess Podium.</li>
<li>Data sent: Tournament IDs, player names, and scores.</li>
</ul>
</li>
<li>
FIDE Ratings (https://ratings.fide.com): Used to fetch and update player Elo ratings and titles based on their FIDE ID.
<ul>
<li>Service provided by: International Chess Federation (FIDE).</li>
<li>Data sent: FIDE ID (public identifier).</li>
</ul>
</li>
<li>
Stripe (https://api.stripe.com): Used to process payments for the Pro license.
<ul>
<li>Service provided by: Stripe, Inc.</li>
<li>Terms of Service: https://stripe.com/legal</li>
<li>Privacy Policy: https://stripe.com/privacy</li>
</ul>
</li>
<li>
PayPal (https://api-m.paypal.com, https://api-m.sandbox.paypal.com): Used to process payments for the Pro license.
<ul>
<li>Service provided by: PayPal Holdings, Inc.</li>
<li>Terms of Service: https://www.paypal.com/webapps/mpp/ua/useragreement-full</li>
<li>Privacy Policy: https://www.paypal.com/webapps/mpp/ua/privacy-full</li>
</ul>
</li>
</ol>
Additional services (optional, depending on configuration):
<ul>
<li>Chess Podium License API (chesspodium.com): Validates Pro licenses. Sends: license key, site URL. Ensure Terms and Privacy pages exist on your site (e.g. /terms-of-service/, /privacy-policy/) or use your own policy URLs.</li>
<li>Lichess (lichess.org): PGN live feed for broadcast games. Fetched server-side; no user data sent.</li>
<li>Wikimedia (Wikipedia REST API, Wikidata SPARQL — wikipedia.org, wikidata.org): Optional. Used only to resolve player profile thumbnail images when FIDE does not return a usable photo. Sends: player name and/or FIDE ID (public). No account data.</li>
</ul>
Note on shortcode names: This plugin uses the prefix <code>chess_podium_</code> for all new shortcodes (e.g. <code>[chess_podium_tournament]</code>, <code>[chess_podium_manager_tornei]</code>). Legacy shortcodes <code>checkmate_manager_tornei</code>, <code>storico_tornei</code>, and <code>regina_torneo</code> are kept only for backward compatibility; prefer the <code>chess_podium_*</code> equivalents for new installations.
<h3>Third-party software</h3>
For third‑party software licenses and external services used by this plugin, see <code>THIRD-PARTY.txt</code> in the plugin root.

Chess Podium

Manage chess tournaments from WordPress: players, Swiss pairings, results, standings, and exports. Free plan: up to 10 players per tournament.

WP Tournament Registration vs Chess Podium