Kjeks
← All docs

Kjeks Add-ons — manage the family from one screen

Install, activate, update, and remove every Kjeks add-on from a single Add-ons screen under Cookie Consent — downloaded straight from each add-on's GitHub release.

Requires WordPress 6.8+PHP 8.3+Requires the Kjeks core Source on GitHub →
101 · Setup201 · What it does301 · Catalog, tokens & internals

101 Setup

Kjeks Add-ons is a small companion for the core plugin. It doesn't gate anything itself — it gives you one screen to manage the rest of the family so you don't have to download and upload each add-on by hand.

Install & activate

  • Download the latest kjeks-addons.zip and upload it under Plugins → Add New → Upload Plugin, then activate it (network-activate on multisite).
  • Updates arrive automatically from GitHub releases.

Open the screen

Go to Cookie Consent → Add-ons. Each add-on shows a card with its status, installed and latest version, and buttons to install, activate, deactivate, update, or delete it.

201 What it does

Every card action downloads the add-on's latest release zip from GitHub and runs the standard WordPress plugin installer, then activates, deactivates, updates, or deletes it in place:

  • Install — fetches releases/latest/download/<slug>.zip and installs it.
  • Activate / Deactivate — network-wide on Multisite, per-site on a single install.
  • Update — overwrites in place when a newer release tag is published.
  • Delete — deactivates (if needed) and removes the plugin.
  • Check updates now — clears the cached release tags so the latest versions refresh immediately.

The Add-ons menu carries a badge counting how many installed add-ons have a newer release available. Each card also links to the add-on's readme (a details modal) and its GitHub repository.

On Multisite the screen lives under the network Cookie Consent menu and requires the manage_network_plugins capability. On a single site it lives under the site menu and requires install_plugins.

301 Catalog, tokens & internals

The catalog

The manager ships a fixed catalog of the official add-ons — Google Consent Mode, Embeds, Scripting, Social, and the AI Reviewer. Each entry resolves to a GitHub release zip, a raw readme.txt for the details modal, and a plugin file path used to detect install and activation status.

Private repositories

Release downloads and version checks are unauthenticated by default. If any add-on repository is private, define a GitHub token and the manager sends it as a bearer token on every request: 

// wp-config.php — only needed while any add-on repo is private:
define( 'KJEKS_GITHUB_TOKEN', 'ghp_xxx' );

Self-updates

Kjeks Add-ons updates itself from its own GitHub releases through the shared Soderlind\WordPress\GitHubUpdater, the same mechanism every add-on in the family uses. Latest-version lookups are cached for six hours to stay within GitHub's rate limits; Check updates now clears that cache.

Building your own add-on? Follow the Build an add-on guide — anything published to GitHub releases with a matching zip name can be managed the same way.