diff --git a/faq/installation.xml b/faq/installation.xml index c637824502..166d1fe8a8 100644 --- a/faq/installation.xml +++ b/faq/installation.xml @@ -464,38 +464,9 @@ cgi error: - There are several ways of doing this. If you are using Apache, read - their installation specific instructions (Apache 1, Apache 2), otherwise you must - set the PHPRC environment variable: - - - On Windows: - - - Go to Control Panel and open the System icon (Start → Settings - → Control Panel → System, or just Start → Control Panel - → System) - - - Go to the Advanced tab - - - Click on the 'Environment Variables' button - - - Look into the 'System variables' pane - - - Click on 'New' and enter 'PHPRC' as the variable name and the - directory where &php.ini; is located as the variable value (e.g. - C:\php) - - - Press OK and restart your computer - - + There are several ways of doing this. If you are using Apache, + refer to the Apache documentation, otherwise + you must set the PHPRC environment variable. diff --git a/features/commandline.xml b/features/commandline.xml index 45201c5fb1..a00b32660b 100644 --- a/features/commandline.xml +++ b/features/commandline.xml @@ -1289,7 +1289,7 @@ This is a command line PHP script with one option. On Windows, PHP can be configured to run without the need to supply the C:\php\php.exe or the .php - extension, as described in Command + extension, as described in Command Line PHP on Microsoft Windows. diff --git a/install/pecl.xml b/install/pecl.xml index c0ef29765e..64356e58c9 100644 --- a/install/pecl.xml +++ b/install/pecl.xml @@ -111,16 +111,15 @@ $ svn checkout http://svn.php.net/repository/pecl/extname/trunk extname (see next section for the download). - To compile an extension into PHP, please refer to + To compile an extension into PHP, please refer to building from source documentation. - To compile a standalone extension (aka a DLL file), please refer to + To compile a standalone extension (aka a DLL file), please refer to building from source documentation. If the DLL file is available neither with your PHP distribution nor in PECL, you may have to compile it before you can start using the extension. - Where to find an extension? diff --git a/install/windows/apache2.xml b/install/windows/apache2.xml new file mode 100644 index 0000000000..b2ef5bee09 --- /dev/null +++ b/install/windows/apache2.xml @@ -0,0 +1,173 @@ + + + Apache 2.x on Microsoft Windows + + This section contains notes and hints specific to Apache 2.x installs + of PHP on Microsoft Windows systems. + + + + You should read the manual + installation steps first! + + + + + It is strongly recommended to consult the + Apache Documentation + to get have a basic understanding of the Apache 2.x Server. + Also consider reading the + Windows specific notes + for Apache 2.x before reading on here. + + + + Download the most recent version of + Apache 2.x + and a fitting PHP version. Follow the + Manual Installation Steps + and come back to go on with the integration of PHP and Apache. + + + + There are three ways to set up PHP to work with Apache 2.x on Windows. + PHP can be run as a handler, as a CGI, or under FastCGI. + + + ¬e.apache.slashes; + + + Installing as an Apache handler + + To load the PHP module for Apache 2.x the following lines in the + Apache &httpd.conf; configuration file must be inserted: + + PHP and Apache 2.x as handler + + + + + + + + Remember, the actual path to PHP on must be substituted instead of + C:/php/ in the above examples. + Take care that the file referenced in the LoadModule directive is at + the specified location, and to use php7apache2_4.dll + for PHP 7, or php8apache2_4.dll for PHP 8. + + + + The above configuration will enable PHP handling of any file that has a + .php extension, even if there are other file extensions. For example, a + file named example.php.txt will be executed by the + PHP handler. To ensure that only files that end in + .php are executed, use the following configuration + instead: + + + + + + SetHandler application/x-httpd-php + +]]> + + + + + + Running PHP as CGI + + + It is strongly recommended to consult the + Apache CGI documentation + for a more complete understanding of running CGI on Apache. + + + + To run PHP as CGI, the php-cgi files will need to be placed in a + directory designated as a CGI directory using the ScriptAlias directive. + + + + A #! line will need to be placed in the PHP files, + which point to the location of the PHP binary: + + + PHP and Apache 2.x as CGI + + +]]> + + + + &warn.install.cgi; + + + + Running PHP under FastCGI + + + Running PHP under FastCGI has a number of advantages over running it as a + CGI. Setting it up this way is fairly straightforward: + + + Obtain mod_fcgid from + &url.apachelounge;. + Win32 binaries are available for download from that site. + Install the module according to the instructions that will come with it. + + + Configure your web server as shown below, taking care to adjust any paths + to reflect your how you have installed things on your particular system: + + + Configure Apache to run PHP as FastCGI + + + + + + Files with a .php extension will now be executed by the PHP FastCGI + wrapper. + + + + diff --git a/install/windows/legacy/building.xml b/install/windows/building.xml similarity index 84% rename from install/windows/legacy/building.xml rename to install/windows/building.xml index 1cfeab0e3f..2252e3beea 100644 --- a/install/windows/legacy/building.xml +++ b/install/windows/building.xml @@ -1,6 +1,5 @@ - - + Building from source This chapter teaches how to compile PHP from sources on windows, using @@ -11,8 +10,7 @@ See the Wiki documentation at: &url.wiki.windows.build.howto; - - + + + Command Line PHP on Microsoft Windows + + This section contains notes and hints specific to getting PHP running + from the command line for Windows. + + + + You should read the manual + installation steps first! + + + + Getting PHP to run from the command line can be performed without making + any changes to Windows. + + + + + + + But there are some easy steps that can be followed to make this simpler. + Some of these steps should already have been taken, but are repeated here + to be able to provide a complete step-by-step sequence. + + + + + Both PATH and PATHEXT are important + pre-existing system variables in Windows, + and care should be taken to not overwrite either variable, + only to add to them. + + + + + + Append the location of the PHP executable (php.exe, + php-win.exe or php-cli.exe + depending upon your PHP version and display preferences) to the + PATH environment variable. Read more about how to + add your PHP directory to PATH in the corresponding FAQ entry. + + + + + + Append the .PHP extension to the + PATHEXT environment variable. This can be done + at the same time as amending the PATH environment + variable. Follow the same steps as described in the FAQ but amend the + PATHEXT environment variable rather than the + PATH environment variable. + + + The position in which you place the .PHP will + determine which script or program is executed when there are matching + filenames. For example, placing .PHP before + .BAT will cause your script to run, rather than + the batch file, if there is a batch file with the same name. + + + + + + + + Associate the .PHP extension with a file type. This + is done by running the following command: + + + + + + + + + Associate the phpfile file type with the appropriate + PHP executable. This is done by running the following command: + + + + + + + + + + + Following these steps will allow PHP scripts to be run from any directory + without the need to type the PHP executable or the .PHP + extension and all parameters will be supplied to the script for processing. + + + + The example below details some of the registry changes that can be made manually. + + Registry changes + + + + + + + + With these changes the same command can be written as: + + + + or, if your "C:\PHP Scripts" path is in the + PATH environment variable: + + + + + + + + There is a small problem if you intend to use this technique and use your + PHP scripts as a command line filter, like the example below: + + + + or + + + + You may find that the script simply hangs and nothing is output. + To get this operational, you need to make another registry change. + + + + Further information regarding this issue can be found in this Microsoft + Knowledgebase Article : 321788. + As of Windows 10, this setting seems to be reversed, making the default install of + Windows 10 support inherited console handles automatically. This + Microsoft forum post provides the explanation. + + + + diff --git a/install/windows/figures/iis6anonauth.png b/install/windows/figures/iis6anonauth.png deleted file mode 100644 index 0a503d7af7..0000000000 Binary files a/install/windows/figures/iis6anonauth.png and /dev/null differ diff --git a/install/windows/figures/iis6defaultdoc.png b/install/windows/figures/iis6defaultdoc.png deleted file mode 100644 index 850b99255a..0000000000 Binary files a/install/windows/figures/iis6defaultdoc.png and /dev/null differ diff --git a/install/windows/figures/iis7handlericon.png b/install/windows/figures/iis7handlericon.png deleted file mode 100644 index 135943bd38..0000000000 Binary files a/install/windows/figures/iis7handlericon.png and /dev/null differ diff --git a/install/windows/figures/iis7handlermap.png b/install/windows/figures/iis7handlermap.png deleted file mode 100644 index 91c5ae0765..0000000000 Binary files a/install/windows/figures/iis7handlermap.png and /dev/null differ diff --git a/install/windows/figures/iis7vistacgi.png b/install/windows/figures/iis7vistacgi.png deleted file mode 100644 index 520486195b..0000000000 Binary files a/install/windows/figures/iis7vistacgi.png and /dev/null differ diff --git a/install/windows/figures/iis7w2k8cgi.png b/install/windows/figures/iis7w2k8cgi.png deleted file mode 100644 index a8b86eec76..0000000000 Binary files a/install/windows/figures/iis7w2k8cgi.png and /dev/null differ diff --git a/install/windows/index.xml b/install/windows/index.xml index 3bf33724ba..a9534b3fd6 100644 --- a/install/windows/index.xml +++ b/install/windows/index.xml @@ -1,98 +1,84 @@ - Installation on Windows systems - - Installing PHP on modern Microsoft Windows systems and recommended configuration with common web servers. - - + Installation on Windows systems + + Installing PHP on modern Microsoft Windows systems and recommended configuration with common web servers. + + + + The Official releases of PHP on Windows are recommended for production use. + However, you are welcome to build PHP from Source. + You will need a Visual Studio environment. + See Step by Step Build Instructions. + + + + - If you are looking for information about older systems, such as Windows XP, 2003, 98 or Apache 1.x, see the Legacy Info section. + Using PHP on Windows Command line - + + + + Installing PHP on Azure App Services + (aka Microsoft Azure, Windows Azure, or (Windows) Azure Web Apps). + + + + + + + Install Requirements - The Official releases of PHP on Windows are recommended for production use. - However, you are welcome to build PHP from Source. You will need a Visual Studio environment. See Step by Step Build Instructions. + PHP requires at least Windows 2008/Vista. + Either 32-Bit or 64-bit (AKA X86 or X64. PHP does not run on Windows RT/WOA/ARM). + As of PHP 7.2.0 Windows 2008 and Vista are no longer supported. + + + + PHP requires the Visual C runtime (CRT). Many applications require that so it may already be installed. + + + + The Microsoft Visual C++ Redistributable for Visual Studio 2019 is suitable + for all these PHP versions, see + https://visualstudio.microsoft.com/downloads/. + + + + You MUST download the x86 CRT for PHP x86 builds and the x64 CRT for PHP x64 builds. + + + + If CRT is already installed, the installer will tell you that and not change anything. + + + + The CRT installer supports the /quiet and /norestart command-line switches, so you can script running it. + + + + + PECL + + PECL extensions are pre-built for Windows and available from: + http://windows.php.net/downloads/pecl/releases/ - - - - Using PHP on Windows Command line - - - - - Installing PHP on Azure App Services (aka Microsoft Azure, Windows Azure, or (Windows) Azure Web Apps). - - - + Some extensions use features specific to some Unix systems and so are not available on Windows. + Otherwise, all extensions are available for Windows. + - - Install Requirements - - - PHP 5.5+ require at least Windows 2008/Vista, or 2008r2, 2012, 2012r2, 2016 or 7, 8, 8.1, 10. Either 32-Bit or 64-bit (aka X86 or X64. PHP does not run on Windows RT/WOA/ARM). - As of PHP 7.2.0 Windows 2008 and Vista are no longer supported. - - - - PHP requires the Visual C runtime(CRT). Many applications require that so it may already be installed. - - - - PHP 5.5 and 5.6 require VC CRT 11 (Visual Studio 2012). See: https://www.microsoft.com/en-us/download/details.aspx?id=30679 - - - - PHP 7.0 and 7.1 require VC CRT 14 (Visual Studio 2015). - PHP 7.2, 7.3 and 7.4 require VC CRT 15 (Visual Studio 2017). - The Microsoft Visual C++ Redistributable for Visual Studio 2019 is suitable - for all these PHP versions, see - https://visualstudio.microsoft.com/downloads/. - - - - You MUST download the x86 CRT for PHP x86 builds and the x64 CRT for PHP x64 builds. - - - - If CRT is already installed, the installer will tell you that and not change anything. - - - - The CRT installer supports the /quiet and /norestart command-line switches, so you can script running it. - - - - VC11 CRT DLLs can be copied from your local machine to a remote machine(a `Copy Deployment` installation) instead of running the installer on the remote machine (such as a web server you have restricted access to). - - - - VC14 CRT does not support a `Copy Deployment` installation. VC14 CRT has many more DLLs(most in files with names starting with api-*). If you can find them all and copy them, it will also work (try a tool like Resource Hacker to get a list of all the DLLs to copy). - - - - - - PECL - - PECL extensions are pre-built for Windows and available from: http://windows.php.net/downloads/pecl/releases/ - - - Some extensions use features specific to some Unix systems and so are not available on Windows. Otherwise, all extensions are available for Windows. - - - - - &install.windows.tools; - &install.windows.recommended; - &install.windows.manual; - &install.windows.troubleshooting; - &install.windows.legacy.index; + &install.windows.tools; + &install.windows.recommended; + &install.windows.manual; + &install.windows.building; + &install.windows.commandline; + &install.windows.apache2; + &install.windows.troubleshooting; - - Apache 1.3.x on Microsoft Windows - - This section contains notes and hints specific to Apache 1.3.x installs - of PHP on Microsoft Windows systems. There are also - - - - - Please read the manual - installation steps first! - - - - - There are two ways to set up PHP to work with Apache 1.3.x - on Windows. One is to use the CGI binary (php.exe - for PHP 4 and php-cgi.exe for PHP 5), - the other is to use the Apache Module DLL. In either case - you need to edit your &httpd.conf; to configure Apache to - work with PHP, and then restart the server. - - - - It is worth noting here that now the SAPI module has been - made more stable under Windows, we recommend it's use above - the CGI binary, since it is more transparent and secure. - - - - Although there can be a few variations of configuring PHP - under Apache, these are simple enough to be used by the - newcomer. Please consult the Apache Documentation for further - configuration directives. - - - - After changing the configuration file, remember to restart the server, for - example, NET STOP APACHE followed by - NET START APACHE, if you run Apache as a Windows - Service, or use your regular shortcuts. - - - ¬e.apache.slashes; - - - Installing as an Apache module - - You should add the following lines to your Apache &httpd.conf; file: - - - - PHP as an Apache 1.3.x module - - This assumes PHP is installed to c:\php. Adjust the - path if this is not the case. - - - For PHP 4: - - - - - - For PHP 5: - - - - - - For both: - - - conditional brace -AddType application/x-httpd-php .php - -# For syntax highlighted .phps files, also add -AddType application/x-httpd-php-source .phps -]]> - - - - - - - Installing as a CGI binary - - - If you unzipped the PHP package to C:\php\ as described - in the Manual - Installation Steps section, you need to insert - these lines to your Apache configuration file to set - up the CGI binary: - - PHP and Apache 1.3.x as CGI - - - - - Note that the second line in the list above can be found - in the actual versions of &httpd.conf;, but it is commented out. Remember - also to substitute the c:/php/ for your actual path to - PHP. - - &warn.install.cgi; - - If you would like to present PHP source files syntax highlighted, there - is no such convenient option as with the module version of PHP. - If you chose to configure Apache to use PHP as a CGI binary, you - will need to use the highlight_file function. To - do this simply create a PHP script file and add this code: - <?php highlight_file('some_php_script.php'); ?>. - - - - - - diff --git a/install/windows/legacy/apache2.xml b/install/windows/legacy/apache2.xml deleted file mode 100644 index cb4fd98613..0000000000 --- a/install/windows/legacy/apache2.xml +++ /dev/null @@ -1,198 +0,0 @@ - - - - Apache 2.x on Microsoft Windows - - This section contains notes and hints specific to Apache 2.x installs - of PHP on Microsoft Windows systems. We also - - - - - You should read the manual - installation steps first! - - - - Apache 2.2 Support - - Users of Apache 2.2 should note that the DLL file for Apache 2.2 is - named php5apache2_2.dll rather than php5apache2.dll - and is available only for PHP 5.2.0 and later. - - - - - You are strongly encouraged to consult the - Apache Documentation to get - a basic understanding of the Apache 2.x Server. Also consider - reading the Windows specific - notes for Apache 2.x before reading on here. - - - - Apache 2.x is designed to run on the Windows version designated as - server platforms, such as Windows NT 4.0, Windows 2000, - Windows XP, or Windows 7. While Apache 2.x works tolerably well on Windows 9x, - support on these platforms is incomplete, and some things will not work - correctly. There is no plan to remedy this situation. - - - - Download the most recent version of - Apache 2.x and a fitting PHP version. - Follow the Manual Installation - Steps and come back to go on with the integration of PHP and Apache. - - - - There are three ways to set up PHP to work with Apache 2.x on Windows. - You can run PHP as a handler, as a CGI, or under FastCGI. - - - ¬e.apache.slashes; - - - Installing as an Apache handler - - You need to insert the following lines into your - Apache &httpd.conf; configuration file to load the - PHP module for Apache 2.x: - - PHP and Apache 2.x as handler - - - - - - - - Remember to substitute your actual path to PHP for the - C:/php/ in the above examples. Take care to use - either php5apache2.dll or - php5apache2_2.dll in your LoadModule directive and - verify that the referenced file is in fact located at the file path - that you point to in this directive. - - - - The above configuration will enable PHP handling of any file that has a - .php extension, even if there are other file extensions. For example, a - file named example.php.txt will be executed by the - PHP handler. To ensure that only files that end in - .php are executed, use the following configuration - instead: - - - - - - SetHandler application/x-httpd-php - -]]> - - - - - - Running PHP as CGI - - - You should consult the Apache CGI - documentation for a more complete understanding of running CGI - on Apache. - - - - To run PHP as CGI, you'll need to place your php-cgi files in a - directory designated as a CGI directory using the ScriptAlias directive. - - - - You will then need to insert a #! line in the PHP files, pointing to the - location of your PHP binary: - - - PHP and Apache 2.x as CGI - - -]]> - - - - &warn.install.cgi; - - - - Running PHP under FastCGI - - - Running PHP under FastCGI has a number of advantages over running it as a - CGI. Setting it up this way is fairly straightforward: - - - Obtain mod_fcgid from - &url.apache.fcgid;. Win32 - binaries are available for download from that site. Install the module - according to the instructions that will come with it. - - - Configure your web server as shown below, taking care to adjust any paths - to reflect your how you have installed things on your particular system: - - - Configure Apache to run PHP as FastCGI - - - - - - Files with a .php extension will now be executed by the PHP FastCGI - wrapper. - - - - - - - diff --git a/install/windows/legacy/commandline.xml b/install/windows/legacy/commandline.xml deleted file mode 100644 index 7d6a295437..0000000000 --- a/install/windows/legacy/commandline.xml +++ /dev/null @@ -1,209 +0,0 @@ - - - - Command Line PHP on Microsoft Windows - - This section contains notes and hints specific to getting PHP running - from the command line for Windows. - - - - You should read the manual - installation steps first! - - - - Getting PHP to run from the command line can be performed without making - any changes to Windows. - - - - - - - But there are some easy steps that can be followed to make this simpler. - Some of these steps should already have been taken, but are repeated here - to be able to provide a complete step-by-step sequence. - - - - - - - Both PATH and PATHEXT are important pre-existing system variables in Windows, and care should be taken to not overwrite either variable, only to add to them. - - - - - - Append the location of the PHP executable (php.exe, - php-win.exe or php-cli.exe - depending upon your PHP version and display preferences) to the - PATH environment variable. Read more about how to - add your PHP directory to PATH in the corresponding FAQ entry. - - - - - - Append the .PHP extension to the - PATHEXT environment variable. This can be done - at the same time as amending the PATH environment - variable. Follow the same steps as described in the FAQ but amend the - PATHEXT environment variable rather than the - PATH environment variable. - - - The position in which you place the .PHP will - determine which script or program is executed when there are matching - filenames. For example, placing .PHP before - .BAT will cause your script to run, rather than - the batch file, if there is a batch file with the same name. - - - - - - - - Associate the .PHP extension with a file type. This - is done by running the following command: - - - - - - - - - Associate the phpfile file type with the appropriate - PHP executable. This is done by running the following command: - - - - - - - - - - - Following these steps will allow PHP scripts to be run from any directory - without the need to type the PHP executable or the .PHP - extension and all parameters will be supplied to the script for processing. - - - - The example below details some of the registry changes that can be made manually. - - Registry changes - - - - - - - - With these changes the same command can be written as: - - - - or, if your "C:\PHP Scripts" path is in the - PATH environment variable: - - - - - - - - There is a small problem if you intend to use this technique and use your - PHP scripts as a command line filter, like the example below: - - - - or - - - - You may find that the script simply hangs and nothing is output. - To get this operational, you need to make another registry change. - - - - Further information regarding this issue can be found in this Microsoft - Knowledgebase Article : 321788. - As of Windows 10, this setting seems to be reversed, making the default install of - Windows 10 support inherited console handles automatically. This - Microsoft forum post provides the explanation. - - - - - diff --git a/install/windows/legacy/extensions.xml b/install/windows/legacy/extensions.xml deleted file mode 100644 index fe76468b75..0000000000 --- a/install/windows/legacy/extensions.xml +++ /dev/null @@ -1,361 +0,0 @@ - - - - Installation of extensions on Windows - - After installing PHP and a web server on Windows, you will probably want to - install some extensions for added functionality. You can choose which - extensions you would like to load when PHP starts by modifying your - &php.ini;. You can also load a module dynamically in your script using - dl. - - - The DLLs for PHP extensions are prefixed with php_. - - - Many extensions are built into the Windows version - of PHP. This means additional DLL files, and the - extension directive, are - not used to load these extensions. The Windows - PHP Extensions - table lists extensions that require, or used to require, additional PHP - DLL files. Here's a list of built in extensions (updated PHP 5.0.4): - BCMath, - Calendar, - COM, - Ctype, - DOM, - FTP, - LibXML, - Iconv, - ODBC, - PCRE, - Session, - SimpleXML, - SPL, - WDDX, - XML&listendand; - Zlib. - - - The default location PHP searches for extensions is - C:\php5. To change this - setting to reflect your setup of PHP edit your &php.ini; file: - - - - You will need to change the - extension_dir setting to - point to the directory where your extensions lives, or where you have - placed your php_*.dll files. For example: - - - - - - - - - - Enable the extension(s) in &php.ini; you want to use by uncommenting the - extension=php_*.dll lines in &php.ini;. This is done - by deleting the leading ; from the extension you want to load. - - Enable <link linkend="book.bzip2">Bzip2</link> extension for PHP-Windows - - - - - - - - - Some of the extensions need extra DLLs to work. Couple of them can be - found in the distribution package, in the main folder, but some, for example Oracle - (php_oci8.dll) require DLLs which are not bundled - with the distribution package. Don't forget to include C:\php in the system - PATH (this process is explained in a separate FAQ entry). - - - - - Some of these DLLs are not bundled with the PHP distribution. See each - extensions documentation page for details. Also, read the manual - section titled Installation of PECL - extensions for details on PECL. An - increasingly large number of PHP extensions are found in - PECL, and these extensions require a - separate download. - - - - - - If you are running a server module version of PHP - remember to restart your web server to reflect your changes to &php.ini;. - - - - - - The following table describes some of the extensions available and required - additional dlls. - - PHP Extensions - - - - Extension - Description - Notes - - - - - php_bz2.dll - bzip2 compression functions - None - - - php_calendar.dll - Calendar conversion functions - None - - - php_ctype.dll - ctype family functions - None - - - php_curl.dll - CURL, Client URL library functions - Requires: libeay32.dll, - ssleay32.dll (bundled), or, as of OpenSSL 1.1 - libcrypto-*.dll and libssl-*.dll (bundled) - - - php_dba.dll - DBA: DataBase (dbm-style) - Abstraction layer functions - None - - - php_dbase.dll - dBase functions - None - - - php_exif.dll - EXIF functions - - php_mbstring.dll. And, - php_exif.dll must be loaded after - php_mbstring.dll in &php.ini;. - - - - php_fbsql.dll - FrontBase functions - None - - - php_fdf.dll - FDF: Forms Data Format functions. - Requires: fdftk.dll (bundled) - - - php_ftp.dll - FTP functions - None - - - php_gd2.dll - GD library image functions - GD2 - - - php_gettext.dll - Gettext functions - - PHP <= 4.2.0 requires gnu_gettext.dll (bundled), - PHP >= 4.2.3 requires libintl-1.dll, - iconv.dll (bundled). - - - - php_hyperwave.dll - HyperWave functions - None - - - php_iconv.dll - ICONV characterset conversion - - Requires: iconv-1.3.dll (bundled), iconv.dll - - - - php_iisfunc.dll - IIS management functions - None - - - php_imap.dll - IMAP POP3 and NNTP functions - None - - - php_interbase.dll - InterBase functions - Requires: gds32.dll (bundled) - - - php_ldap.dll - LDAP functions - - Requires libeay32.dll, - ssleay32.dll (bundled), or, as of OpenSSL 1.1 - libcrypto-*.dll and libssl-*.dll (bundled) - - - - php_mbstring.dll - Multi-Byte String functions - None - - - php_mcrypt.dll - Mcrypt Encryption functions - Requires: libmcrypt.dll - - - php_mhash.dll - Mhash functions - Requires: libmhash.dll (bundled) - - - php_mysql.dll - MySQL functions - Requires libmysql.dll (bundled) - - - php_mysqli.dll - MySQLi functions - Requires libmysql.dll - (libmysqli.dll in PHP <= 5.0.2) (bundled) - - - php_oci8.dll - Oracle 8 functions - Requires: Oracle 8.1+ client libraries - - - php_openssl.dll - OpenSSL functions - Requires: libeay32.dll (bundled), - or, as of OpenSSL 1.1, liblibcrypto-*.dll (bundled) - - - php_pgsql.dll - PostgreSQL functions - None - - - php_shmop.dll - Shared Memory functions - None - - - php_snmp.dll - SNMP get and walk functions - NT only! - - - php_soap.dll - SOAP functions - None - - - php_sockets.dll - Socket functions - None - - - php_tidy.dll - Tidy functions - None - - - php_tokenizer.dll - Tokenizer functions - None - - - php_w32api.dll - W32api functions - None - - - php_xmlrpc.dll - XML-RPC functions - Requires: iconv.dll (bundled) - - - php_xslt.dll - XSLT functions - - Requires sablot.dll, expat.dll, - iconv.dll (bundled). - - - - php_yaz.dll - YAZ functions - Requires: yaz.dll (bundled) - - - php_zip.dll - Zip File functions - Read only access - - - php_zlib.dll - ZLib compression functions - None - - - -
- - - - diff --git a/install/windows/legacy/iis.xml b/install/windows/legacy/iis.xml deleted file mode 100644 index 2ce4c7943a..0000000000 --- a/install/windows/legacy/iis.xml +++ /dev/null @@ -1,41 +0,0 @@ - - - - Microsoft IIS - - This section contains PHP installation instructions specific to Microsoft Internet Information Services (IIS). - - - - - Manually installing PHP on Microsoft IIS 5.1 and IIS 6.0 - - - - - Manually installing PHP on Microsoft IIS 7.0 and later - - - - - - diff --git a/install/windows/legacy/iis6.xml b/install/windows/legacy/iis6.xml deleted file mode 100644 index 83b49b4c96..0000000000 --- a/install/windows/legacy/iis6.xml +++ /dev/null @@ -1,241 +0,0 @@ - - - - - Microsoft IIS 5.1 and IIS 6.0 - - This section contains instructions for manually setting up Internet Information - Services (IIS) 5.1 and IIS 6.0 to work with PHP on Microsoft Windows XP and Windows - Server 2003. For instructions on setting up IIS 7.0 and later versions on Windows - Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2 refer to - Microsoft IIS 7.0 and later. - - - Configuring IIS to process PHP requests - - Download and install PHP in accordance to the instructions described in - manual installation steps - - - Non-thread-safe build of PHP is recommended when using IIS. The non-thread-safe - builds are available at PHP for Windows: - Binaries and Sources Releases. - - - - - Configure the CGI- and FastCGI-specific settings in php.ini file as shown below: - - CGI and FastCGI settings in <filename>php.ini</filename> - - - - - - - Download and install the Microsoft FastCGI Extension for IIS 5.1 and 6.0. - The extension is available for 32-bit and 64-bit platforms - select the right download package for your platform. - - Configure the FastCGI extension to handle PHP-specific requests by running the command shown below. - Replace the value of the "-path" parameter with the absolute file path to the - php-cgi.exe file. - - Configuring FastCGI extension to handle PHP requests - - - - - - - This command will create an IIS script mapping for *.php file extension, which will result in all URLs - that end with .php being handled by FastCGI extension. Also, it will configure FastCGI extension to - use the executable php-cgi.exe to process the PHP requests. - - - At this point the required installation and configuration steps are completed. The remaining - instructions below are optional but highly recommended for achieving optimal functionality - and performance of PHP on IIS. - - - - - - Impersonation and file system access - - It is recommended to enable FastCGI impersonation in PHP when using IIS. This - is controlled by the fastcgi.impersonate directive in php.ini file. When - impersonation is enabled, PHP will perform all the file system operations on - behalf of the user account that has been determined by IIS authentication. This - ensures that even if the same PHP process is shared across different IIS web - sites, the PHP scripts in those web sites will not be able to access each - others' files as long as different user accounts are used for IIS authentication - on each web site. - - - For example IIS 5.1 and IIS 6.0, in its default configuration, has anonymous authentication enabled - with built-in user account IUSR_<MACHINE_NAME> used as a default identity. This means that in - order for IIS to execute PHP scripts, it is necessary to grant IUSR_<MACHINE_NAME> account - read permission on those scripts. If PHP applications need to perform write operations on certain - files or write files into some folders then IUSR_<MACHINE_NAME> account should have write permission to those. - - - To determine which user account is used by IIS anonymous authentication, follow these steps: - - - In the Windows Start Menu choose "Run:", type "inetmgr" and click "Ok"; - - - Expand the list of web sites under the "Web Sites" node in the tree view, right-click on a web - site that is being used and select "Properties"; - - - - Click the "Directory Security" tab; - - - Take note of a "User name:" field in the "Authentication Methods" dialog - - - - Anonymous authenication for IIS 5.1 and IIS 6.0 - - - - - - - To modify the permissions settings on files and folders, use the Windows Explorer user interface - or icacls command. - - Configuring file access permissions - - - - - - - - Set <filename>index.php</filename> as a default document in IIS - - The IIS default documents are used for HTTP requests that do not specify a document name. With PHP applications, - index.php usually acts as a default document. To add index.php to the list of - IIS default documents, follow these steps: - - - In the Windows Start Menu choose "Run:", type "inetmgr" and click "Ok"; - - - Right-click on the "Web Sites" node in the tree view and select "Properties"; - - - Click the "Documents" tab; - - - Click the "Add..." button and enter "index.php" for the "Default content page:". - - - - Setting index.php as default document for IIS - - - - - - - - FastCGI and PHP Recycling configuration - - Configure IIS FastCGI extension settings for recycling of PHP processes by using the commands shown below. - The FastCGI setting instanceMaxRequests controls how many requests will be processed by a single - php-cgi.exe process before FastCGI extension shuts it down. The PHP environment variable - PHP_FCGI_MAX_REQUESTS controls how many requests a single php-cgi.exe process - will handle before it recycles itself. Make sure that the value specified for FastCGI InstanceMaxRequests - setting is less than or equal to the value specified for PHP_FCGI_MAX_REQUESTS. - - Configuring FastCGI and PHP recycling - - - - - - - - Configuring FastCGI timeout settings - - Increase the timeout settings for FastCGI extension if there are applications that have long running PHP scripts. - The two settings that control timeouts are ActivityTimeout and RequestTimeout. - Refer to Configuring FastCGI Extension for IIS 6.0 for more - information about those settings. - - Configuring FastCGI timeout settings - - - - - - - - Changing the Location of <filename>php.ini</filename> file - - PHP searches for php.ini file in - several locations and it is - possible to change the default locations of php.ini - file by using PHPRC environment variable. To instruct PHP - to load the configuration file from a custom location run the command shown below. - The absolute path to the directory with php.ini file should be - specified as a value of PHPRC environment variable. - - Changing the location of <filename>php.ini</filename> file - - - - - - - - - diff --git a/install/windows/legacy/iis7.xml b/install/windows/legacy/iis7.xml deleted file mode 100644 index 410133e607..0000000000 --- a/install/windows/legacy/iis7.xml +++ /dev/null @@ -1,387 +0,0 @@ - - - - - Microsoft IIS 7.0 and later - - This section contains instructions for manually setting up Internet Information - Services (IIS) 7.0 and later to work with PHP on Microsoft Windows Vista SP1, - Windows 7, Windows Server 2008 and Windows Server 2008 R2. For instructions - on setting up IIS 5.1 and IIS 6.0 on Windows XP and Windows Server 2003 refer to - Microsoft IIS 5.1 and IIS 6.0. - - - Enabling FastCGI support in IIS - - FastCGI module is disabled in default installation of IIS. The steps to enable it differ - based on the version of Windows being used. - - - To enable FastCGI support on Windows Vista SP1 and Windows 7: - - - - In the Windows Start Menu choose "Run:", type "optionalfeatures.exe" - and click "Ok"; - - - - - In the "Windows Features" dialog expand "Internet Information - Services", "World Wide Web Services", "Application Development - Features" and then enable the "CGI" checkbox; - - - - - Click OK and wait until the installation is complete. - - - - - Enabling FastCGI support for IIS7 on Windows Vista SP1 and Windows 7 - - - - - - - To enable FastCGI support on Windows Server 2008 and Windows Server 2008 R2: - - - - In the Windows Start Menu choose "Run:", type "CompMgmtLauncher" - and click "Ok"; - - - - - If the "Web Server (IIS)" role is not present under the "Roles" - node, then add it by clicking "Add Roles"; - - - - - If the "Web Server (IIS)" role is present, then click "Add Role Services" - and then enable the "CGI" checkbox under "Application Development" group; - - - - - Click "Next" and then "Install" and wait for the installation to complete. - - - - - Enabling FastCGI support on Windows Server 2008 and Windows Server 2008 R2 - - - - - - - - Configuring IIS to process PHP requests - - Download and install PHP in accordance to the instructions described in - manual installation steps - - - Non-thread-safe build of PHP is recommended when using IIS. The non-thread-safe - builds are available at PHP for Windows: - Binaries and Sources Releases. - - - - - Configure the CGI- and FastCGI-specific settings in php.ini file as shown below: - - CGI and FastCGI settings in <filename>php.ini</filename> - - - - - - - Configure IIS handler mapping for PHP by using either IIS Manager user interface or a command line tool. - - - Using IIS Manager user interface to create a handler mapping for PHP - - Follow these steps to create an IIS handler mapping for PHP in IIS Manager user interface: - - - In the Windows Start Menu choose "Run:", type "inetmgr" and click "Ok"; - - - In the IIS Manager user interface select the server node in the "Connections" tree view; - - - - In the "Features View" page open the "Handler Mappings" feature; - - Create IIS handler mapping for PHP : Locate Handler Mappings - - - - - - - - In the "Actions" pane click "Add Module Mapping..."; - - - - In the "Add Module Mapping" dialog enter the following: - - - Request path: *.php - - - Module: FastCgiModule - - - Executable: C:\[Path to PHP installation]\php-cgi.exe - - - Name: PHP_via_FastCGI - - - - - - - Click "Request Restrictions" button and then configure the mapping to invoke handler - only if request is mapped to a file or a folder; - - - - Click OK on all the dialogs to save the configuration. - - - - Create IIS handler mapping for PHP : Add Handler Mapping - - - - - - - - Using command line tool to create a handler mapping for PHP - - Use the command shown below to create an IIS FastCGI process pool which will use php-cgi.exe - executable for processing PHP requests. Replace the value of the fullPath parameter with the - absolute file path to the php-cgi.exe file. - - Creating IIS FastCGI process pool - - - - - - - Configure IIS to handle PHP specific requests by running the command shown below. Replace the value of the - scriptProcessor parameter with the absolute file path to the php-cgi.exe file. - - Creating handler mapping for PHP requests - - - - - - - This command creates an IIS handler mapping for *.php file extension, which will result in all URLs that - end with .php being handled by FastCGI module. - - - At this point the required installation and configuration steps are completed. The remaining - instructions below are optional but highly recommended for achieving optimal functionality - and performance of PHP on IIS. - - - - - - - Impersonation and file system access - - It is recommended to enable FastCGI impersonation in PHP when using IIS. This - is controlled by the fastcgi.impersonate directive in php.ini - file. When impersonation is enabled, PHP will perform all the file system operations on behalf of - the user account that has been determined by IIS authentication. This ensures that even if the - same PHP process is shared across different IIS web sites, the PHP scripts in those web sites - will not be able to access each other's files as long as different user accounts are used - for IIS authentication on each web site. - - - For example IIS 7, in its default configuration, has anonymous authentication enabled with - built-in user account IUSR used as a default identity. This means that in order for IIS to - execute PHP scripts, it is necessary to grant IUSR account read permission on those scripts. - If PHP applications need to perform write operations on certain files or write files into some - folders then IUSR account should have write permission to those. - - - To determine what user account is used as an anonymous identity in IIS 7 use the following command. - Replace the "Default Web Site" with the name of IIS web site that you use. In the output - XML configuration element look for the userName attribute. - - Determining the account used as IIS anonymous identity - - - - - - - - -]]> - - - - - If userName attribute is not present in the anonymousAuthentication element, - or is set to an empty string, then it means that the application pool identity is used as an - anonymous identity for that web site. - - - - - To modify the permissions settings on files and folders, use the Windows Explorer - user interface or icacls command. - - Configuring file access permissions - - - - - - - - Set <filename>index.php</filename> as a default document in IIS - - The IIS default documents are used for HTTP requests that do not specify a - document name. With PHP applications, index.php usually - acts as a default document. To add index.php to the list - of IIS default documents, use this command: - - Set <filename>index.php</filename> as a default document in IIS - - - - - - - - FastCGI and PHP Recycling configuration - - Configure IIS FastCGI settings for recycling of PHP processes by using the commands shown below. - The FastCGI setting instanceMaxRequests controls how many requests will be - processed by a single php-cgi.exe process before IIS shuts it down. - The PHP environment variable PHP_FCGI_MAX_REQUESTS controls how many - requests a single php-cgi.exe process will handle before it recycles - itself. Make sure that the value specified for FastCGI InstanceMaxRequests - setting is less than or equal to the value specified for PHP_FCGI_MAX_REQUESTS. - - Configuring FastCGI and PHP recycling - - - - - - - - FastCGI timeout settings - - Increase the timeout settings for FastCGI if it is expected to have long running PHP scripts. - The two settings that control timeouts are activityTimeout and - requestTimeout. Use the commands below to change the timeout settings. - Make sure to replace the value in the fullPath parameter to - contain the absolute path to the php-cgi.exe file. - - Configuring FastCGI timeout settings - - - - - - - - Changing the Location of <filename>php.ini</filename> file - - PHP searches for php.ini file in - several locations and it is - possible to change the default locations of php.ini - file by using PHPRC environment variable. To instruct PHP - to load the configuration file from a custom location run the command shown below. - The absolute path to the directory with php.ini file should be - specified as a value of PHPRC environment variable. - - Changing the location of <filename>php.ini</filename> file - - - - - - - - - diff --git a/install/windows/legacy/index.xml b/install/windows/legacy/index.xml deleted file mode 100644 index 29fb77336d..0000000000 --- a/install/windows/legacy/index.xml +++ /dev/null @@ -1,68 +0,0 @@ - - - - Installation on old Windows systems - - This section applies to Windows 98/Me and Windows NT/2000/XP/2003. PHP - will not work on 16 bit platforms such as Windows 3.1 and sometimes - we refer to the supported Windows platforms as Win32. - - - - Windows XP/2003 are no longer supported as of PHP 5.5.0. - - - - - Windows 98/Me/NT4/2000 are no longer supported as of PHP 5.3.0. - - - - - Windows 95 is no longer supported as of PHP 4.3.0. - - - - If you have a development environment such as Microsoft Visual Studio, you can also - - build PHP from the original source code. - - - Once you have PHP installed on your Windows system, you may also - want to load various extensions - for added functionality. - - - &install.windows.legacy.manual; - &install.windows.legacy.iis; - &install.windows.legacy.iis6; - &install.windows.legacy.iis7; - &install.windows.legacy.apache1; - &install.windows.legacy.apache2; - &install.windows.legacy.sambar; - &install.windows.legacy.xitami; - &install.windows.legacy.building; - &install.windows.legacy.extensions; - &install.windows.legacy.commandline; - - - diff --git a/install/windows/legacy/manual.xml b/install/windows/legacy/manual.xml deleted file mode 100644 index a29b936cea..0000000000 --- a/install/windows/legacy/manual.xml +++ /dev/null @@ -1,264 +0,0 @@ - - - - Manual Installation Steps - - This section contains instructions for manually installing and configuring - PHP on Microsoft Windows. - - - Selecting and downloading the PHP distribution package - - Download the PHP zip binary distribution from - PHP for Windows: Binaries and Sources. - There are several different versions of the zip package - to choose the right version for you, - follow the detailed guide on the download page. - - - - The PHP package structure and content - - Unpack the content of the zip archive into a directory of your choice, for - example C:\PHP\. The directory and file structure extracted from the zip will - look as below: - - PHP 5 package structure - - - - - - - Below is the list of the modules and executables included in the PHP zip - distribution: - - - - go-pear.bat - the PEAR setup script. Refer to Installation (PEAR) - for more details. - - - - - php-cgi.exe - CGI executable that can be used when running PHP on IIS via CGI or FastCGI. - - - - - php-win.exe - the PHP executable for executing PHP scripts without using a command line window - (for example PHP applications that use Windows GUI). - - - - - php.exe - the PHP executable for executing PHP scripts within a command line interface (CLI). - - - - - php5apache2_2.dll - Apache 2.2.X module. - - - - - php5apache2_2_filter.dll - Apache 2.2.X filter. - - - - - - - Changing the <filename>php.ini</filename> file - - After the php package content has been extracted, copy the php.ini-production into php.ini - in the same folder. If necessary, it is also possible to place the php.ini into any other location of your choice - but that will require additional configuration steps as described in PHP Configuration. - - - The php.ini file tells PHP how to configure itself, and how to work with the - environment that it runs in. Here are a number of settings for the php.ini file - that help PHP work better with Windows. Some of these are optional. There are - many other directives that may be relevant to your environment - refer to the - list of php.ini directives for more information. - - - Required directives: - - - - extension_dir = <path to extension directory> - The extension_dir needs - to point to the directory where PHP extensions files are stored. The path can be absolute - (i.e. "C:\PHP\ext") or relative (i.e. ".\ext"). Extensions that are listed lower in the php.ini file need - to be located in the extension_dir. - - - - - extension = xxxxx.dll - For each extension you wish to enable, you need a corresponding "extension=" - directive that tells PHP which extensions in the extension_dir to load at startup time. - - - - - log_errors = On - PHP has an error logging facility that can be used to send errors to a file, - or to a service (i.e. syslog) and works in conjunction with the error_log directive below. When running under IIS, - the log_errors should be enabled, with a valid error_log. - - - - - error_log = <path to the error log file> - The error_log needs to specify the absolute, - or relative path to the file where PHP errors should be logged. This file needs to be writable for the web server. - The most common places for this file are in various TEMP directories, for example "C:\inetpub\temp\php-errors.log". - - - - - cgi.force_redirect = 0 - This directive is required for running under IIS. - It is a directory security facility required by many other web servers. However, enabling it under IIS will - cause the PHP engine to fail on Windows. - - - - - cgi.fix_pathinfo = 1 - This lets PHP access real path info following the CGI Spec. - The IIS FastCGI implementation needs this set. - - - - - fastcgi.impersonate = 1 - FastCGI under IIS supports the ability to impersonate - security tokens of the calling client. This allows IIS to define the security context that the request runs under. - - - - - fastcgi.logging = 0 - FastCGI logging should be disabled on IIS. If it is left enabled, - then any messages of any class are treated by FastCGI as error conditions which will cause IIS to generate an HTTP 500 exception. - - - - - - Optional directives - - - - max_execution_time = ## - This directive tells PHP the maximum amount of time that it can spend - executing any given script. The default for this is 30 seconds. Increase the value of this directive if PHP application take long time to execute. - - - - - memory_limit = ###M - The amount of memory available for the PHP process, in Megabytes. - The default is 128, which is fine for most PHP applications. Some of the more complex ones might need more. - - - - - display_errors = Off - This directive tells PHP whether to include any error messages in the - stream that it returns to the Web server. If this is set to "On", then PHP will send whichever classes of errors - that you define with the error_reporting directive back to web server as part of the error stream. - For security reasons it is recommended to set it to "Off" on production servers in order not to reveal any - security sensitive information that is often included in the error messages. - - - - - open_basedir = <paths to directories, separated by semicolon>, e.g. - openbasedir="C:\inetpub\wwwroot;C:\inetpub\temp". This directive specified the directory paths where PHP - is allowed to perform file system operations. Any file operation outside of the specified paths will result in an error. - This directive is especially useful for locking down the PHP installation in shared hosting environments to prevent - PHP scripts from accessing any files outside of the web site's root directory. - - - - - upload_max_filesize = ###M and post_max_size = ###M - - The maximum allowed size of an uploaded file and post data respectively. The values of these directives should be - increased if PHP applications need to perform large uploads, such as for example photos or video files. - - - - - - PHP is now setup on your system. The next step is to choose a web - server, and enable it to run PHP. Choose a web server from the table of - contents. - - - In addition to running PHP via a web server, PHP can run from the command - line just like a .BAT script. See - - - - - - diff --git a/install/windows/legacy/sambar.xml b/install/windows/legacy/sambar.xml deleted file mode 100644 index cc4325d98e..0000000000 --- a/install/windows/legacy/sambar.xml +++ /dev/null @@ -1,87 +0,0 @@ - - - - Sambar Server on Microsoft Windows - - This section contains notes and hints specific to the - Sambar Server for Windows. - - - - You should read the manual - installation steps first! - - - - This list describes how to set up the ISAPI module to - work with the Sambar server on Windows. - - - - - - - Find the file called mappings.ini (in the config - directory) in the Sambar install directory. - - - - - Open mappings.ini and add the following line - under [ISAPI]: - - ISAPI configuration of Sambar - - - - - (This line assumes that PHP was installed in - c:\php.) - - - - - Now restart the Sambar server for the changes to take effect. - - - - - - - - If you intend to use PHP to communicate with resources which are held on - a different computer on your network, then you will need to alter the - account used by the Sambar Server Service. The default account used for - the Sambar Server Service is LocalSystem which will not have access to - remote resources. The account can be amended by using the Services - option from within the Windows Control Panel Administration Tools. - - - - - diff --git a/install/windows/legacy/xitami.xml b/install/windows/legacy/xitami.xml deleted file mode 100644 index de4683529c..0000000000 --- a/install/windows/legacy/xitami.xml +++ /dev/null @@ -1,89 +0,0 @@ - - - - Xitami on Microsoft Windows - - This section contains notes and hints specific to - Xitami on Windows. - - - - You should read the manual - installation steps first! - - - - This list describes how to set up the PHP CGI binary - to work with Xitami on Windows. - - - - Important for CGI users - - Read the faq - on cgi.force_redirect for important details. This - directive needs to be set to 0. - If you want to use $_SERVER['PHP_SELF'] you have to - enable the cgi.fix_pathinfo - directive. - - - &warn.install.cgi; - - - - - Make sure the web server is running, and point - your browser to xitamis admin console - (usually http://127.0.0.1/admin), - and click on Configuration. - - - - - Navigate to the Filters, and put the - extension which PHP should parse (i.e. .php) - into the field File extensions (.xxx). - - - - - In Filter command or script put the path and name - of your PHP CGI executable i.e. C:\php\php.exe - for PHP 4, or C:\php\php-cgi.exe for PHP 5. - - - - - Press the 'Save' icon. - - - - - Restart the server to reflect changes. - - - - - - - diff --git a/install/windows/manual.xml b/install/windows/manual.xml index 9c3174a4bc..d50d9545b1 100644 --- a/install/windows/manual.xml +++ b/install/windows/manual.xml @@ -42,8 +42,6 @@ REM Configure FastCGI Variables ]]> - - See also the old IIS installation instructions. @@ -54,7 +52,6 @@ REM Configure FastCGI Variables The Apache builds of ApacheLounge are recommended, but other options include XAMPP, WampServer and BitNami, which provide automatic installer tools. PHP can be used on Apache through mod_php or mod_fastcgi. mod_php requires a TS build of Apache built with same version of Visual C and same CPU (x86 or x64). - See also the old Apache installation instructions. @@ -75,10 +72,10 @@ REM Configure FastCGI Variables Non-Thread-Safe(NTS) - for IIS and other FastCGI web servers (Apache with mod_fastcgi) and recommended for command-line scripts - x86 - production use of PHP 5.5 and up. + x86 - for 32-bits systems. - x64 - production use of PHP 7 (unless its a 32-bit only version of Windows). PHP 5.5 and 5.6 x64 builds are experimental. + x64 - for 64-bits systems. @@ -103,4 +100,4 @@ End: vim600: syn=xml fen fdm=syntax fdl=2 si vim: et tw=78 syn=sgml vi: ts=1 sw=1 ---> \ No newline at end of file +--> diff --git a/install/windows/recommended.xml b/install/windows/recommended.xml index 0413b6ec57..600f0e501b 100644 --- a/install/windows/recommended.xml +++ b/install/windows/recommended.xml @@ -1,87 +1,93 @@ -Recommended Configuration on Windows systems - - + Recommended Configuration on Windows systems + OpCache - - -Highly Recommended that you enable OpCache. This extension is included with PHP for Windows. It compiles and optimizes PHP scripts and caches them in memory so that they aren't compiled every time the page is loaded. - - -In your php.ini, set - - Recommended OpCache configuration - + + It is highly recommended to enable OpCache. + This extension is included with PHP for Windows. + It compiles and optimizes PHP scripts and caches them in memory so that + they aren't compiled every time the page is loaded. + + + Set the &php.ini; to: + + Recommended OpCache configuration + - - - -And restart your web server. + + + And restart the web server. -For more info, see: OpCache Configuration - - - - + For more info, see: OpCache Configuration + + + WinCache + + It is recommended to use WinCache if using IIS, especially if in a shared + web hosting environment or using networked file storage (NAS). + Note that WinCache is no longer supported as of PHP 8.0.0. - -Recommended that you use WinCache if using IIS, especially if in a shared web hosting environment or using networked file storage (NAS). + All PHP Applications automatically benefit from WinCache's file cache feature. File system operations are cached in memory. -All PHP Applications automatically benefit from WinCache's file cache feature. File system operations are cached in memory. + WinCache also can cache user objects in memory and share them between php.exe or php-cgi.exe processes (share objects between requests). -WinCache also can cache user objects in memory and share them between php.exe or php-cgi.exe processes (share objects between requests). + Many major web applications have a plugin or extension or configuration option to make use of the WinCache user object cache. -Many major web applications have a plugin or extension or configuration option to make use of the WinCache user object cache. + If you need high performance, you should use the object cache in your applications. -If you need high performance, you should use the object cache in your applications. + See: http://pecl.php.net/package/WinCache to download a WinCache DLL (or tgz) to your PHP extensions directory (extensions_dir in your php.ini). -See: http://pecl.php.net/package/WinCache to download a WinCache DLL (or tgz) to your PHP extensions directory (extensions_dir in your php.ini). - -In your php.ini, set - - Recommended WinCache configuration - + Set the &php.ini; to: + + Recommended WinCache configuration + - - + + + For more info, see: + WinCache Configuration + + -For more info, see: http://php.net/manual/en/wincache.configuration.php - - - - - IIS Configuration - - In IIS Manager, Install FastCGI module and add a handler mapping for `.php` to the path to PHP-CGI.exe (not PHP.exe) + + IIS Configuration - - You may use the APPCMD command line tool to script IIS configuration. + In IIS Manager, Install FastCGI module and add a handler mapping for + `.php` to the path to PHP-CGI.exe + (not PHP.exe) - - + + You may use the APPCMD command line tool to script IIS configuration. + + + + Database + + You'll probably need a Database Server. + Popular databases provide PHP extensions to use them. + If your web site doesn't get a lot of traffic, + you can run your database server on the same server as your web server. + Many popular database servers run on Windows. + - You'll probably need a Database Server. Popular databases provide PHP extensions to use them. If your web site doesn't get a lot of traffic, you can run your database server on the same server as your web server. Many popular database servers run on Windows. - - PHP includes mysqli and pdo_mysql extensions. PHP 5.5 and 5.6 include mysql extension (deprecated in 7.0). - - See https://dev.mysql.com/downloads/windows/ - + PHP includes mysqli and pdo_mysql extensions. + + See https://dev.mysql.com/downloads/windows/ + + \ No newline at end of file +--> diff --git a/install/windows/tools.xml b/install/windows/tools.xml index 7a8b18431d..f69e13ab27 100644 --- a/install/windows/tools.xml +++ b/install/windows/tools.xml @@ -1,20 +1,24 @@ - - -PHP Installer Tools on Windows - - + PHP Installer Tools on Windows + PHP Install Tools - - If you want to setup PHP and are using IIS, the easiest way is to use Microsoft's Web Platform Installer (WebPI). - + + If you want to setup PHP and are using IIS, + the easiest way is to use Microsoft's Web Platform Installer (WebPI). + - XAMPP, WampServer and BitNami will setup PHP applications for use with Apache on Windows. - - Setting up and configuring Nginx on Windows requires a bit more configuration. See the Nginx documentation for additional setup help. - + + XAMPP, + WampServer and BitNami will setup PHP applications for use with Apache on Windows. + + + Setting up and configuring Nginx on Windows requires a bit more configuration. + See the Nginx documentation + for additional setup help. + + \ No newline at end of file +--> diff --git a/install/windows/troubleshooting.xml b/install/windows/troubleshooting.xml index 60c7a00218..07285d3904 100644 --- a/install/windows/troubleshooting.xml +++ b/install/windows/troubleshooting.xml @@ -1,25 +1,23 @@ - - -Troubleshooting PHP on Windows - - + Troubleshooting PHP on Windows + Check Temp Directory Permissions - - Right-click temp directory in File Explorer to get the permissions. - - - - For IIS, check that user IIS_User has MODIFY permission. You can get the temporary directory from the configuration or php info. - - + + + Right-click temp directory in File Explorer to get the permissions. + + + + + For IIS, check that user IIS_User has MODIFY permission. + You can get the temporary directory from the configuration or php info. + + - - - + \ No newline at end of file +--> diff --git a/language-snippets.ent b/language-snippets.ent index 5240b88538..5cf9f85b75 100644 --- a/language-snippets.ent +++ b/language-snippets.ent @@ -1597,7 +1597,7 @@ this extension is still available within DLL for this PECL extension is currently unavailable. See also the -building on Windows +building on Windows section.'> DLL files)