[bonelifer]

Boards running Kailey's kinerity/knowledgebase extension can now move to this one: disable kinerity, keeping its data, and enable this extension. Enabling it imports kinerity's categories, articles and permissions. Nothing has to be converted by hand. The steps are in docs/upgrading-from-kinerity.md.

Builds on the PostgreSQL fix PR (its two commits are at the start of this branch). Merge that one first.

How it works

• kinerity's tables are also called kb_articles and kb_categories, with different columns. A new migration that runs before version_1_0_0 copies them to backup tables (kb_kinerity_*) and checks that every row arrived. Only then does it drop the originals, so this extension can create its own tables. The backup tables stay.
• version_2_0_32 imports from the backup, a batch at a time:
  • Categories: the same tree. Descriptions become plain text, at most 255 characters.
  • Articles: text, author, dates and views are kept.
    • Approved articles are published.
    • Waiting articles go to the approval queue.
    • Deleted and denied articles are kept, deactivated.
    • An article in several categories goes in the oldest one and is cross-listed in the rest.
    • Articles kinerity left in no category go in a new category, named in the board's language.
  • Permissions: each group's and user's kinerity setting (Yes or Never, set directly or through a role) is given to them on every category. kinerity's "read" and "manage" permissions become u_kb_view and a_manage_kb.
  • Clean-up: kinerity's permissions, ACP modules, settings, notification types and extension entry are removed. Its migration records stay, on purpose: re-enabling kinerity would otherwise drop this extension's tables.
• Each backup row records the id it got here, and is claimed inside its batch's transaction before it is converted. An import that stops part way carries on where it stopped, and two requests at once never import the same row twice.
• Enabling this extension is refused while kinerity is still enabled.

On large boards, use the command line. phpBB's ACP enables an extension in one page load, so a large import can end on a time-out page while PHP keeps going. Nothing is lost: purge the cache and enable again. The guide explains this.

Tests

• tests/kb_kinerity_import_test.php builds this extension's real tables from its own migrations and covers each case above, including an import stopped part way and two imports running at once, on SQLite, MySQL and PostgreSQL. The full suite passes on phpBB 3.3.x and master, none skipped.
• Claude switched seed-forum boards of 2,000 categories and 50,000 articles on phpBB 3.3 (MySQL, PostgreSQL, SQLite) and 4.0 (MySQL, PostgreSQL), through both the command line and the ACP. tests/board/kinerity_import_check.php compared every imported row with kinerity's. All checks passed on every board.
• tests/browser/kb_kinerity_import.js passed 14 browser checks on the result.
• Details, and what was not covered, are in docs/testing.md.

Not imported: old kinerity links (/kb/viewarticle?a=…) don't lead to the new article ids; the backup tables record old and new ids.

The board fixture and the ACP helper used for testing are in phpbbmodders/seed-forum and phpbbmodders/phpbb-release-tools PRs.

---

Investigated and written by Claude on behalf of William Jacoby (bonelifer).

🤖 Generated with Claude Code