Complete Guide to Enabling PHP 7 Module in Apache Server with Conflict Resolution

Problem Background and Phenomenon Analysis

In Ubuntu Wily system environment, when users attempt to execute the a2enmod php7.0 command to enable PHP 7.0 module, the system returns the message "Considering conflict php5 for php7.0", indicating that Apache has detected potential conflicts between PHP 5 and PHP 7 modules. Subsequently, after restarting the Apache service, the server fails to start normally, which is typically caused by module dependencies or configuration conflicts.

From a technical perspective, Apache's module system allows loading multiple modules simultaneously, but when multiple modules provide similar functionality or compete for resources, conflicts arise. Both PHP 5 and PHP 7 modules belong to PHP processing modules, responsible for parsing and executing PHP scripts, therefore they cannot be enabled concurrently. The conflict message displayed by the system is the normal response of Apache's module management mechanism when detecting such incompatibility.

Core Solution: Module Disabling and Enabling

To resolve PHP module conflicts, first disable the enabled PHP 5 module. This can be achieved using Apache's a2dismod command:

sudo a2dismod php5

After executing this command, the system removes the symbolic link for PHP 5 module and deletes it from the active module list. Next, enable the required PHP 7.0 module:

sudo a2enmod php7.0

This command creates a symbolic link for PHP 7.0 module in the /etc/apache2/mods-enabled directory, making it an active module for Apache. After completing the module switch, the Apache service must be restarted to apply the changes:

sudo service apache2 restart

Or using systemd systems:

sudo systemctl restart apache2

In-depth Understanding of Module Management Mechanism

Apache's module management system is based on symbolic link mechanism. The /etc/apache2/mods-available directory contains configuration files for all available modules, while the /etc/apache2/mods-enabled directory contains symbolic links pointing to these configuration files. Only modules with symbolic links in this directory will be loaded.

When executing a2enmod and a2dismod commands, the system is actually manipulating these symbolic links. This design makes module enabling and disabling simple and reversible, while avoiding risks associated with directly modifying configuration files.

Version Specification and Compatibility Considerations

In practical operations, ensure that the enabled PHP module version exactly matches the PHP version installed in the system. If multiple PHP 7.x versions are installed in the system (such as PHP 7.0, PHP 7.1, PHP 7.2, etc.), specific version numbers must be used:

sudo a2enmod php7.0  # Enable PHP 7.0 module
sudo a2enmod php7.1  # Enable PHP 7.1 module
sudo a2enmod php7.2  # Enable PHP 7.2 module

Incorrect version specification may cause modules to malfunction or produce unexpected behavior. The current PHP version used in CLI environment can be checked using the php -v command, but note that the PHP version used in web server may differ from the CLI environment.

Supplementary Solutions and Best Practices

In some complex environments, additional configuration steps may be necessary. For example, when using PHPMyAdmin or other PHP applications, MPM (Multi-Processing Module) settings may need adjustment:

sudo a2dismod mpm_event
sudo a2enmod mpm_prefork
sudo service apache2 restart

This is because the mpm_prefork module has better compatibility with PHP, especially when handling PHP applications that require state maintenance. Additionally, ensure all necessary PHP extensions are installed:

sudo apt install php7.0-mbstring php7.0-gd php7.0-mysql

These extensions provide basic functionalities such as string processing, graphic processing, and database connections, which are essential for normal operation of most PHP applications.

Troubleshooting and Verification

After completing configuration, verify whether PHP 7 module is functioning properly through the following steps:

1. Create a test PHP file (e.g., /var/www/html/info.php):

<?php
phpinfo();
?>

If the page fails to display normally or shows error messages, check Apache error log:

sudo tail -f /var/log/apache2/error.log

The log file typically contains detailed error information, helping diagnose the root cause of problems.

Environment Variables and Symbolic Link Handling

In some cases, even with correct Apache module configuration, PHP versions may still appear inconsistent. This could be due to multiple PHP versions in the system, with environment variables or symbolic links pointing to incorrect versions.

Check and update PHP symbolic links:

sudo update-alternatives --config php

This command allows users to choose among multiple installed PHP versions, ensuring the system uses the correct PHP version.

Summary and Recommendations

Enabling PHP 7 module in Apache is a relatively simple process, but requires careful handling of module conflicts and version compatibility issues. Key steps include: disabling conflicting PHP 5 module, enabling correct PHP 7 module, restarting Apache service, and verifying configuration results.

It is recommended to verify all configurations in a testing environment before making changes in production environment. Additionally, regularly update the system and software packages to ensure security and stability. For more complex multi-version PHP environments, consider using PHP-FPM and virtual host configurations to achieve more flexible PHP version management.