Skip to content

Shortcodes

Twelve shortcodes: four from Club Player Manager for the club's public forms and the parents' account page, six from English FA for fixtures and results, and two from Card Payment for card payments. All of them go in ordinary page or post content.

You do not always need to place them yourself. The core plugin creates a Join us page (/join-us/) carrying the sign-up form and a My account page (/account/) carrying the account panel, and it can create a page per season with the registration form already on it (Club Management → Settings → Season and squad pages).

Each one also comes as a block, with its attributes as sidebar settings: see Blocks.

Club Player Manager

[cpm_signup_form]

The join-the-club form. Asks for the child's name and date of birth, the parent's name, email and mobile, which teams they are interested in, where they are, and anything else they want to add.

A submission lands on the waiting list and emails the club secretary, the secretary of every squad whose date-of-birth range and type match the child, and a fallback address if no squad matches at all. All three are configured on Email Settings.

[cpm_signup_form]

No attributes. The plugin's own Join us page already shows this form.

[cpm_registration_form]

The season confirmation form parents reach from their emailed link. It lists that parent's children for the season and takes a yes or no for each.

[cpm_registration_form]
[cpm_registration_form season_id="12"]
Attribute Default What it does
season_id the active season Pins the page to one season. Use it when two seasons are open at once.

Parents reach it signed in. The link in every registration, confirmation and payment email, and the one the request form sends, signs the parent in and opens straight onto their children. It works as often as they follow it for 24 hours, then stops. Once signed in, the page knows them on that device without any link, and a parent who saved a passkey on the account page can come back with no email at all. The page shows who is signed in, with links to their account and to sign out. The one other way in is an admin's single-use link for one member. With neither — someone landed here signed out, or their link expired — the page falls back to the request form rather than a dead end.

[cpm_registration_request]

The self-service "send me my link" form, for a parent who has lost their email.

[cpm_registration_request]
[cpm_registration_request season_id="12"]
Attribute Default What it does
season_id the active season, or the most recent season when none is active Which season the link is for

Two ways in:

  • By email address — if it matches a parent on file, their link is emailed to them.
  • By the child's FA Number and date of birth — on a match, the link is emailed to the parent or carer address held for that child. The page confirms where it went with the address partly hidden (for example j•••@example.com), and tells the parent to contact their squad admin if that address needs changing. It never opens the registration form in that browser, so someone who guesses a child's details learns nothing about the family.

A wrong email address gets the same answer as a right one, and every kind of FA Number miss gets the same "no match" answer, so the form cannot be used to find out who is registered with the club. Repeated failed attempts from one address are throttled, and repeat requests for the same address are rate-limited so nobody can be email-bombed.

Put this page's address in the approval email

It is the difference between a parent who has lost their link mailing the club secretary and a parent who sorts it out themselves.

[cpm_guardian_account]

The parents' account panel. Signed out, it offers a passkey sign-in (when the browser holds one) and an email box that sends a one-hour sign-in link. Signed in, it shows the parent's children at the club with their registration and payment status for the active season, their saved passkeys, links contributed by companion plugins under "More from the club", and a sign-out button.

[cpm_guardian_account]

No attributes. You rarely need it: the plugin creates /account/ and adds this panel beneath whatever the page says, and every sign-in link and redirect points there. If you paste the shortcode into that page yourself, the panel appears where you put it instead of being added a second time.

English FA

These need the English FA plugin. Teams are discovered from the matches its collector brings in, so each team attribute takes the team's name exactly as Full-Time writes it (capitals do not matter), or its page slug.

[english_fa_fixtures]

Upcoming fixtures for one team, or for every team when team is left out — which is what a club-wide "next matches" block on a home page wants.

[english_fa_fixtures team="U12 Reds" limit="5"]
[english_fa_fixtures heading="This weekend" show="competition,venue"]
Attribute Default What it does
team every team Which team to list. Name or page slug.
limit the Fixture limit setting (5) How many matches to show
heading Fixtures Replaces the heading above the list
show competition,venue Optional columns, comma-separated: competition, venue

When the list covers more than one team, each row also names the team it belongs to.

[english_fa_results]

Recent results, most recent first. Identical to [english_fa_fixtures] otherwise.

