Xgenious/ docs
Products
Get support

How to Download Manual Update File

This guide explains how to download and install manual update files for your Xgenious products. Manual updates are useful when automatic updates are not available or when you need to update multiple installations.

Danger

If you have made any custom changes to the core system files, do not run this update. The update will overwrite the core files and permanently remove all of your custom changes. Contact support before updating if you have core-level customizations you need to keep.

Tip

Don't have any core customizations? Use One Click Update instead — it's faster and updates your script automatically from the admin panel.

When to Use Manual Update

  • Automatic updater is not working
  • You are behind several versions
  • You need to apply a patch or hotfix
  • Your server does not support outbound connections
  • You want to control the update timing

Prerequisites

  • Active purchase code for the product
  • FTP or cPanel access to your server
  • A backup of your current installation (strongly recommended)

Step 1: Download the Update File

  1. Visit xgenious.com and login to your account
  2. Navigate to My Account > Downloads
  3. Find your product in the downloads list
  4. Click the Download button to get the latest version
  5. Save the ZIP file to your computer
Tip

Having trouble downloading the update file? Open a support ticket and our team will share the file with you via Google Drive.

Step 2: Backup Your Current Installation

Before applying any update, create a full backup:

Files: Download all product files via FTP Database: Export your database using phpMyAdmin or mysqldump Configuration: Save any custom configuration files

Step 3: Extract the Update Files

  1. Locate the downloaded ZIP file on your computer
  2. Extract the contents to a folder

Step 4: Upload via FTP

  1. Connect to your server using an FTP client (FileZilla, Cyberduck, etc.)
  2. Navigate to your product installation directory
  3. Upload the extracted files, overwriting existing files when prompted
  4. Ensure all files upload successfully (check for errors)

Step 5: Run the Update Script

Some products require running an update script:

  1. Navigate to your site URL in a web browser
  2. If an update script is required, you will be redirected to yourdomain.com/update
  3. Follow the on-screen instructions
  4. The update script will migrate your database and apply necessary changes

Alternative: Manually Replace Files (If the Update Script Fails)

If visiting yourdomain.com/update fails to load, gets stuck, or throws an error, you can skip the update script entirely and replace the project files by hand.

Danger

Take a full backup of your files and database before touching anything. Manual file replacement overwrites your live project directly — if a step goes wrong partway through, a backup is the only way to recover. Do not proceed without one.

In your live project, _build/, ajax.php, assets/, and index.php sit outside your core/@core directory, while the rest live inside core/@core. The extracted update package does not have this split — it is flat, with all folders sitting together at a single level. Match each entry in the update package to its correct location in your live project and go through them one by one, replacing the old version with the new one.

Your Project Root                            Update Package (extracted ZIP)
├── _build/          (outside core/@core)    ├── _build/
├── ajax.php         (never copy or remove)  ├── ajax.php      (never copy)
├── assets/          (outside core/@core)    ├── assets/
│   └── uploads/     (never replace)         ├── app/
├── index.php        (never copy or remove)  ├── config/
└── core/ (or @core/)                        ├── custom/
    ├── app/                                 ├── database/
    ├── config/                              ├── index.php     (never copy)
    ├── custom/                              ├── Modules/
    ├── database/                            ├── plugins/
    ├── Modules/                             ├── public/
    ├── plugins/                             ├── resources/   (contains lang/)
    ├── public/                              ├── routes/
    ├── resources/   (contains lang/)        └── vendor/
    ├── routes/
    └── vendor/
  1. Extract the update ZIP file (see Step 3) — you will get one flat folder containing all the items shown above, with no core/@core wrapper
  2. Open your live project and the extracted update folder side by side
  3. From the update package, take _build/ and replace its counterpart at your project root — not inside core/@core
  4. From the update package, take app, config, custom, database, Modules, plugins, public, resources, routes, and vendor and replace their counterparts inside your core/@core directory
  5. Repeat until every folder from the update package has replaced its counterpart in your live project
Danger

Never copy or replace ajax.php or index.php from the update package, in any case. Your live project's ajax.php and index.php at the project root must stay untouched — do not overwrite them with the versions from the extracted update folder.

Danger

Do not replace or delete the assets/ folder as a whole. Open it and replace its contents one by one, the same as the other folders — and never remove or overwrite the assets/uploads/ folder. It holds user-uploaded files (images, media, etc.) that are not part of the update package and cannot be recovered if deleted.

Warning

The resources/lang folder holds your translation files. If you have custom or edited translations, back up resources/lang separately before you replace the resources folder, then restore your backed-up language files once the update is complete — otherwise your custom translations will be overwritten by the defaults shipped in the update.

Run the Database Upgrade

Danger

This step is required. Replacing the files alone does not update your database — skipping it will leave your site on the old database schema and can break the update.

You can run the database update either from the admin panel or from the terminal.

Option 1: From the Admin Panel

  1. Log in to your admin panel
  2. Go to General Settings > Database Upgrade
  3. Run the database update and wait for it to finish

Option 2: From the Terminal

  1. Log in to your server via terminal (SSH)
  2. Navigate into your core/@core folder
  3. Run:
php artisan migrate

Clear the Cache

Once the database update has finished, clear the cache so the update takes effect. You can do this manually or from the terminal.

Option 1: Delete the Cache Files Manually

Clear each of the following folders inside core/@core:

  1. bootstrap > cache — delete all files inside this cache folder
  2. storage > logs — delete all files inside this logs folder
  3. storage > framework > cache — delete all files inside this cache folder (app/framework cache)

Option 2: From the Terminal

  1. Log in to your server via terminal (SSH)
  2. Navigate into your core/@core folder
  3. Run:
php artisan optimize:clear

Step 6: Verify the Update

After completing the update:

  1. Visit your site frontend and confirm it loads correctly
  2. Check the admin panel and verify all sections work
  3. Go to the dashboard and confirm the version number has changed
  4. Test key functionality to ensure nothing is broken

Troubleshooting

White screen after update

Clear your browser cache and check for PHP errors in your server error log. If the issue persists:

  • Verify all files were uploaded correctly
  • Check PHP version compatibility
  • Restore from backup and try the update again

Database errors after update

Run the update script again. If errors persist:

  • Check that your database user has ALTER and CREATE permissions
  • Verify the database is using a supported MySQL/MariaDB version
  • Contact support with the specific error message

Update script not running

Manually trigger the update by visiting yourdomain.com/update.php or check the product documentation for the specific update URL.

Still stuck?
Our support team is ready to help you get set up.
Get support