Here are examples of what can be done with PHP Manager command line tools:

• Register a new PHP version:

PS C:\Users\Administrator>New-PHPVersion -ScriptProcessor "C:\PHP\536\php-cgi.exe"

• Get information about current PHP configuration:

PS C:\Users\Administrator> Get-PHPConfiguration

HandlerName              : php-5.3.6
Version                  : 5.3.6
ScriptProcessor          : C:\php\536\php-cgi.exe
HandlerType              : Local
ErrorLog                 : C:\Windows\Temp\php-5.3.6_errors.log
PHPIniFilePath           : C:\php\536\php.ini
InstalledExtensionsCount : 35
EnabledExtensionsCount   : 9

• Change PHP version for a particular web site or a folder:

PS C:\Users\Administrator> Set-PHPVersion -HandlerName php-5.3.6 -SiteName "Default Web Site"
PS C:\Users\Administrator> Get-PHPVersion -SiteName "Default Web Site"

HandlerName      Version      ScriptProcessor             Active
------------     -------      ---------------             ------
php-5.3.6        5.3.6        C:\php\536\php-cgi.exe      True
php-5.2.17       5.2.17       C:\php\5217\php-cgi.exe     False

• Change PHP settings:

PS C:\Users\Administrator> Set-PHPSetting -Name display_errors -Value On
PS C:\Users\Administrator> Get-PHPSetting -Name *error*

Name                         Value                               Section
----                         -----                               -------
error_reporting              E_ALL                               PHP
display_errors               On                                  PHP
display_startup_errors       Off                                 PHP
log_errors                   On                                  PHP
log_errors_max_len           1024                                PHP
ignore_repeated_errors       Off                                 PHP
track_errors                 Off                                 PHP
html_errors                  Off                                 PHP
mssql.min_error_severity     10                                  MSSQL
error_log                    C:\Windows\temp\php53_errors.log    WebPIChanges

• Enable PHP extensions:

PS C:\Users\Administrator> Get-PHPExtension -Name *pdo*sql* | Set-PHPExtension -Status enabled
PS C:\Users\Administrator> Get-PHPExtension -Name *pdo*sql*

Name                                 Status
----                                 ------
php_pdo_mysql.dll                    Enabled
php_pdo_sqlite.dll                   Enabled
php_pdo_sqlsrv.dll                   Enabled
php_pdo_pgsql.dll                    Enabled

Note that the example above demonstrates that it is possible to pipe several commands together. In this particular example the commands are used to enable all PHP extensions that contain “pdo” and “sql” in their names.

• Get detailed help for commands and their usage examples:

PS C:\Users\Administrator> get-help Get-PHPExtension

NAME
Get-PHPExtension

SYNOPSIS
Gets the list of PHP extensions available in the currently active PHP version.

SYNTAX
Get-PHPExtension [[-Name] <String>] [[-Status] <PHPExtensionStatus>]
[-SiteName <String>] [-VirtualPath <String>] [<CommonParameters>]

DESCRIPTION
The Get-PHPExtension cmdlet outputs the list of all PHP extensions available
in the currently active PHP version. The list can be filtered by extension
name and by the status (enabled or disabled).

RELATED LINKS
Set-PHPExtension

REMARKS
To see the examples, type: "get-help Get-PHPExtension -examples".
For more information, type: "get-help Get-PHPExtension -detailed".
For technical information, type: "get-help Get-PHPExtension -full".

Also, refer to the PHP Manager Documentation to get more information and usage examples.

Other improvements in the v1.2 include French translation (thanks to Emmanuel Boersma and Sylvain Lecerf) and several bug fixes.

Use Web Platform Installer to get the latest release of PHP Manager for IIS.

The new build of WinCache with the fix for this problem is available now at the following location:

https://sourceforge.net/projects/wincache/files/development/

The latest dev build at that location is a release candidate build. Several customers have already verified that this build fixes the problem and is running stable in their environments. Please try it out and let me know if it works or does not work for you. The things to try and to look for are:

