Upgrading from WISECP 3.x to 5.x
The 3.x to 5.x upgrade moves a WISECP 3.x installation to WISECP 5 in place, keeping your customers, services, invoices and settings.
Opening the Screen
The upgrade starts in the 3.x admin panel under Help → Updates. It needs 3.x release 3.1.9.8.3 or newer. On an older 3.x the Updates page offers that release first; the 5.0 line appears after you apply it. If the page moves on to the 5.0 line right after applying 3.1.9.8.3, it prepares the wizard. Open the link it shows to continue.
The card WISECP 5.0 is ready for this installation carries the button Start the 5.0 upgrade wizard. It opens upgrade.php in your installation root with a signed link that expires with the day.
How the Upgrade Runs
The wizard has two parts: a preparation screen that fetches the 5.x package, then the steps that carry out the upgrade. Nothing in your 3.x installation changes before the Upgrade step. To move to a new server at the same time, install 5.x there and use Import Tools instead.
Preparation
Three rows run on their own. The licence service names the 5.0 build you may install. The package is downloaded to your server and unpacked into _wisecp_v5_stage next to your installation. A failed row shows its reason and a Try again button. When all three pass, the wizard opens.
The Steps
| Step | What happens | What you do |
|---|---|---|
| Agreement | Shows the terms of service. | Tick the acceptance box, then click Continue. |
| Check | Checks the server, the database, the licence and free disk space, and rehearses the migration without changing anything. It appears only when something blocks the upgrade; each card shows what was detected and how to fix it. | Fix each card, then click Check Again. When nothing blocks, the wizard moves on to Confirm. |
| Confirm | Asks you to confirm the backup. | Tick the backup confirmation, then click Start the Upgrade. |
| Upgrade | Shows a progress bar with the current phase. The site is in maintenance mode until the health check passes. | Keep the page open. Nothing to click. |
| Finished | Confirms the site and the panel answer, then deletes the upgrade files. | Click Go to the Admin Panel and sign in as before. |
What Is Carried Over
Customers, services, orders, invoices, tickets, uploads, visitor statistics, and email and SMS logs stay where they are. Old messages that carried a secret, such as a verification code or a reset link, lose their content. A service set to Custom Price on 3.x keeps it and renews at its own amount. Settings, encryption keys, module settings, notification preferences and the admin folder name are carried into 5.x. Passwords keep working. An account whose password was kept in an older or imported format needs a new password: set it in the 3.x panel before the upgrade, or reset it from the sign-in page afterwards.
The logos you uploaded on 3.x (site, client area and email logos, and the favicon) are carried over; the default logos that came with 3.x are not, so 5.x shows its own. The colors your 3.x site showed move to Site Colors on the Logo/Branding tab. If they look pale, click Pick from logo there, then click Save Changes. Your contact address becomes the head office on the Contact page in place of the sample offices. The full-access administrator group receives the permissions 5.x added; a restricted group receives only the counterparts of those it had on 3.x.
Release 3.1.9.8.3 (Beta V23) or newer also carries three items. 3.x contract texts with real wording become contract pages, chosen in Contract Settings on the Contracts screen if it was empty. Easy Order turned off becomes Require verification before ordering turned on in Client Membership Settings. Automation tasks you turned off stay off, and Delete From Server waits for Confirm Settings on the Automation screen.
What Is Not Carried Over
Nothing on this list is deleted; it stays in the backup folder.
Before You Start
Tasks
Run the Upgrade
- Take the database backup and confirm it restores.
- In the 3.x panel open Help → Updates, apply 3.1.9.8.3 if it is offered, then click Start the 5.0 upgrade wizard.
- Let the preparation finish, tick the acceptance box and click Continue. If the Check step appears, fix each card and click Check Again.
- Tick the backup confirmation and click Start the Upgrade. The progress bar runs through to Upgrade Complete.
After the Upgrade
- Sign in to the 5.x panel with the same email and password as before.
- Update the cron job: the 5.x command differs from the 3.x one, and Settings → Cron Jobs shows it.
- Pick and configure a website theme, check the modules that had no 5.x counterpart, and review the notification templates.
- If the dashboard shows a price cycle notice, see Product Pricing.
Continue After an Interruption
- If the connection drops, open the page again: the upgrade resumes where it stopped.
- If a stage fails, a card and the log open under the progress bar. Fix the cause and click Retry; finished stages are not repeated.
If the Wizard Session Ends
- On the Your wizard session has ended notice, open the wizard again from the Updates page of the 3.x panel. If the 3.x panel no longer opens, use the link you first opened, the one containing key=. The upgrade resumes where it stopped.
- If PHP Cannot Start a Session appears, correct the session folder it shows or the PHP version in your hosting panel. Open the link again and the wizard opens.
Go Back to 3.x
- Move the 5.x entries out of the root and put the contents of the backup folder back. The folder holds a notes file with the exact steps.
- Move uploads and visitor statistics back from the 5.x tree.
- Restore the full database backup you took before the upgrade. The site answers as 3.x again.
Things to Watch
The migration renames tables, converts every MyISAM table to InnoDB and writes values that 3.x cannot read. The files can be put back in a minute; the database only from your backup.
Keep the 3.x backup folder and the database backup for at least 72 hours. Data created in 5.x after the upgrade cannot be carried back to 3.x.
The Check step shows this when the same key is registered to another address, and the upgrade does not start. Ask support to reissue the licence for this address, then click Check Again.
An AddHandler line you wrote into .htaccess is not carried over, and the upgrade does not start while it is there. Choose the PHP version in the MultiPHP section of your hosting panel or remove the line, then click Check Again.
Related Articles
Дякуємо за відгук!
Наша служба підтримки на зв’язку цілодобово з усього, чого ви не знайшли вище.