PHP-Extensions Manual Enabling

&lt;p&gt;&lt;div class=&quot;warning&quot;&gt;&lt;b&gt;Attention!&lt;/b&gt; Knowledge of how to administer *nix systems is required for operations described in this section. Please, create a full &lt;I&gt;Virtual appliance&lt;/I&gt; system backup before performing operations described below.&lt;/div&gt;&lt;/p&gt; &lt;br&gt; &lt;p&gt;In addition to &lt;a href=&quot;/support/training/course/index.php?COURSE_ID=113&LESSON_ID=9619&quot; target=&quot;_blank&quot;&gt;enabling specific PHP-extensions from the BitrixEnv menu&lt;/a&gt;, the required extensions can be connected &lt;b&gt;manually&lt;/b&gt;. &lt;/p&gt; &lt;p&gt;Configuration ini-files for the available php-extensions are located in the directory &lt;code&gt;/etc/php.d/&lt;/code&gt;:&lt;/p&gt; &lt;p&gt;&lt;img src=&quot;/images/portal_admin_en/php_ext1_en.png&quot; /&gt;&lt;/p&gt; &lt;p&gt;To manually enable a required extension, the file &lt;b&gt;{name_extension}.ini.disabled&lt;/b&gt; must be renamed to &lt;b&gt;{name_extension}.ini&lt;/b&gt; and the Apache service must be re-launched – &lt;b&gt;httpd&lt;/b&gt;. &lt;/p&gt; &lt;br&gt; &lt;br&gt; &lt;p&gt;For example, extension &lt;b&gt;dom&lt;/b&gt; must be enabled.&lt;/p&gt; &lt;ol&gt; &lt;li&gt;&lt;p&gt;Go to server directory &lt;code&gt;/etc/php.d/&lt;/code&gt;:&lt;/p&gt; &lt;pre class=&quot;syntax&quot;&gt; cd /etc/php.d/ &lt;/pre&gt; &lt;/li&gt; &lt;li&gt;&lt;p&gt;Print list of files in the directory:&lt;/p&gt; &lt;pre class=&quot;syntax&quot;&gt; ls &lt;/pre&gt; &lt;/li&gt; &lt;li&gt;&lt;p&gt;Find the file &lt;b&gt;20-dom.ini.disabled&lt;/b&gt; in the list, rename it for &lt;b&gt;20-dom.ini&lt;/b&gt;, save and replace the current file: &lt;/p&gt; &lt;pre class=&quot;syntax&quot;&gt; mv 20-dom.ini.disabled 20-dom.ini &lt;/pre&gt; &lt;p&gt;&lt;div class=&quot;warning&quot;&gt;&lt;b&gt;Attention!&lt;/b&gt; If the content of &lt;b&gt;20-dom.ini.disabled&lt;/b&gt; is copied into &lt;b&gt;20-dom.ini&lt;/b&gt; and those two files are kept in the directory &lt;code&gt;/etc/php.d/&lt;/code&gt;, then the dom-extension will deactivated when the PHP or Virtual Appliance are updated. To avoid this, only one file &lt;b&gt;20-dom.ini&lt;/b&gt; must be kept with the active extension.&lt;/div&gt;&lt;/p&gt; &lt;/li&gt; &lt;li&gt;&lt;p&gt;Re-launch the Apache service – &lt;b&gt;httpd&lt;/b&gt;: &lt;/p&gt; &lt;ul&gt; &lt;li&gt;&lt;p&gt;&lt;b&gt;CentOS 6&lt;/b&gt;:&lt;/p&gt; &lt;pre class=&quot;syntax&quot;&gt; service httpd restart &lt;/pre&gt; &lt;/li&gt; &lt;li&gt;&lt;p&gt;&lt;b&gt;CentOS 7&lt;/b&gt;:&lt;/p&gt; &lt;pre class=&quot;syntax&quot;&gt; systemctl restart httpd.service &lt;/pre&gt; &lt;/li&gt; &lt;/ul&gt; &lt;li&gt;&lt;p&gt;The procedure is completed, extension is &lt;b&gt;dom&lt;/b&gt; operational:&lt;/p&gt; &lt;p&gt;&lt;img src=&quot;/images/bitrixvm/vmbitrix7/other_options/php_ext2_sm.png&quot; /&gt;&lt;/p&gt; &lt;/li&gt; &lt;/ol&gt; &lt;br&gt;&lt;br&gt;

Bitrix Virtual Appliance