PHP-Extensions Manual Enabling

Attention! Knowledge of how to administer *nix systems is required for operations described in this section. Please, create a full Virtual appliance system backup before performing operations described below.

In addition to enabling specific PHP-extensions from the BitrixEnv menu, the required extensions can be connected manually.

Configuration ini-files for the available php-extensions are located in the directory /etc/php.d/:

To manually enable a required extension, the file {name_extension}.ini.disabled must be renamed to {name_extension}.ini and the Apache service must be re-launched – httpd.

For example, extension dom must be enabled.

Go to server directory /etc/php.d/:
```
cd /etc/php.d/
```
Print list of files in the directory:
```
ls
```
Find the file 20-dom.ini.disabled in the list, rename it for 20-dom.ini, save and replace the current file:
```
mv 20-dom.ini.disabled 20-dom.ini
```
Attention! If the content of 20-dom.ini.disabled is copied into 20-dom.ini and those two files are kept in the directory /etc/php.d/, then the dom-extension will deactivated when the PHP or Virtual Appliance are updated. To avoid this, only one file 20-dom.ini must be kept with the active extension.

Re-launch the Apache service – httpd:

CentOS 6:
```
service httpd restart
```
CentOS 7:
```
systemctl restart httpd.service
```

The procedure is completed, extension is dom operational:

Bitrix Virtual Appliance