Updating EasyChat

Generic PHP provides an Install update button. EasyChat creates a protected backup before publishing verified files. If the new version cannot be fully verified, the previous files are restored automatically.

After confirmation, the screen shows four clear phases: verification, download, preparation, and installation. If the browser loses its connection or the page is reloaded, EasyChat reconciles the saved phase and continues the same operation. It never starts another installation on top of one already in progress. EasyChat retries a temporary failure first and shows Retry phase only when operator input is actually needed.

If EasyChat has already been updated in another tab or by a manual deployment, the Update Center closes the earlier operation automatically. Its old error and Retry phase action disappear without reinstalling the older archive.

Before replacing files, EasyChat waits up to 70 seconds for active requests to finish. If it cannot proceed, the message explains how to retry and check long-running jobs or permissions on the log directory. There is no need to delete lock files manually.

Preparation files are kept outside the running EasyChat directory. This keeps the updater from trying to publish a source tree over itself even when the hosting log directory lives inside the installed runtime.

On Windows, EasyChat follows the platform’s access model instead of reporting a false failure for unavailable POSIX permission bits. When an earlier request is still finishing, the installer briefly waits for the files to be released instead of failing immediately.

The first transition from an older installation to protected updates may need up to four minutes once while previous server requests finish. Update Center shows an exact countdown and resumes automatically. Later updates wait for actual active requests only and usually start much faster. Keeping the tab open is still preferable, but a page reload no longer loses the saved operation.

EasyChat pauses background admin checks during this countdown so they cannot create new requests before files are replaced. Polling resumes automatically after installation, an error, or navigation away from the page. A legacy lock file is hardened in place only after EasyChat confirms that it is a regular, unused file and has not been replaced with a link.

When a One-Time Transition Is Required

Some Generic releases earlier than 1.12.0 cannot safely replace their own updater. EasyChat therefore does not keep retrying a phase that cannot succeed. Update Center shows Download transition package instead.

1. Download the package from that button or the official download page only.
2. Extract the easychat directory over the existing installation directory.
3. Do not delete the existing directory first, and do not replace its config.php, log, or uploads data with empty directories.
4. Open Update Center again and select Check.

Settings, conversations, uploads, and logs remain in place. Any interrupted operation is reconciled with the installed version and cannot publish its old prepared files. Later Generic updates return to the regular one-click flow.

EasyChat downloads and verifies the correct package while OpenCart performs the installation through its native workflow. On OpenCart 2.3 and 3, click Update through OpenCart and confirm: there is no package to download and upload again. OpenCart uses its configured FTP or Local Copy transport. OpenCart 4 currently receives the exact package and a direct path to the correct CMS section.

If EasyChat was opened directly or its OpenCart handoff has expired, Update Center shows a prominent How to continue through OpenCart button. Select it and follow the three short on-screen steps: return to the OpenCart admin, open the installed module, and enter EasyChat again. The action then becomes Update through OpenCart. This is not a background wait or an error; the fresh handoff grants the short-lived permission required by the native CMS installer. You do not need to sign out of EasyChat or open a private window: entering again from OpenCart refreshes the permission even when an EasyChat session is already active.

If the OpenCart 2.3 installer cannot move the files, EasyChat never reports a false success. The current version remains operational and safe manual options appear on screen. Do not install Local Copy from an unknown source solely for this update; verify your hosting permissions and configuration first.