1. Try to auto-upgrade any of the WordPress plugins;
2. After installing this build check the Windows Application event log from time to time looking for errors caused by module “php_wincache.dll”.

If you see any errors while using this build please let me know by leaving a comment here or in WinCache forum or by opening a bug in PECL bug database.

• German – the translation is provided by Christian Graefe
• Dutch – the translation is provided by Harrie Verveer
• Turkish – the translation is provided by Yusuf Oztürk
• Japanese – the translation is provided by Kenichi Wakasa
• Russian – the translation is provided by Ruslan Yakushev

Thanks to above mentioned people for providing these high quality translations! The PHP Manager Project is still looking for volunteers who can help with Spanish, French and Chinese translations.

Note that this release still includes English and it is recommended to upgrade even if you do not need these translations.

Use Web Platform Installer to get the latest release of PHP Manager for IIS (make sure to upgrade to the latest build of Web Platform Installer to get this release of PHP Manager).

Step 1: Enable PHP in WebMatrix from the site “Settings” page:

Note that if you installed any of the PHP applications from the Application Gallery then PHP will be automatically enabled.

Step 2: Download the appropriate build of Xdebug extension from downloads page. If your site uses PHP 5.2 then download “5.2 VC6 Non-thread safe (32 bit)”. If your site uses PHP 5.3 then download “5.3 VC9 Non-thread safe (32 bit)”. Use 32 bit build even if your Windows OS is 64 bit.

Step 3: Install the extension by copying the downloaded file to the following locations:

• For PHP 5.2 on Windows 64 bit:
  C:\Program Files (x86)\IIS Express\PHP\v5.2\ext\
• For PHP 5.2 on Windows 32 bit:
  C:\Program Files\IIS Express\PHP\v5.2\ext\
• For PHP 5.3 on Windows 64 bit:
  C:\Program Files (x86)\IIS Express\PHP\v5.3\ext\
• For PHP 5.3 on Windows 32 bit:
  C:\Program Files\IIS Express\PHP\v5.3\ext\

Step 4: Open the php.ini file located in the PHP installation folder, e.g.
C:\Program Files\IIS Express\PHP\v5.2\php.ini and append the following at the end (make sure that the absolute path is correct for your version of PHP and Windows.):

[xdebug]
zend_extension = C:\Program Files\iis express\PHP\v5.2\ext\php_xdebug-2.1.0-5.2-vc6-nts.dll

Step 5: Configure PHP to display errors by changing these PHP settings in php.ini file:

display_errors = On
error_reporting = E_ALL & ~E_NOTICE

Step 6: Test that extension is enabled and works by either calling a phpinfo() function from a script or by running a buggy script:

The Xdebug extension provides a lot of useful features that help with debugging of PHP applications. You can learn more about them from the Xdebug documentation. For example you can use it to profile a PHP application. Just change the php.ini file as shown below and then make a request to a PHP script:

[xdebug]
zend_extension = C:\Program Files\iis express\PHP\v5.2\ext\php_xdebug-2.1.0-5.2-vc6-nts.dll
xdebug.profiler_enable = On
xdebug.profiler_output_dir = C:\Windows\temp

The profile log will be saved into the specified directory and will have a name cachegrind.out.* Use WinCacheGrind to open and analyze it:

• Improved detection logic for existing PHP installations. Now PHP Manager detects the location to php.ini file in accordance to the PHP specifications.
• Configuring date.timezone. PHP Manager can automatically set the date.timezone directive which is required to be set starting from PHP 5.3.
• Ability to add new PHP extensions. When pointed to a PHP extension file, the PHP Manager will copy it to the right location and will enable the extension in php.ini file.

In addition, several bugs were fixed in this release. The complete list of changes can be found in the change list.

PHP Manager can now be installed with Web Platform Installer. Use the link below to install it:

Start by installing PHP on Windows by using one of the following methods:

• Install PHP for by using Web PI 3.0. With that you can install PHP for either IIS or WebMatrix or both;
• Download and unpack the PHP 5.3 VC9 non-thread-safe zip package and then register it with IIS by using PHP Manager.

