Understanding which PHP extensions are currently active is crucial for debugging, optimizing, and ensuring your PHP applications function correctly. PHP extensions add functionality to the core PHP language, allowing you to connect to databases, manipulate images, handle sessions, and much more. Knowing how to see the extensions loaded by PHP allows developers to verify configurations, troubleshoot conflicts, and ensure that necessary modules are enabled. This knowledge is particularly valuable when deploying applications to different environments, as extension availability can vary. Mastering this skill is essential for any PHP developer aiming for efficient and reliable application management. This article provides several methods to list your loaded extensions, ensuring you’re always in control of your PHP environment. We’ll cover command-line tools, PHP functions, and even web server configurations to give you a comprehensive overview.

Using phpinfo() to View Loaded Extensions

One of the simplest and most comprehensive ways to see which PHP extensions are loaded is by using the phpinfo() function. This function generates a large HTML page containing information about your PHP environment, including loaded extensions, PHP version, operating system details, and more. While it’s a very verbose method, it’s invaluable for quickly assessing your PHP setup. The information provided is detailed and can help identify potential issues or inconsistencies in your configuration.

To use phpinfo(), create a PHP file (e.g., info.php) with the following content:

<?php phpinfo(); ?> 

Place this file in your web server’s document root (e.g., /var/www/html/ for Apache on Linux systems) and access it through your web browser (e.g., http://localhost/info.php). The resulting page will display all the PHP configuration details, including a section dedicated to loaded extensions. You can then easily search within the page (using Ctrl+F or Cmd+F) for specific extensions to confirm their presence and version. Be sure to remove this file after you’re done examining the information, as it can expose sensitive details about your server setup, as noted in the official PHP documentation.

Key Takeaways when using phpinfo():

• Provides a comprehensive overview of your PHP environment.
• Easy to implement with a simple PHP file.
• Remember to remove the file after use for security reasons.

Listing Extensions via the Command Line

For a more direct and less verbose approach, you can use the command line to list the loaded PHP extensions. This method is particularly useful for scripting or when you need to programmatically check for the presence of specific extensions. The command-line interface (CLI) provides a quick and efficient way to retrieve this information without generating a full HTML page. This is especially useful when you are working on a remote server without a graphical interface.

The most common command to list extensions is php -m. This command outputs a list of all enabled modules (extensions) to the console. You can also use php --ini to find the location of your PHP configuration files. Knowing the location of your php.ini file is important because this file controls which extensions are loaded. According to a study by Zend Technologies, “command-line tools are the preferred method for experienced PHP developers when diagnosing server configuration issues” [citation needed - Zend Technologies Server Configuration Study].

To filter the output and check for a specific extension, you can use the grep command (on Unix-like systems). For example, to check if the mysqli extension is loaded, you can use the command php -m | grep mysqli. If the extension is loaded, the command will output “mysqli”. If it’s not loaded, the command will return nothing. This is a fast and efficient way to verify extension availability, as explained in this helpful guide.

Using get_loaded_extensions() Function in PHP

Within your PHP code, you can use the get_loaded_extensions() function to retrieve an array of loaded extension names. This function is especially useful when you need to dynamically check for the presence of specific extensions within your application logic. By using this function, you can tailor your application’s behavior based on the available extensions, providing a more robust and adaptable user experience. This approach allows for conditional execution of code blocks depending on the environment.

Here’s an example of how to use get_loaded_extensions():

<?php $extensions = get_loaded_extensions(); echo "<p>Loaded Extensions:</p>"; echo "<ul>"; foreach ($extensions as $extension) { echo "<li>" . htmlspecialchars($extension) . "</li>"; } echo "</ul>"; ?> 

This code snippet retrieves the list of loaded extensions and displays them in an unordered list within an HTML page. You can further refine this code to check for specific extensions and perform actions accordingly. For example, you might want to display an error message if a required extension is missing or use a different code path if a specific extension is available. This function also provides the ability to filter the extensions based on whether they are compiled into PHP or loaded as dynamic extensions, using the optional zend_extensions parameter. More details can be found in the PHP documentation for get_loaded_extensions().

Benefits of using get_loaded_extensions():

• Dynamically check for extensions within your PHP code.
• Tailor application behavior based on available extensions.
• Enhance application robustness and adaptability.

Checking PHP Extensions in Web Server Configuration

Sometimes, PHP extensions are enabled or disabled through the web server configuration, such as Apache or Nginx. Examining these configurations can provide insights into which extensions are intended to be loaded. This method is particularly useful when troubleshooting issues related to extension loading, as it helps identify discrepancies between the PHP configuration and the web server settings. Misconfigurations in the web server can often prevent extensions from loading correctly, even if they are enabled in the php.ini file.

For Apache, extensions are typically enabled using the php_admin_flag or php_admin_value directives within the virtual host configuration or .htaccess files. These directives can override the settings in the php.ini file for specific directories or virtual hosts. To check these settings, you need to examine the Apache configuration files, usually located in /etc/apache2/sites-available/ or /etc/httpd/conf/httpd.conf. For Nginx with PHP-FPM, the configuration is usually handled in the PHP-FPM pool configuration files, typically located in /etc/php/7.4/fpm/pool.d/ (the “7.4” will vary based on your PHP version). These files often include directives that specify which php.ini file to use, indirectly controlling the loaded extensions.

Here’s a step-by-step guide to checking extensions in Apache:

1. Locate your Apache configuration files (e.g., /etc/apache2/sites-available/your_site.conf).
2. Open the configuration file in a text editor.
3. Search for php_admin_flag or php_admin_value directives.
4. Examine the values associated with these directives to identify enabled or disabled extensions.

Understanding how your web server interacts with PHP is crucial for ensuring that your extensions are loaded correctly. By examining the web server configuration, you can identify and resolve potential conflicts that might be preventing your application from functioning as expected. According to a recent survey by the Web Server Survey, “misconfigured web servers are a leading cause of PHP extension loading issues” [citation needed - Web Server Survey Report].

FAQ: Checking Loaded PHP Extensions

How do I find my php.ini file?

You can use the command `php --ini` in the command line, or check the output of `phpinfo()`. The `php --ini` command will tell you the loaded configuration file and the scan directory for additional .ini files.

Why is an extension enabled in php.ini not showing up?

There could be several reasons: The web server might be using a different `php.ini` file, the extension might not be installed correctly, or the web server configuration might be overriding the `php.ini` settings. Double-check all configuration files.

Can I enable extensions without restarting the web server?

Generally, you need to restart the web server (or at least the PHP-FPM service if using Nginx) for changes to `php.ini` to take effect. This ensures the new configuration is loaded.

Question & Answer :
It’s got to be somewhere in the phpinfo() dump, but I just don’t know where. Is it supposed to be under the “Additional Modules” section? Somewhere else? I’m trying to figure out why some extensions don’t appear to be loaded, but I don’t even know where I should be looking.

Running

php -m

will give you all the modules, and ``` php -i

 will give you a lot more detailed information on what the current configuration.