Guides
Coming from Okno
Leiho was called Okno until 1.0.0-beta.11.
Okno was renamed Leiho in 1.0.0-beta.12, because another project already used the name. Your content, settings and front end are carried over.
- Back up the database.
- Upload
leiho.zipin Plugins → Add New → Upload Plugin, deactivate Okno, then activate Leiho. If both are active, Leiho waits and asks you to deactivate Okno. - Leiho takes over Okno's settings, tokens, content types and their values, change history and per-user preferences, then confirms it in wp-admin. You can then delete Okno: its uninstall leaves Leiho's data alone.
Update the CMS first. Your front end keeps working unchanged until Leiho 2.0: the okno/v1 REST routes, the X-Okno-Token header, data-okno-* attributes, the Okno bridge, OKNO_URL / OKNO_TOKEN and the .okno/ snapshot are still understood, and okno_* hooks still run (with a deprecation notice under WP_DEBUG). Switch when convenient:
| Okno | Leiho |
|---|---|
npm i @pixelersagency/okno-bridge |
npm i leiho |
initOknoBridge, OknoBridge, loadOknoContent |
initLeihoBridge, LeihoBridge, loadLeihoContent |
okno-bridge.js |
leiho-bridge.js |
data-okno-section, data-okno-layout… |
data-leiho-section, data-leiho-layout… |
/wp-json/okno/v1/…, X-Okno-Token |
/wp-json/leiho/v1/…, X-Leiho-Token |
npx okno pull, OKNO_URL, OKNO_TOKEN, .okno/ |
npx leiho pull, LEIHO_URL, LEIHO_TOKEN, .leiho/ |
okno.schema.json, okno_* hooks, OKNO_KEEP_DATA |
leiho.schema.json, leiho_* hooks, LEIHO_KEEP_DATA |