Booknetic / Alovio Essentials

Getting started

What Alovio Essentials is — nineteen Booknetic add-ons in one plugin — how to install and licence it, and the two switches that decide what runs.

Alovio Essentials folds nineteen Booknetic add-ons into one plugin. Each one is a self-contained module you switch on or off site-wide, and — where it makes sense — gate per Booknetic plan. Instead of installing, updating and licensing a shelf of separate plugins, you run one, and turn on only the features you need.

It works on both Booknetic and Booknetic SaaS. Most features run on either; a handful are platform-owner tools that only mean anything on SaaS. See The features.

Requirements

  • Booknetic installed and active. Essentials registers as a Booknetic add-on; without Booknetic it does nothing.
  • Booknetic SaaS for the SaaS-admin features (Bulk Workflow Tools, Tenant Categories, Platform Customers, Dormant Tenants, Workflow Menu Control). On a regular install those modules are hidden.
  • PHP 7.4 or later.
  • A few features depend on something of their own — an online gateway, the Locations module, the official Giftcards add-on, a core hook. Each is listed with the feature in The features, and the Hub’s health checks flag anything missing.

Install

  1. Download the Alovio Essentials zip from your Code Heaven account.
  2. In wp-admin go to Plugins → Add New → Upload Plugin, choose the zip, install and activate.
  3. Activate your licence — see Licence & updates.

Until a valid licence is active, no feature registers anything — no hooks, no plan capabilities, no menu entries. The Hub stays reachable so you can enter a key, and nothing is deleted while you wait. Activating a key brings everything back exactly as it was.

The Hub

Everything lives under one admin menu, Essentials: an Overview that reads the health of the bundle, a page per feature, an activity log, settings of its own, and the Licence page. On a regular Booknetic site the Hub is in the Booknetic admin; on Booknetic SaaS it lives in the SaaS admin (the platform owner’s), never in a tenant’s panel — the switches are a platform decision. See The Hub.

The two switches

Every feature answers to a platform-wide on/off toggle. Turn it off and the module registers nothing at all. Turn it on and it runs.

On Booknetic SaaS, a feature that is tenant-facing also carries a Booknetic plan capability — the platform’s own mechanism for deciding which plans (and so which tenants) get it. So a feature reaches a tenant only when it is globally on and that tenant’s plan grants it. A few features have no plan capability and simply apply wherever they are switched on; the SaaS-admin tools have none because they are the platform owner’s, not a tenant’s. Enabling features walks through both switches.

Coming from the standalone add-ons

Several of these modules began life as separate plugins. Essentials keeps the same database table names and the same plan-capability slugs those plugins used, so a site already running one keeps its data and its per-plan grants when it moves across — switch the standalone plugin off, switch the matching Essentials feature on, and the records are still there. Switching an Essentials feature off never drops its tables either. See the FAQ.

Try it live

There is a live admin demo at demo.alovio.org — it opens straight on the Essentials Hub so you can see the features, the health checks and the settings without a login.