Applies to: Saleculator POS/PDA 4.5 update 4 (4.5.4), Webin 3.7 and Waiter 1.3.0, as relevant to this guide. Download the published packages from Saleculator Downloads.
Update Webin while preserving your database connection, customized files and waiter recovery information. A Webin code update is not a database reset.
Prepare the update #
- Read the release notes on Downloads and confirm compatibility with the installed POS/PDA and waiter app.
- Choose a quiet period. Finish active work or record the state of outstanding bill requests and uncertain printer attempts. Keep the phones containing unbacked-up work available.
- Back up the Saleculator database, the existing Webin folder, its configuration and its private waiter recovery storage as one coordinated backup.
- Record the current Webin address, database settings, private state/session paths and any web-server environment overrides. Preserve customized resources in the database.
Replace the application files #
- Download and extract the new Webin ZIP to a separate staging folder.
- Preserve your existing
application/config/config.phpanddatabase.phpsettings. The new ZIP contains actual local-default configuration files, so extracting over the old folder can overwrite your connection settings. - Apply the existing installation values to the new configuration, or retain equivalent environment overrides. Keep the same recovery directory with
SALECULATOR_WAITER_STATE_DIR; an empty replacement directory cannot recover existing requests. - Replace only the Webin application’s files, or switch your site’s document root/release symlink to the prepared folder. Retain the previous version for rollback.
- Check file permissions and restart/reload the appropriate web/PHP service if required by your server.
Do not delete /var/www or your entire htdocs directory. They may contain other websites and data. Webin 3.7 does not require a database migration for this release; do not execute historical SQL or reset user passwords as part of the code update.
Verify before resuming service #
- Webin sign-in and the dashboard load with their CSS and images.
- The waiter connection check recognizes Webin and the database.
- Existing tables and pending work are visible to the correct staff/device.
- Bill and KOT layouts refresh without discarding customized resources.
- A controlled test order reaches the cashier once, and the cashier can complete the intended workflow.
If the update fails #
Keep staff from creating conflicting work while the problem is investigated. Restore the previous Webin code and its installation settings. Preserve the database and recovery state together; do not restore an old database snapshot after new transactions without a coordinated recovery plan. Check private PHP/web-server logs rather than exposing database errors to browsers.
Earlier versions of this article contained appliance-specific Lighttpd commands and default dashboard XML. Keep appliance-specific changes and customized dashboard resources under technician control; they are not universal upgrade steps.
