How the Update System Works

Overview

Larapen uses a built-in version management system that tracks the installed version of your core application, each add-on, and each theme independently. When you upload new files from a release, the system automatically detects version differences and guides you through the update process.

How it works

1. Version tracking: Each component (core, add-on, or theme) has a version number stored in its configuration file. The system compares this against the version recorded in your database.
2. Automatic detection: When you log into the admin panel after uploading new files, the system checks whether the code version is ahead of the installed version. If updates are pending, you are redirected to the Update page.
3. Sequential execution: Updates are applied one version at a time, in order. For example, if you are on version 1.0.0 and the new code is 1.3.0, the system will run the 1.1.0 update, then 1.2.0, then 1.3.0; never skipping a step.
4. Database & data migration: Each version update may include database schema changes (new tables, columns) and data transformations (new settings, data restructuring). Both are handled automatically.

What gets updated

• Core application: The main Larapen platform (pages, menus, media, settings, users, etc.).
• Add-ons: Each installed add-on (Blog, Shop, HelpCenter, etc.) is versioned independently and can be updated separately.
• Themes: Themes may also include version updates with layout improvements, new features, or bug fixes.

Version numbering

Larapen follows semantic versioning (MAJOR.MINOR.PATCH):

• MAJOR (e.g., 1.x.x → 2.0.0) : Significant changes that may include breaking changes. Always read the changelog carefully.
• MINOR (e.g., 1.0.x → 1.1.0) : New features added in a backward-compatible manner.
• PATCH (e.g., 1.0.0 → 1.0.1) : Bug fixes and minor improvements.