The Hub

The Hub is where you run the bundle. On a regular Booknetic site it sits in the Booknetic admin; on Booknetic SaaS it lives only in the SaaS admin — the platform owner’s — because the switches are a platform decision and no tenant sees them. It is one menu, Essentials, with an Overview page and four sub-pages: Features, Activity, Settings and Licence.

Because the Licence page is the only way to re-open the gate once it is shut, the Hub stays reachable even when no licence is active. Every tile and number on it is computed defensively: a source that fails renders “n/a” and is logged, never a blank page.

Overview

The landing page of the Hub. It reads the state of the whole bundle at a glance:

• Health — a running total of issues, green when there are none. See below.
• Features on — how many of the features visible in this context are switched on, out of the total.
• On Booknetic SaaS, a couple of live figures where the matching feature is on — for example how many tenants have a category (Tenant Categories), and the last Bulk Workflow Tools run.
• The most recent activity, and quick links into the features and their tools.

Health checks

The health checks look only at what actually applies to your site — a switched-off feature is never a fault, and SaaS-only checks don’t run on a regular install. What they surface:

• Database schema. Any switched-on feature whose table is behind its current version. The upgrade runs by itself on the next admin page load; the check just tells you one is pending.
• Core hook for Service Break. Service Break needs a hook (bkntc_staff_appointments) that older Booknetic versions don’t fire. Where it is missing, the check explains it and — if the file is writable and in the layout it recognises — offers to add the one line for you, keeping a backup. On a server with no PHP command line it says so, because the patched file can’t be syntax-checked afterwards. A Booknetic update removes the line again, and the check offers it again.
• Core patch backups. Each Booknetic update rewrites that file and the patch re-applies, so the backups pile up. When more than one is sitting in Booknetic’s plugin folder, the check offers to delete all but the most recent.
• Backup directory (SaaS, with Bulk Workflow Tools on) — whether the folder bulk runs back up to is writable, so a run can be undone.
• Orphaned workflow actions (SaaS, with Bulk Workflow Tools on) — workflow actions whose workflow no longer exists and can never fire, with a one-click clean-up.

Each check that found something offers the fix inline; nothing is changed until you press the button.

Features

One row per feature, grouped the way they are grouped in The features. Each row shows the feature’s switch, its scope (site-wide, or — on SaaS — per plan), and, where it has a plan capability, how many active plans grant it. From here you open a feature’s own detail page: what it does, how it works, where it shows, what it depends on, its settings, and any caveats worth knowing. See Enabling features.

Activity

A log of what changed and who changed it — a feature switched on or off, settings saved, a bulk job run, a core patch applied. It is kept for as long as the retention you set on the Settings page, and it is fail-safe: a logging problem is recorded to the server log and never interrupts the action it was describing.

Settings

Essentials’ own settings, platform-wide. They are a short list of numbers, each clamped to a safe range:

• how long the activity log is kept;
• how long Bulk Workflow Tools backups are kept;
• the batch sizes Bulk Workflow Tools uses for delete and import runs.

Licence & the update check

The Licence page activates the site, re-checks the key, or releases the seat so the key can be used elsewhere. It also carries a Check for updates button that asks the update server straight away rather than waiting for WordPress’s own schedule. The same button sits on the WordPress Plugins screen, next to Deactivate, for when that is where you happen to be. See Licence & updates.