Server and PHP requirements for legacy Fusion

Archived guide for existing Fusion Owned License installations; use the instructions for your installed build.

Historical server requirements

The archived **System Requirements** article records the following environment. These values describe that source's legacy baseline; they are not a statement that these old runtimes are currently secure or that every later major release is compatible.

| Component | Requirement recorded in the archive |

| --- | --- |

| Operating system | Linux; CentOS was recommended in the original article |

| Database | MariaDB 10.1 or later; the article specifies strict mode disabled |

| Web server | Apache 2.4 or later, with GET, POST, PUT and DELETE support |

| Friendly links | `.htaccess` support |

| PHP | 7.4 or later, as recorded in this requirements article |

| ionCube Loader | Version 13 or later, as recorded in this requirements article |

| API processing | A scheduled job every minute |

| Hosting panel | cPanel was recommended |

| PHP `memory_limit` | Suggested 256M |

| PHP `max_execution_time` | Suggested 300 seconds |

The historical strict-mode setting belongs to the documented application/database combination. Confirm the actual build requirement before changing a database server's SQL mode; do not apply a server-wide change to unrelated applications.

Required PHP modules

The legacy installer checks `curl`, `mbstring`, `date`, `libxml`, `openssl`, `pcre`, `zlib`, `filter`, `hash`, `session`, `ctype`, `dom`, `gd`, `iconv`, `json`, `PDO`, `SimpleXML`, `xml`, `xmlwriter`, `zip`, `mysqli` and `pdo_mysql`.

The old requirements page labels database connectivity as `MySQL`; the reviewed PHP 7 installer checks `mysqli` and `pdo_mysql`. Its separate extension-version annotations are inconsistent, so use the installer check and the release package rather than treating those annotations as extension minimums.

After a PHP switch, check the website's PHP version, ionCube Loader and extensions together. A cron job that requests the site over HTTPS uses the website's PHP configuration. A job that launches PHP directly may use a different CLI binary and set of extensions; verify both runtimes if that is how your installation runs its scheduled jobs.

Compare with the exact update package

The separate historical update guide names PHP 7.2 and ionCube 10.2. It does not identify which build that note covers, so it cannot replace the requirements for every installation. Record the installed Fusion build, intended target build, PHP version, ionCube Loader version and database version before changing the environment.

Use the package's README and a restored test copy to establish compatibility. For a loader or missing-module error, include the component versions and exact error, not a public configuration dump.