Keywords: PHP7 | ext-dom | Composer | Ubuntu | Laravel
Abstract: This article provides an in-depth analysis of the ext-dom extension missing issue encountered when installing Laravel packages on Ubuntu servers. By parsing Composer error messages, it identifies that phpunit/php-code-coverage depends on the ext-dom extension. The article details the method to install the php-xml package in Ubuntu 16.04 systems and explains the differences between local development and production environments. It also discusses the installation of related extensions like mbstring and best practices for avoiding running Composer as root.
Problem Background and Error Analysis
When running a Laravel 5.4 application on an Ubuntu 16.04 server, attempting to install the cviebrock/eloquent-sluggable package via Composer resulted in dependency resolution errors. The error message clearly states: phpunit/php-code-coverage 4.0.7 requires ext-dom * -> the requested PHP extension dom is missing from your system. This indicates that the DOM extension for PHP is missing from the system.
Environment Difference Analysis
The user mentioned that the package installs normally in the local environment but fails on the server. This discrepancy often stems from configuration differences between development and production environments. Local environments might use integrated solutions like XAMPP, which include a complete set of PHP extensions by default, while production servers typically have minimal installations requiring manual installation of necessary extensions.
Solution Implementation
First, the php-xml package needs to be installed, as it includes the DOM extension and other related XML processing functionalities. On Ubuntu systems, this can be done with the following commands:
sudo apt-get update
sudo apt install php-xmlAfter installation, it is advisable to check for and install other potentially missing extensions, such as mbstring:
sudo apt-get install php-mbstringSecurity Best Practices
Composer issued an important warning during execution: Do not run Composer as root/super user! Running Composer as root poses security risks, as it might accidentally modify system files. The correct approach is to run Composer commands with regular user privileges.
Verification and Follow-up Actions
After installing the required extensions, verify that they are correctly loaded. This can be done by running the php -m command to view the list of loaded modules, ensuring that dom and mbstring appear in the list. Then execute:
composer update
composer require cviebrock/eloquent-sluggableRelated Technical Extensions
Cases from reference articles show that similar DOM extension issues can occur in other PHP versions and operating systems. For instance, in FreeBSD systems, it might be necessary to enable DOM support by adding the --enable-dom parameter during compilation. This indicates that solutions may vary across environments, but the core issue remains the improper enabling of the DOM extension.
Preventive Measures
To avoid similar issues, it is recommended to check the PHP extension configuration of the production environment before deployment. Creating a deployment checklist can ensure all necessary extensions are installed. Additionally, maintaining consistent configurations between development and production environments can reduce the occurrence of such compatibility problems.