[english_fa_results team="U12 Reds" limit="10"]
Attribute Default What it does
team every team Which team to list
limit the Result limit setting (5) How many matches to show
heading Results Replaces the heading above the list
show competition,venue Optional columns: competition, venue

[english_fa_matches]

Results and fixtures together, results first — the usual contents of a team page.

[english_fa_matches team="U12 Reds" fixtures="5" results="5"]
Attribute Default What it does
team every team Which team to list
fixtures the Fixture limit setting (5) How many fixtures
results the Result limit setting (5) How many results
show competition,venue Optional columns, applied to both lists

[english_fa_teams]

A list of every team English FA has discovered, each linking to its generated page at /teams/<slug>/ (the teams part is the page address set in English FA → Settings).

[english_fa_teams heading="Our teams"]
Attribute Default What it does
heading none A heading above the list

With no teams discovered yet, it renders nothing at all.

[english_fa_latest_results]

The club's latest results for a home page: every team together, newest first, each row naming its team. Only games with a score are listed, so a game whose score was never published does not take a place. Teams whose results the public site hides (under 11s and younger) are left out.

[english_fa_latest_results limit="6"]
Attribute Default What it does
limit 6 How many results to show (all of them, with no Show all link)
heading "Latest results" The heading above the list
show competition,venue Optional details on each row's second line

Under the list, an All results link goes to the club-wide results page (below).

[english_fa_next_games]

Every game across the club from today to the end of the next seven days, soonest first, each row naming its team. Under 11s are included: only their results are hidden, never their fixtures. A game drops off once it has kicked off.

[english_fa_next_games days="7"]
Attribute Default What it does
days 7 How many days to cover, today included
heading "Games in the next seven days" The heading above the list
show competition,venue Optional details on each row's second line

Under the list, an All fixtures link goes to the club-wide fixtures page.

Club-wide fixtures and results pages

Beside the team pages, English FA publishes two pages of its own (no shortcode needed), under the same address as the team pages:

  • /teams/fixtures/: every team's fixtures still to play, soonest first.
  • /teams/results/: every team's results that have a score, newest first. Under 11s and younger are left out, as everywhere results are public.

Each page has a Teams drop-down where any number of teams can be ticked, and From / To dates. Above it, quick filters fill the form in: Next week / fortnight / month on fixtures, Last week / fortnight / month on results (today counts as the first or last day), then All teams, Girls and Mixed (shown when at least one team is linked on English FA → Teams to a squad whose type is Girls; every other team counts as mixed). Pick a date range and a team group, then press Show. The chosen filters stay in the page's address (?team[]=u12-reds&team[]=u12-blues&from=2025-09-01&to=2025-09-30), so a filtered list can be bookmarked or shared. Ticking one team also shows its form strip on the results page. Like the team pages, they are switched off with Team pages (Publish a page for each team) in English FA's settings, and the home page lists then show no link.

Card Payment

These need the Card Payment plugin. Neither takes any attributes.

[ccp_shop]

The public shop. A parent identifies their child by the member's ID number in Club Player Manager (the form labels it Club Player ID) and the child's surname, then picks an active product and pays by card through Stripe Checkout.

[ccp_shop]

[ccp_pay_request]

Where a payment-request email sends a parent: it reads the token in the link, shows what is being asked for, and takes the card payment through Stripe Checkout. Choose the page carrying it as the Payment request page in Card Payments → Settings, or the emailed links have nowhere to go.

[ccp_pay_request]

Both forms answer identically whatever was wrong with the details given, and throttle repeated failures, so neither can be used to find out which children or links exist. Neither marks an order paid: only Stripe's webhook does that.

Notes

Most empty states are rendered, not hidden. A team with no fixtures produces "No fixtures listed at the moment." rather than an empty page — deliberate, so an editor can tell a working shortcode from a mistyped one. An unknown team shows the same empty state. The one exception is [english_fa_teams], which renders nothing until a team has been discovered.

Styles load only where a shortcode renders. English FA enqueues its stylesheet at render time, so pages without a match list carry no extra CSS.

A shortcode rendering as literal text means WordPress is not running shortcodes on that page — usually a block or template outputting raw content. Put it in an ordinary paragraph or shortcode block.