নতুন ভার্সনে আপডেট

An update is three moves: back up, extract the update ZIP over the installation, and run the database update. Your settings, clients, invoices and uploads are never in the ZIP, so they cannot be overwritten. This chapter covers the update ZIP, the two ways to run the database update, what you must never overwrite, the checks afterwards, and how to go back.

The two packages

Both come from your account at license.faruk.bd. Neither ever contains config.php, installed.lock, anything inside data/ or anything inside uploads/. Utilities → What's New shows what each version brought and any message the License Center has for you.

What you never overwrite

Two things the ZIP does replace, so watch them:

• .htaccess: if you changed RewriteBase for a sub-folder install, or added your own rules, put them back after extracting.
• Files you edited yourself inside the script, a plugin or a theme. Keep your own look in a copy of a theme under another code instead of editing the shipped one. Plugin and gateway settings are in the database and are safe.

Step by step

1. Back up. In cPanel use Backup (or Backup Wizard) for the home folder and phpMyAdmin → Export for the database. On a VPS, copy the folder and run mysqldump. Keep both until the update is checked.
2. Download the update ZIP of the new version.
3. Upload and extract it into the installation folder with the File Manager or FTP, answering Overwrite when asked.
4. Run the database update, in either of two ways below.
5. Check the list at the end of this chapter.

Running the database update

New versions can add tables, columns, settings, roles and e-mail templates. The database update brings the database to the version of the files. It is safe to run twice and never deletes data.

From the admin area: open Setup → Database Update. The page shows four figures: the Script version, the Schema it needs, the Schema in the database and Tables missing. A green notice says The database is up to date.; an orange one says The database needs an update. and lists missing tables. Press Run update. It creates missing tables, lets every active plugin create its own tables, adds missing settings, roles, statuses and e-mail templates, and writes a short report on the page. Steps done lists the tagged steps that have run.

The full step runner: the same page has the button Open db_update.php (full step runner). Each new version can carry numbered steps (for example 1.1.0-something) that do heavier changes. Every step runs exactly once, and the script remembers which ones are done. The runner needs you to be signed in to the admin area with a role that may Configure General Settings. Open https://your-domain/db_update.php and read the plain-text report: lines starting done succeeded, a line starting FAILED names the step and the reason.

From the command line (VPS, or cPanel Terminal):

php db_update.php

Run it from the installation folder. It needs no sign-in. It prints the same report.

Run Run update after every update, even when the notes do not mention the database. It also adds the e-mail templates a new version introduced, without touching templates you edited.

Checks afterwards

1. Utilities → What's New or Utilities → System Health & PHP Info shows the new version number.
2. Setup → Database Update says The database is up to date.
3. Setup → Licence: press Check now; the state should be Active.
4. Utilities → Automation Status: the heartbeat is Alive and the last runs say OK.
5. Open the store, a product page and one invoice in the client area, and the admin dashboard.
6. Look at data/logs/errors.log for new lines (see Troubleshooting).
7. Clear your browser cache if the layout looks old.

Going back

An update that misbehaves can be undone only from your backup, because a database update may have added columns and settings the old files do not know:

1. Restore the files from your backup (but keep the current config.php).
2. If the database update had already run, restore the database export too.
3. Run Check now on the Licence page.

Tell support the version, the message in data/logs/errors.log and the FAILED line of the step runner if there was one.

Moving to another server or domain

Copy the whole folder, including config.php, data/ and uploads/, and import the database export. Then edit config.php (the AB_DB_HOST, AB_DB_NAME, AB_DB_USER and AB_DB_PASS lines), set the new System URL under Setup → General Settings, and, if the domain changed, release the licence on the old domain first (see The licence key). Set up the cron job again (Installing).