A KAS installation combines Core, project-owned themes, private configuration and its database. Preserve encryption keys, credentials, uploaded files and application data when installing or updating. Use the installation package and approved configuration supplied for that installation; do not copy another project's secrets or database as a generic setup.
Core updates
Use the native updater for the installation. Database migrations run before their corresponding application files. File eligibility is checked against the executing update and SHA-256 verification protects downloaded contents. Failed file synchronization can resume without treating future/ineligible files as obsolete. Back up the database and relevant files before operational updates and verify the intended menus, forms and tables afterward.
Developer file registration
Register every new or modified distributed Core file in its owning update case, preserving published migration history. UPDATE_VERSION is the minimum eligible executing update; VERSION is the separate synchronization timestamp. Historical eligibility remains unchanged unless that file's contents change. Documentation, tests and local tooling are not customer runtime files.
// $release is the actual owning update number from your maintenance record.
if (!is_int($release) || $release < 1) {
throw new InvalidArgumentException('A valid owning update is required.');
}
$sql = "INSERT INTO KAS_UPDATES(FILE,VERSION,UPDATE_VERSION)
VALUES ('kas/includes/EXAMPLE/VIEW_ITEMS.php',0,$release)
ON DUPLICATE KEY UPDATE VERSION=0,
UPDATE_VERSION=GREATEST(UPDATE_VERSION,VALUES(UPDATE_VERSION))";
The file path is illustrative; use the real distributed file and actual case. Customer installations receive Core through the native updater. Preserve project overrides, configuration and mutable data. Developer documentation does not authorize running an update or modifying an installation.
Section initialization
After section definitions are deployed to an installation, log out, open its /kas/init route and accept native section initialization. Sign in again and verify navigation. Run this on each intended target; initializing one does not update another. See Creating a KAS section for registration and hidden-page routing.
Validation and query failures
Check PHP compatibility, actual Form/Table workflows, permissions, migration repeatability and file coverage before delivery. Use isolated test data and preserve operational backups. A successful DB_connector query has getError()===false, including an empty SELECT; a failed new_query() can itself be false. Never call result methods before checking the query outcome.
$result = $connection->new_query($sql, false, true);
if ($result === false || $result->getError() !== false || $result->getErrorNo() != 0) {
throw new RuntimeException('The update query failed.');
}