Now open an elevated command line prompt and go to the directory where PHP was installed. For example if PHP 5.3 was installed with Web PI 3.0 then the directory path will be:

• %ProgramFiles%\PHP\v53\ – when PHP is installed for IIS
• %ProgramFiles%\IIS Express\PHP\v53 – when PHP is installed for IIS Express

While in that directory run the go-pear.bat command. If you intend on having multiple versions of PHP installed on the same machine then make sure to answer “local” on the first question asked by go-pear.bat:

C:\Program Files\PHP\v5.3>go-pear.bat

Are you installing a system-wide PEAR or a local copy?
(system|local) [system] : local
Please confirm local copy by typing 'yes' : yes

Below is a suggested file layout for your new PEAR installation.  To
change individual locations, type the number in front of the
directory.  Type 'all' to change all of them or simply press Enter to
accept these locations.

1. Installation base ($prefix)                   : C:\Program Files\PHP\v5.3
2. Temporary directory for processing            : C:\Program Files\PHP\v5.3\tmp
3. Temporary directory for downloads             : C:\Program Files\PHP\v5.3\tmp
4. Binaries directory                            : C:\Program Files\PHP\v5.3
5. PHP code directory ($php_dir)                 : C:\Program Files\PHP\v5.3\pear
6. Documentation directory                       : C:\Program Files\PHP\v5.3\docs
7. Data directory                                : C:\Program Files\PHP\v5.3\data
8. User-modifiable configuration files directory : C:\Program Files\PHP\v5.3\cfg
9. Public Web Files directory                    : C:\Program Files\PHP\v5.3\www
10. Tests directory                               : C:\Program Files\PHP\v5.3\tests
11. Name of configuration file                    : C:\Program Files\PHP\v5.3\pear.ini
12. Path to CLI php.exe                           : .

1-12, 'all' or Enter to continue:

Continue following the prompts to complete the installation process. During the installation you may see a warning similar to the one shown below:

******************************************************************************
WARNING!  The include_path defined in the currently used php.ini does not
contain the PEAR PHP directory you just specified:
<C:\Program Files\PHP\v5.3\pear>
If the specified directory is also not in the include_path used by
your scripts, you will have problems getting any PEAR packages working.

Would you like to alter php.ini <C:\Program Files\PHP\v5.3\php.ini>? [Y/n] : y

Make sure to say yes [y] to the question about altering php.ini so that include_path directive is updated to the correct PEAR PHP directorty

After that you may also get a warning about out-of-date version of PEAR package manager:

** WARNING! Old version found at C:\Program Files\PHP\v5.3, please remove it or
be sure to use the new c:\program files\php\v5.3\pear.bat command

If you see that then after the go-pear.bat has finished its work, run the following command to upgrade the PEAR package manager:

