Skip to content

Companion plugins

Club Player Manager does one job: the club's people, their registrations and their money. Four separate plugins add things a club often wants alongside that, without being folded into it.

  • English FA


    Publishes the club's fixtures and results from FA Full-Time, through shortcodes and a generated page per team, and keeps the club's FA registrations, including the FA Club Player Report import.

    English FA

  • Club Mailer


    Lets each WordPress user connect their own Outlook or Gmail mailbox, so club email can go out from a real person's address and land in their own Sent Items.

    Club Mailer

  • Referees


    Keeps the club's referee list — names and phone numbers — and publishes it to the people the club names, behind the sign-in its parents already use.

    Referees

  • Card Payment


    Takes card payments for one-off items, such as kit or tournament fees, through Stripe Checkout: a public shop page, and pay links the club emails to a guardian.

    Card Payment

How they relate to the core plugin

They are genuinely separate plugins, not modules. That has consequences worth knowing before you install one:

They install, update, back up and uninstall independently. Each keeps its data in its own tables. Deleting English FA removes its teams, matches and FA registrations and leaves every member record untouched.

They reach the core plugin only through its platform layer. None of them reads or writes the core plugin's tables directly. English FA, for example, asks the core plugin to save the members and guardians from an FA Club Player Report, and keeps the team registrations from the same report in its own table. Its teams come from the fixtures and results it collects, not from anything the core plugin holds.

They need the core plugin present. All four declare Requires Plugins: club-management, so WordPress will not activate one first. Referees and English FA also use the core plugin's parent sign-in: the referee list, and English FA's match invitations page for parents, sit behind the same /account/ sign-in, so the club has one sign-in for parents, not several.

They are versioned against a platform contract, not against the core plugin's version. The shared admin scaffolding the core plugin exposes — page handlers, view helpers, capability checks — has a version of its own. A companion plugin declares the minimum it needs and refuses to load, with an admin notice rather than a fatal error, against a core that is too old. This matters because core and companions deploy separately: for a few minutes after a release the site can be running a new companion against the previous core, and that window is designed to be harmless.

Developers extending the plugin will want the platform layer for the detail.

Which to install

None is required, and none depends on another.

Plugin Install it if
English FA Your teams play in leagues on FA Full-Time and you want fixtures and results on the club site without maintaining them twice, or you want to import the FA Club Player Report and track FA registrations
Club Mailer Club email should come from a named person rather than a shared noreply@ address — and you can register an app in Microsoft Entra or Google Cloud once
Referees The club books its own referees, and the people who do that booking need their numbers to hand without them being on the public web
Card Payment The club sells one-off items and wants parents to pay by card, separately from the GoCardless registration and instalment payments

Club Mailer is the most involved to set up, because OAuth requires an app registration with the mail provider. English FA needs no API key, but it does need a collector: a small machine, such as a Raspberry Pi on the club's own broadband, that fetches each league's Full-Time code snippet and pushes it to the site, because Full-Time will not serve the site itself. Card Payment needs a Stripe account and a webhook set up in Stripe. Referees needs none of these: a name, a number, and the email addresses of the people who may read them.

Installation for each is the ordinary upload-a-zip flow; see Installation.