anchor.diff:  NOTICE: PHP message: PHP Warning:  example MUST be loaded as a Zend extension in Unknown on line 0
   ```
   
  -Try moving the `example` extension from `ZEND_EXTENSIONS` to `PHP_EXTENSIONS`, then re-pushing your application.
  +Try moving the `example` extension from `zend_extension` to `extension`, then re-pushing your application.
   
   ### <a id="php-modules"></a> PHP Modules
   
  
positive.code: Include conf/extra/httpd-my-special-config.conf # This line includes your additional file.
  ```
  
  ### <a id="php-extensions"></a> PHP Extensions
  
  PHP extensions are easily enabled by setting the `PHP_EXTENSIONS` or `ZEND_EXTENSIONS` option in `.bp-config/options.json`. Use these options to install bundled PHP extensions.
  
  If an extension is already present and enabled in the compiled php, for example `intl`, you do not need to explicitly enable it through `PHP_EXTENSIONS` or `ZEND_EXTENSIONS` in `.bp-config/options.json` to use that extension.
  
  #### PHP\_EXTENSIONS vs. ZEND\_EXTENSIONS
  
  PHP has two kinds of extensions, "PHP extensions" and "Zend extensions". These [hook into the PHP executable in different ways](https://wiki.php.net/internals/extensions).
  
  The buildpack cannot know, in advance, what kind of extension you are requesting. This is why there are two variables, and why your app will fail if you say a Zend Extension
  is a PHP Extension, or vice versa.
  
  If you see this error:
  
  
negative.code: 
  The buildpack automatically configures HTTPD, Nginx. and PHP for your application.  This section explains how to modify the configuration.
  
  The `.bp-config` directory in your application can contain configuration overrides for these components. Name the directories `httpd`, `nginx`, and `php` (although we suggest you use [php.ini.d](#php_ini_d) or [fpm.d](#fpm_d)).
  
  <p class='note'><strong>NOTE</strong>: If you override the php.ini or php-fpm.ini files many other forms of configuration will not work.</p>
  
  For example:
  ```
  