Install or move an existing site
Archived guide for existing Fusion Owned License installations; use the instructions for your installed build.
Install the package for your existing licence
Back up the database, site files, templates and language customizations. Confirm the package's build requirements before starting.
1. Extract the package ZIP to a local folder.
2. Upload its contents to the intended installation directory. The historical guide recommends binary transfer mode if file transfers are corrupted.
3. Open `https://your-site.example/installer/`, replacing the example with your actual HTTPS address and installation subdirectory.
4. Follow the installer screens and grant only the file access required by the web process. Do not make directories writable by everyone.
5. Delete the installer directory after installation completes.
6. Open the installed admin area's `setup.php` page; the original path is `/admin/setup.php`. Complete the basic site settings.
7. If using a custom admin-directory name, keep the physical directory and the package's configured admin path consistent.
8. Enable the package's Apache rewrite rules and check a friendly URL before opening the site to customers.
Configuration and friendly URLs
The reviewed older installer uses `configs/config.php` and `$admindirpath` for the configured admin directory. Keep that value consistent with the physical directory name. Some builds use a different admin-path setting, such as `$customadminpath`; edit the existing setting supplied with your build rather than adding both.
For Apache friendly URLs, check the rewrite file shipped in the package. When it is supplied as `_htaccess`, enable it as `.htaccess`, preserving any existing custom rules. Check a friendly URL after the change. Do not create a second configuration file because an old instruction names a different file.
Move the installation to another host
1. Back up the old database and transfer the site's files to the new host.
2. Restore the database on the new host, for example using phpMyAdmin, and update the database connection in the package's actual configuration file. Use the file shipped with your build.
3. If the domain, IP address or installation directory changes, review the licence's registered installation details and any required reissue before the final switch.
4. Sign in to the restored admin area and update the site URLs under **Setup/Settings > General Settings**.
5. Update the scheduled jobs, gateway callback addresses and email forwarding that refer to the old host.
6. Check the site, ordering, callbacks and mail on the new host, then remove the old installation and its scheduled jobs when the move is complete.
Avoid having both copies process the same live jobs or callbacks during the switch.