Skip to the products
LCPanelLicence Center Panel

Updating to a new version

An update replaces the script files and updates the database - from the admin panel or by FTP - and never touches your settings or uploads.

Keeping it running Updated 6 Nov 2026 5 / 40

An update replaces the script files and updates the database. It never touches config.php, installed.lock, .htaccess, uploads/ or your settings.

From the admin panel

Admin → Updates.

  1. Check now asks the licence site whether a newer version exists.
  2. Backups → Make a backup now saves the script files as a ZIP in cache/backups. Download it. Also download a database backup on Admin → Tools.
  3. Update → Download now fetches the package and compares its SHA-256 with the one the licence site announced. A package that does not match is never installed.
  4. Install the downloaded package copies the new files over the old ones, runs the database update and clears the cache.

A valid licence key is needed for steps 1 and 3.

The manual way (FTP)

This always works, also on hosts with a short time limit.

  1. Download MyMeetBook-<version>-update.zip from your account on lcpanel.com.
  2. Upload it to the folder of the site and extract it over the existing files.
  3. Open https://your-site/db_update.php once while signed in as an admin.

The update package has no install.php, so extracting it can never start a new installation.

What an update contains

The whole script with its plugins and the default theme. Plugins and themes you bought separately are updated with their own ZIP on Admin → Plugins → Upload or Admin → Themes; uploading a newer ZIP over an installed one updates it and keeps its settings.

If something goes wrong

  • A white page after an update. Extract the backup ZIP from step 2 over the site. The files are back as they were.
  • The time limit was hit. Use the manual way.
  • Something looks old. Admin → Tools → Clear the cache, then reload the page with Ctrl+F5.

db_update.php is safe to open more than once: each step runs only once and is remembered.

The update page

Opened in the browser by an admin, db_update.php shows a report instead of plain text: the site logo, the version the site was on and the version it is going to, every update step with its state (done before, ran now with a green tick and how long it took, failed with the error in red, or skipped because an earlier step failed), the counts, and a big summary — green Your site is up to date, or red Something failed with what to do next (read the error, fix the cause, open the page again; steps that already ran are never repeated). Back to the admin panel takes you home. It works on a phone and follows the light or dark mode of the site. From the command line (php db_update.php) it still prints the same plain text as before, and the quiet run after an update from the admin panel is unchanged.

What changed

The notes of the new version are added to your What's new page by the daily cron job, so your members see them too. Admin → What's new adds them at once, and lets you edit, hide or delete each entry.

Was this helpful?
Share this chapter