Update from Version 2.6 to 2.7
A list of updates for the script version 2.7 is available at this link.
Before starting the script update, please update the Ioncube Loader on your server to version 14.0 or higher (if your current version is below 14 — refer to the instructions for checking the installed version** and the update instructions). Your hosting provider's technical support can assist you with the update.
If you are using merchant and auto-payment modules developed specifically for you, please request updated modules in your Telegram group (not through technical support via the bot).
If you are using merchant and auto-payment modules, as well as other types of modules from third-party developers, they will not work on version 2.7 without updates from the developers.
If you used the Electrum modules and/or "Trading Actions" in version 2.6, please request the modules for version 2.7 in your Telegram group (not through technical support via the bot).
Please note — when updating the script from version 2.6 to 2.7, a free update is required for those with a custom design developed by us for the site!
If you are using such a design, please send an archive of the theme for adaptation to version 2.7.
To do this, navigate to the folder on your server at www/<site_name>/wp-content/themes/, find the folder with your theme, compress it into an archive, download it to your computer, and then send the archive to your Telegram group.
Before updating, make sure to back up your website and database!
If something goes wrong during the update, you can always restore your site from the backup. Backup methods may vary depending on your hosting, so it's advisable to contact your hosting provider's technical support for assistance.
The simplest way to back up your site is through the server control panel (ISP Manager or other software) using the built-in file manager or via an FTP client (download the site files to your computer, and also download the site's database from the database management section or through PhpMyAdmin).
Update Process
In the exchange panel, go to the "Console" section and enable technical mode to prevent users from making requests on the site during the script update.
In the "Plugins" section, deactivate the "Premium Exchanger" and "Premium Exchanger hooks" plugins.\
Using an FTP client or file manager, delete the contents of the
/wp-content/plugins/premiumbox/folder on the server, except for the following files and folders inside it:
/flags//languages//moduls/(but first, read the text in the block below)
/sms//userdata.php
Delete all files from the previous license in the root folder of your site.\
Go to the "Your Licenses" section and download the archive with the license files license.zip. To do this, click on the "Download for version 2.7" link.\
Upload the downloaded archive to the root folder of your site using the user created for the site (not root!) and make sure to extract the archive.
Make sure to complete step 4, even if the license files were previously uploaded to the server — otherwise, the site will not function!
Go to the "Your Scripts" section and download the archive with update files for version 2.7 that matches your PHP version.
You need to know the exact PHP version installed on your server to select the appropriate archive. Instructions for checking the PHP version installed on the server.
Upload the contents of the update archive to the root folder of your site using the user created for the site (not root!). Use an FTP client or file manager. Extract the archive, replacing the files.
Go to the "Plugins" section and activate the "Premium Exchanger" and "Premium Exchanger hooks" plugins.
Go to the "Exchange Settings → "Migration"** section and sequentially complete each step in the "Migration (if version is less than 2.7)" block.
If you used AML modules in version 2.6 — you need to enable the AML module in the "Modules" section after updating the script and before performing the migration for the correct transfer of settings from version 2.6.
The same applies if you used coefficients (in the "Parsers 2.0" section ➔ "Custom Coefficients") — if you used coefficients in version 2.6, you need to enable the module of the same name in the "Modules" section after updating the script and before performing the migration for the correct transfer of coefficients from version 2.6.
When you start each step, the system will determine the total number of requests that need to be executed. You can specify the number of requests to be processed in one cycle.
By default, the number of requests = 50. If you are unsure about your server's capacity, we recommend not changing the default value.
If necessary, you can specify any other value, but if the execution cycle with the specified value is too resource-intensive for the server, it will cause an error.
Go to the "Settings → "Permalinks"** section and click the "Save Changes" button without making any changes on the page.\
Go to the "Requests" section and disable the update mode.\
The update mode is activated each time the main plugin is deactivated and reactivated, so it must always be manually disabled.
If you are using the "Parsers 2.0" or "Bestchange Parser" modules — after disabling the update mode, you need to start the parsers in the corresponding sections by manually following the Cron link. For the operation of Parsers 2.0:
For the operation of the BestChange parser:
Make sure to delete all uploaded zip archives of the script and site backups from the root folder on the server.\
Disable maintenance mode in the "Console" section.
Update completed successfully!
Last updated