Updates

Updates arrive as a zip built for your current product version. They never replace client-config/, .env, or files already in private/.

FTP update

1. Upload the update zip and extract it over the existing files in public_html (binary FTP mode).
2. Do not delete client-config, .env, or private contents.
3. Sign in as admin, open Setup → System, re-authenticate if asked.
4. If any file does not match the release, upload the zip again in binary mode.
5. Click Run update (or download from the update server if enrolled). Migrations run and obsolete release files are removed when unchanged.

Take a backup from System before updating.

Remote updates (optional)

When your store is enrolled, System shows the next release and its changelog. Download and update checks the zip hash and unpacks only allowed paths. The admin must re-authenticate to apply.

Enrollment starts from System; Mariviq approves the code shown on the update server.

Help for your version

On System, Help for this version opens the knowledge base snapshot that matches the release running on your server.