C:\Program Files\PHP\v5.3>pear upgrade pear
downloading PEAR-1.9.1.tgz ...
Starting to download PEAR-1.9.1.tgz (293,587 bytes)
.................done: 293,587 bytes
downloading Archive_Tar-1.3.7.tgz ...
Starting to download Archive_Tar-1.3.7.tgz (17,610 bytes)
...done: 17,610 bytes
downloading Structures_Graph-1.0.4.tgz ...
Starting to download Structures_Graph-1.0.4.tgz (30,318 bytes)
...done: 30,318 bytes
upgrade ok: channel://pear.php.net/Archive_Tar-1.3.7
upgrade ok: channel://pear.php.net/Structures_Graph-1.0.4
upgrade ok: channel://pear.php.net/PEAR-1.9.1
PEAR: Optional feature webinstaller available (PEAR's web-based installer)
PEAR: Optional feature gtkinstaller available (PEAR's PHP-GTK-based installer)
PEAR: Optional feature gtk2installer available (PEAR's PHP-GTK2-based installer)

PEAR: To install optional features use "pear install pear/PEAR#featurename"

At this point PEAR package manager is installed and you can start using it to download and install PEAR packages. For example to install phploc package, follow these steps:

Step 1: Register the appropriate PEAR channels:

C:\Program Files\PHP\v5.3>pear channel-discover pear.phpunit.de
Adding Channel "pear.phpunit.de" succeeded
Discovery of channel "pear.phpunit.de" succeeded

C:\Program Files\PHP\v5.3>pear channel-discover components.ez.no
Adding Channel "components.ez.no" succeeded
Discovery of channel "components.ez.no" succeeded

Step 2: Install the phploc package:

C:\Program Files\PHP\v5.3>pear install phpunit/phploc
phpunit/phploc can optionally use PHP extension "bytekit"
downloading phploc-1.5.1.tgz ...
Starting to download phploc-1.5.1.tgz (7,893 bytes)
.....done: 7,893 bytes
downloading File_Iterator-1.2.3.tgz ...
Starting to download File_Iterator-1.2.3.tgz (3,406 bytes)
...done: 3,406 bytes
downloading ConsoleTools-1.6.1.tgz ...
Starting to download ConsoleTools-1.6.1.tgz (869,994 bytes)
...done: 869,994 bytes
downloading Base-1.8.tgz ...
Starting to download Base-1.8.tgz (236,357 bytes)
...done: 236,357 bytes
install ok: channel://pear.phpunit.de/File_Iterator-1.2.3
install ok: channel://components.ez.no/Base-1.8
install ok: channel://components.ez.no/ConsoleTools-1.6.1
install ok: channel://pear.phpunit.de/phploc-1.5.1

Finally run the phploc to ensure that it works correctly:

C:\Program Files\PHP\v5.3>phploc
phploc 1.5.1 by Sebastian Bergmann.

Usage: phploc [switches] <directory|file> ...

  --count-tests            Count PHPUnit test case classes and test methods.

  --log-xml <file>         Write result in XML format to file.

  --exclude <directory>    Exclude <directory> from code analysis.
  --suffixes <suffix,...>  A comma-separated list of file suffixes to check.

  --help                   Prints this usage information.
  --version                Prints the version and exits.

  --verbose                Print progress bar.

• It is now possible to enable PHP 5.3 (previous versions of WebMatrix and Web PI only supported PHP 5.2)
• PHP can now be enabled on an empty new site in WebMatrix (previously it was required to install a PHP application in order to enable PHP on a site)
• PEAR installation is now included when PHP is installed.

This post describes those improvements in more details.

Enabling PHP in WebMatrix

When you create a new web site in WebMatrix, by default PHP is not enabled. To enable it go to “Site” –> “Settings” and use the “Enable PHP” check box:

You can choose whether to enable latest stable version of PHP 5.2 or PHP 5.3:

If a selected PHP version is not yet installed then it will be downloaded and installed when you choose to enable it for a site:

(Note that Microsoft Visual C++ Redistributable Package is installed as a depenency for PHP 5.3. This is because WebMatrix and IIS use PHP 5.3 VC9 build, which requires VC9 runtime installed on a machine).

In addition to making it easy to enable PHP for a site, WebMatrix also allows you to easily change major PHP version for a particular site. This is useful when you develop a PHP application and want to test that it works correctly across PHP 5.2 and PHP 5.3. To change the PHP version go back to “Site” –> “Settings” section and use the “Change” link:

PEAR installation

PEAR is a framework and distribution system for reusable PHP components. Until recently PEAR was not installed with PHP if installation was performed by Web Platform Installer. With WebMatrix Beta 3 (and with Web Platform Installer 3.0 Beta 3), the PEAR installation scripts are installed when PHP is installed. This means that after you use Web Platform Installer 3.0 to install PHP either for IIS or for WebMatrix, you can enable PEAR by following the instructions described at Getting and installing the PEAR package manager. I will write a more detailed blog post with instructions on how to enable PEAR on Windows and how to install popular PEAR packages.

Both x86 and x64 builds of PHP Manager 1.0 for IIS 7 can be downloaded from the project’s page at codeplex.com:

http://phpmanager.codeplex.com/releases/

Note: if you already have the beta release installed then it will be upgraded when you install the final build of PHP Manager 1.0 for IIS 7.

PHP Manager 1.0 can be used to:

• Register PHP with IIS;
• Validate and properly configure existing PHP installations;
• Run multiple PHP versions side by side on the same server and even within the same web site;
• Check PHP runtime configuration and environment (output of phpinfo() function);
• Configure various PHP settings;
• Enable or disable PHP extensions;
• Remotely manage PHP configuration in php.ini file.

The most important feature introduced in this release is the validation and optimization of existing PHP configurations on IIS. When you install PHP Manager 1.0 on IIS server that already has PHP installed and configured, the PHP Manager will analyze the IIS and PHP configuration settings and will inform you if any of those are not set to recommended values:

Once you click on “View Recommendations” link you will see the list of settings with the description of what’s wrong and what a recommended corrective action should be. You can choose to apply some or all of the recommendations:

Other significant changes and bug fixes included in this release are:

• Support for running different PHP versions within the same web site;
• Functionality to set IIS default document to index.php;
• Links to quickly open php.ini file and PHP error log file;
• Detection of PHP registered via CGI or ISAPI;
• Detection of PHP that is registered by using command line arguments in IIS handler mapping.

Thanks to all who have tried the beta release and provided feedback and bug reports!

IMPORTANT: Even if PHP applications on IIS do not use any of the ASP.NET features the vulnerability still exists as long as ASP.NET is enabled. It is recommended to install the security update as soon as possible.

The security update is available today via the Microsoft Download Center. In a next few days it will also be distributed via Windows Update channels. Once the update is on Windows Update, you can run the Windows Update on your servers to automatically apply the security patch.

If you plan to download the updates directly from Microsoft Download Center then follow the instructions in Scott Guthrie’s blog at:

http://weblogs.asp.net/scottgu/archive/2010/09/28/asp-net-security-update-now-available.aspx

Update on Sep 28th, 2010: The security update for the vulnerability is available. More details can be found at PHP on IIS: get the latest security updates now.

Microsoft has recently released a Security Advisory about a security vulnerability in ASP.NET. This vulnerability exists in all versions of ASP.NET. The PHP applications running on IIS are also subject to this vulnerability if ASP.NET is enabled in IIS.

IMPORTANT: Even if PHP application is not using any of the ASP.NET features the vulnerability still exists as long as ASP.NET is enabled.

More information about the vulnerability can be found at the following links:

• Microsoft Security Advisory
• Security Research and Defense Blog
• Scott Guthrie’s blog about ASP.NET security vulnerability
• FaQ about about security vulnerability on Scott Guthrie’s blog

This blog post describes how to protect you PHP applications on IIS from attacks that exploit this vulnerability.

How to protect your PHP sites on IIS?

Microsoft is working on releasing a patch that fixes this security vulnerability. Until the patch is released there are two options that exist today for protecting your PHP applications on IIS.

1. If you do not need ASP.NET then disable it on the server
2. If you need ASP.NET then apply the workaround described in Scott Guthrie’s blog.

How to disable ASP.NET on IIS 6?

To disable ASP.NET on IIS 6 run the aspnet_regiis tool for every .NET version as shown below:

%WINDIR%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis /u
Start uninstalling ASP.NET (2.0.50727).
......................................................
Finished uninstalling ASP.NET (2.0.50727).

%WINDIR%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis /u
Start uninstalling ASP.NET (1.1.4322.0).
Finished uninstalling ASP.NET (1.1.4322.0).

How to disable ASP.NET on IIS 7?

To disable ASP.NET on IIS 7 follow these steps:

1. In the Windows Start Menu choose “Run:”, type “CompMgmtLauncher” and click “Ok”;
2. Select the “Web Server (IIS)” role, then click “Remove Role Services” and then disable the “ASP.NET” and “.NET Extensibility” checkbox under “Application Development” group:

How to apply the workaround?

If your IIS server is used to host both ASP.NET and PHP or if your PHP web site uses any ASP.NET features, then disabling the ASP.NET on the server is not an option for you. Instead you will need to apply the workaround that is described in details in Scott Guthrie’s blog:

http://weblogs.asp.net/scottgu/archive/2010/09/18/important-asp-net-security-vulnerability.aspx