Licensing
A MilliCache Pro license unlocks the premium modules and plugin updates. Page caching itself never depends on the license: an expired or missing license leaves everything MilliCache itself provides fully intact.
Activating a License#Copied!
- Go to Settings → MilliCache → Settings → License.
- Paste the key from your purchase email into the License key field.
- Click Activate.
The section badge switches to Active and every Pro module unlocks. Lost your key? It is always available in your customer dashboard.
Once active, the key field is locked and displayed masked (first and last three characters only). The key is stored encrypted in your database and is never exposed in full through the settings screen or the REST API.
Seats and License States#Copied!
Your plan includes a number of seats (sites). Activations are checked against millipress.com, and the Status tab always tells you where you stand:
| State | Meaning |
|---|---|
| Active | Everything is fine; all premium features are available. |
| Grace | You are over your seat limit, but premium features keep working for a grace period. Review your plan before it ends. |
| Over capacity | The grace period has ended; premium features are disabled until you free a seat or upgrade. |
| Revoked / not found | Contact support or check the key; page caching is unaffected. |
Going over the limit never breaks anything abruptly: you always pass through the grace state first.
Moving to a New Site or Domain#Copied!
Before migrating, click Deactivate in the License section. This frees the activation slot upstream, so you can re-activate the same key on the new site or domain.
If you clone a site (staging copies, migrations that duplicate the database), the clone carries the original's install identity. Give the clone its own identity with:
1wp millicache license install-id reset
Multisite Networks#Copied!
On multisite, licensing is flexible per site:
- Network key (default): activate one key in the Network Admin License section via Network Activate. Every active subsite uses it and counts toward your seat limit.
- Own key: a subsite can activate its own separate license key instead. Its License section is visible to super admins.
- Opted out: a subsite can be excluded from the network license entirely, running without the Pro features.
Network Deactivate frees the seats of every subsite using the network key and clears the saved key; subsites with their own license are unaffected.
WP-CLI#Copied!
| Command | Description |
|---|---|
wp millicache license status |
Show state, seats, and the masked key |
wp millicache license activate --key=<key> |
Save and activate a license key |
wp millicache license deactivate |
Deactivate and free this install's seats |
wp millicache license subsite-state <blog_id> [<state>] |
Show or set a subsite's license mode: network, own_key, or opted_out (multisite) |
wp millicache license install-id [show|reset] |
Show or reset the install identity (reset after cloning) |
Options:
statussupports--format=table|json|csv|yamland, on multisite,--networkto list every subsite's license mode plus a network summary
Examples:
1# Activate
2wp millicache license activate --key=00000000-1111-2222-3333-444444444444
3
4# Check the whole network at a glance
5wp millicache license status --network
6
7# Let one subsite use its own key
8wp millicache license subsite-state 3 own_key
Good to Know#Copied!
- Settings resets keep your license. A full settings reset restores caching defaults but preserves the license key (along with storage and Edge Cache credentials), so you never have to dig out the key again.
- Updates are license-gated. Plugin updates arrive via the normal WordPress update flow as long as the license is active; see Installation.
- Try prereleases on staging. Add
define( 'MC_UPDATE_PRERELEASE', true );towp-config.phpto follow the prerelease channel, and the update flow offers the newest build including prereleases. Leave it out (the default) to track stable releases only. Best kept to a staging site. - Your key doubles as the Composer credential. Installing via Composer authenticates against the MilliPress package repository with the license key as the HTTP Basic password; downloads require an active license.
- Support snapshots are safe to share. The Status tab's support snapshot includes the license state and seat usage but never the key itself.
Next Steps#Copied!
- Modules Overview: what your license unlocks
- Installation: if you have not installed yet
Last updated: