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.

ianhaycox

landoweb

This plugin is designed to collect users predictions for each match in FIFA Club World Cup 2025™.
Users predict the score for each match in the group stage and knockout stage and are awarded points based on the accuracy of their prediction. Match results may also be displayed using this plugin.
To view examples of usage, visit the website <a href="http://www.wcp.net.br/" rel="nofollow ugc">wcp.net.br</a>
New in V1.7
Inclusion of single pages for show Predictions by Match and Predictions of User. 
New widget for show standings of Stage Groups. 
Show the widget WorldCupPredictions only to logged users. 
Fix the kickoff times for browsers’ timezone
New in V1.5
Inclusion of matches, teams and locations of the 2014 FIFA World Cup Brazil™. 
Ability for users to toggle match kickoff times between Brazilian and browser local time. 
Manually order Group tables in the event that FIFA draw lots. 
Countdown timer message can be customized to use local language conventions. 
Display all users predictions for all matches with one shortcode. 
Option to show/hide avatar in ranking table. 
Marking a match as finished automatically updates the users prediction scores.
Features
<ul>
<li>easy adding of matches, venues, results</li>
<li>entry form for users to make predictions on each World Cup games</li>
<li>sidebar widget to display prediction standings</li>
<li>sidebar widget to display currently logged in users’ predictions</li>
<li>countdown timer to next prediction deadline</li>
<li>display of match results and group tables</li>
<li>configurable scoring system to award points to users’ predictions</li>
<li>toggle match times to local users browser time</li>
</ul>
Translations
Thank you to the following for language translations available in:-
<ul>
<li>German. – Fred Kuhl</li>
<li>French – Robert Maculewicz</li>
<li>Spanish – Domingo Robaina</li>
<li>Brazilian Portuguese – Ed Torres</li>
<li>Dutch – Deborah Kerkhof</li>
<li>Swedish – Axel</li>
<li>Arabic – <a href="http://www.sada-sy.com/" rel="nofollow ugc">Modar Soos</a></li>
<li>Italian – <a href="http://www.sviluppoiphoneitalia.com/" rel="nofollow ugc">Giulio Giorgetti</a></li>
<li>Russian – Oles Lukas</li>
<li>Serbian – <a href="http://marcrelic.wordpress.com/" rel="nofollow ugc">Marko Relic</a></li>
</ul>
Other translations may be available at <a href="http://www.wcp.net.br/translations/" rel="nofollow ugc">Translations</a>
If you would like to help with translations please visit the page above and give a comment.
<h3>Usage</h3>
After installation, use Import button on the Overview menu of ‘WCP Cup’ to load the teams and match schedules.
Verify the timezone offset on this screen. Any difference should reflect the difference in time between your servers’ local time and Russian time. If this setting is incorrect then users may be able to make predictions after kickoff.
The date and times of matches are in Russian local time (UTC+3)
In order to manage the teams, matches, etc. the logged user must be have the WordPress capability <code>wcup_manager</code>. By default the plugin adds this capability to the Administrator and Editor roles. If the ‘WCP Cup’ menu option is not available, verify that the current user has the <code>wcup_manager</code> role. You may need to install a capability manager plugin to manage roles and capabilities.
Users of the blog do not need any special role or capability to make predictions.
Once imported you may wish to update the URL setting via the Admin->World Cup menu for each team or venue to add links to pages on your site.
<h4>Predictions</h4>
Create a post or page with the shortcode <code>[world-cup-predictor]</code> to display an entry form. Other shortcodes are available to display prediction results and match results. See below for more details.
Users can only predict on matches that have not yet started. Once a match has started it is removed from the entry form preventing further predictions.
<h4>Match Results</h4>
As each match is complete, use the Matches admin menu option to enter the goals scored and check the ‘Match Finished’ checkbox. 
The group tables and match results displayed by the shortcodes will be updated.
Once a team is confirmed as coming first or second in the group stage, edit the Matches to change the placeholder team to the team that has qualified to the next stage. For example, if Russia win Group A, edit Match Number 13 and change the team from ‘WA’ to ‘Russia’.
This change is then reflected in the knockout results table.
<h4>Options</h4>
None as yet.
<h4>Points Calculations</h4>
Once a match has finished, enter the final score in the Matches tab and check the ‘Match Finished’ box. The displayed group tables 
will be updated with the latest team standings.
To update the users’ prediction, select the match in the ‘Predictions’ menu and click ‘Score Selected’. This updates the 
users’ scores in the widget and on results tables.
Points are assigned according to the settings in the ‘Configure Scoring’ tab.
NOTE – The bonus points are cumulative (added to the scores for exact, win and draw).
Therefore be aware that both the bonus goal and bonus goal difference points amounts will always be added 
to the points for a win because the goals and goal difference are the same. 
The bonus goal difference points are always added to a draw because the goal difference will match. 
Adjust the win and draw points appropriately if either of the bonus points are non-zero.
<h4>Shortcodes</h4>
Use the following shortcodes to display a prediction form, match results, users’ rankings.
Prediction Form
You can display an entry form for predictions and the results of matches and predictions with the following shortcodes in a post or page.
<pre><code>[world-cup-predictor]
</code></pre>
Display an entry form for all the configured matches where the kickoff time is before the current date and time. 
The form will display a countdown to the next match deadline. Once the match kickoff time has passed the match will 
no longer be displayed and users cannot make predictions.
You may optionally supply the attribute <code>stage=n</code> where <code>n</code> is the stage id to limit the matches to a particular group.
To display just the matches in the group stages, not the knockout stages, use the attribute <code>group=true</code>, 
e.g. <code>[world-cup-predictor group=true]</code>.
To display matches sorted by kickoff time, rather than by each stage, use the attribute <code>kickoff=true</code> and optionally a 
limit, e.g. <code>[world-cup-predictor kickoff=true limit=5]</code> to display the next 5 matches.
To remove the ability to predict penalties during the knockout stages use the attribute <code>predict_penalties=0</code>.
Group Tables
<pre><code>[world-cup-predictor tables=1 stage=n show_results=n]
</code></pre>
Display the group tables with the match results once the match has finished and the results have been entered. 
You may optionally supply the attribute <code>stage=n</code> where <code>n</code> is the stage id to limit the matches to a particular group. 
You may optionally supply the attribute <code>show_results=n</code> where <code>n</code> = 0 or 1 to hide or show the match results below the group table.
Match Results
<pre><code>[world-cup-predictor results=1 stage=n team=n]
</code></pre>
Display a table of match results. You may optionally supply the attribute <code>stage=n</code> where <code>n</code> is the stage id to limit the matches to a particular group or use attribute <code>team=n</code> where <code>n</code> is the team id to limit the matches to a particular team.
Users Predictions
<pre><code>[world-cup-predictor scores=n]
</code></pre>
For each match ID, specified by <code>n</code>, display a table of every users’ predictions and the points awarded. Note – users predictions will not be shown 
if the match kickoff time has not yet passed. This is to prevent users viewing each others predictions before the match has started.
Use the option <code>[world-cup-predictor scores=-1]</code> to display all predictions for all matches in one table.
Optionally add the attribute <code>highlight="css-styles"</code> to add a CSS 
style to the table row of the currently logged in user. For example <code>[world-cup-predictor scores=1 highlight="background:red;font-weight:bold"]</code>.
Logged in Users Predictions
<pre><code>[world-cup-predictor user=1 show_total=n show_results=m]
</code></pre>
For the currently logged in user display the list of predictions for that user. If <code>n</code> is non-zero then show the total points for this user 
at he foot of the table. If <code>m</code> is zero do not show match results against each prediction. Also available via the Widgets.
You may also display just the users total via <code>[world-cup-predictor show_total=1]</code> without the table.
Rankings
<pre><code>[world-cup-predictor ranking=1 limit=999]
</code></pre>
Display a summary of all the users’ points as a ranking table. Optionally add the attribute <code>highlight="css-styles"</code> to add a CSS 
style to the table row of the currently logged in user. For example <code>[world-cup-predictor ranking=1 highlight="background:red;font-weight:bold"]</code>.
Also available via the Widgets.
<h4>User Rankings Widget</h4>
The widget displays similar output to the shortcode <code>[world-cup-predictor ranking=1 limit=9999]</code>
Drag and drop the widget to a sidebar and configure. Multiple instances of the widget, each configured separately, may be 
placed on a sidebar.
If not blank, the URL option adds a link to the full results page using the title below as the link text.
<h4>User Predictions Widget</h4>
The widget displays the list of the currently logged in users’ predictions similar in output to the shortcode <code>[world-cup-predictor user=1]</code>
Drag and drop the widget to a sidebar and configure.
<h4>Toggle timezones</h4>
All match kickoff times and dates are displayed in Brazilian local time. If you have changed the match times in the admin screens 
to another timezone, this will NOT work.
To allow a user to toggle between BRST and local time you need to add the following code in your blog post, or sidebar, that contains 
one of the plugin shortcodes: For example,
<pre><code><div class="tzcContainer">
 Match times are currently set to match local time, please click here to convert to your time zone.
 Match times are currently set to your timezone, please click here to revert to local time.
</div>
</code></pre>
The text can be changed to anything appropriate and include images etc. The key items are: <code>id="tzLocal"</code> and <code>id="tzClient"</code> with the 
second item having <code>style="display:none"</code>. Users clicking on either of these sentences will toggle all match kickoff times between 
BRST and browser local time. It does rely on the users’ browser being configured correctly for their timezone and locale.
By default the plugin will also attempt to display match kickoff times in the users local language.
To disable this <code>auto-translate</code> feature uncheck the setting on the overview screen.

World Cup Predictor

Plugin to manage soccer predictions and present a fantasy football competition for the FIFA Club World Cup 2025™.

WP Tournament Registration vs World Cup Predictor