diff --git a/appendices/configure/index.xml b/appendices/configure/index.xml index ce6178e999..3860c36481 100644 --- a/appendices/configure/index.xml +++ b/appendices/configure/index.xml @@ -1,5 +1,5 @@ - + Configure options @@ -12,7 +12,7 @@ locations on the extension reference pages and not here. For a complete up-to-date list of configure options, run ./configure --help in your PHP source directory after running autoconf - (see also the Installation chapter). + (see also the Installation chapter). You may also be interested in reading the GNU configure documentation for information on additional configure options such as diff --git a/chapters/README b/chapters/README deleted file mode 100644 index f671e398fe..0000000000 --- a/chapters/README +++ /dev/null @@ -1,8 +0,0 @@ -Please do not modify and/or put effort into translating the install.*.xml -files and the config.xml file, since these are going to move to the install -folder, get further split, and then their content will be reorganized. So -putting time and effort now to translate these files is worthless. Also it -would be nice if you would not modify these files, since the install folder -files will replace these, and modification is expected to be done there. - - goba (at) php.net \ No newline at end of file diff --git a/chapters/config.xml b/chapters/config.xml deleted file mode 100644 index b0526e82c0..0000000000 --- a/chapters/config.xml +++ /dev/null @@ -1,263 +0,0 @@ - - - - Runtime Configuration - - - The configuration file - - - The configuration file (called php3.ini in - PHP 3, and simply &php.ini; as of PHP 4) - is read when PHP starts up. For the server module versions of PHP, - this happens only once when the web server is started. For the - CGI and CLI version, it happens on - every invocation. - - - The default location of &php.ini; is a compile time option (see the FAQ entry), but can be changed - for the CGI and CLI version with the - -c command line switch, see the chapter about using - PHP from the command line. You can also use the - environment variable PHPRC for an additional path to - search for a &php.ini; file. - - - If php-SAPI.ini exists (where SAPI is used SAPI, so the - filename is e.g. php-cli.ini or - php-apache.ini), it's used instead of &php.ini;. - - - - The Apache web server changes the directory to root at startup causing - PHP to attempt to read &php.ini; from the root filesystem if it exists. - - - - The &php.ini; directives handled by extensions are documented respectively - on the pages of the extensions themselfs. The list of - the core directives is available in the appendix. Most of the PHP - directives are listed in ini_set with change - permissions and links to documentation. For a complete list - of directives available in your PHP version, please read your well commented - &php.ini; file. Alternatively, you may find the - the latest &php.ini; from CVS - helpful too. - - - - &php.ini; example - - - - - - - - - - How to change configuration settings - - - Running PHP as an Apache module - - When using PHP as an Apache module, you can also change the - configuration settings using directives in Apache configuration - files (e.g. &httpd.conf;) and &htaccess; files. You will need - "AllowOverride Options" or "AllowOverride All" privileges to do so. - - - - With PHP 4 and PHP 5, there are several Apache directives that allow you - to change the PHP configuration from within the Apache configuration - files. For a listing of which directives are - PHP_INI_ALL, PHP_INI_PERDIR, - or PHP_INI_SYSTEM, have a look at the table - found within the ini_set documentation. - - - - - With PHP 3, there are Apache directives that correspond to each - configuration setting in the php3.ini name, - except the name is prefixed by "php3_". - - - - - - - - php_value - name - value - - - - Sets the value of the specified directive. - Can be used only with PHP_INI_ALL and PHP_INI_PERDIR type directives. - To clear a previously set value use none as the value. - - - - Don't use php_value to set boolean values. - php_flag (see below) should be used instead. - - - - - - - php_flag - name - on|off - - - - Used to set a boolean configuration directive. - Can be used only with PHP_INI_ALL and - PHP_INI_PERDIR type directives. - - - - - - php_admin_value - name - value - - - - Sets the value of the specified directive. - This can not be used in &htaccess; files. - Any directive type set with php_admin_value - can not be overridden by &htaccess; or virtualhost directives. - To clear a previously set value use none as the value. - - - - - - php_admin_flag - name - on|off - - - - Used to set a boolean configuration directive. - This can not be used in &htaccess; files. - Any directive type set with php_admin_flag - can not be overridden by &htaccess; or virtualhost directives. - - - - - - - - Apache configuration example - - - php_value include_path ".:/usr/local/lib/php" - php_admin_flag safe_mode on - - - php_value include_path ".:/usr/local/lib/php" - php_admin_flag safe_mode on - - - php3_include_path ".:/usr/local/lib/php" - php3_safe_mode on - -]]> - - - - - - PHP constants do not exist outside of PHP. For example, in - &httpd.conf; you can not use PHP constants - such as E_ALL or E_NOTICE - to set the error_reporting - directive as they will have no meaning and will evaluate to - 0. Use the associated bitmask values instead. - These constants can be used in &php.ini; - - - - - - Changing PHP configuration via the Windows registry - - When running PHP on Windows, the configuration values can be - modified on a per-directory basis using the Windows registry. The - configuration values are stored in the registry key - HKLM\SOFTWARE\PHP\Per Directory Values, - in the sub-keys corresponding to the path names. For example, configuration - values for the directory c:\inetpub\wwwroot would - be stored in the key HKLM\SOFTWARE\PHP\Per Directory - Values\c\inetpub\wwwroot. The settings for the - directory would be active for any script running from this - directory or any subdirectory of it. The values under the key - should have the name of the PHP configuration directive and the - string value. PHP constants in the values are not parsed. - - - - - Other interfaces to PHP - - Regardless of how you run PHP, you can change certain values at runtime - of your scripts through ini_set. See the documentation - on the ini_set page for more information. - - - If you are interested in a complete list of configuration settings - on your system with their current values, you can execute the - phpinfo function, and review the resulting - page. You can also access the values of individual configuration - directives at runtime using ini_get or - get_cfg_var. - - - - - - - diff --git a/chapters/install.apache.xml b/chapters/install.apache.xml deleted file mode 100644 index ac9ec7cfe8..0000000000 --- a/chapters/install.apache.xml +++ /dev/null @@ -1,422 +0,0 @@ - - - - Servers-Apache - - This section contains notes and hints specific to Apache installs - of PHP, both for Unix and - Windows versions. We also - have instructions and notes for Apache 2 - on a separate page. - - - Details of installing PHP with Apache on Unix - - You can select arguments to add to the - configure on line 10 below from the configure options. The version numbers have - been omitted here, to ensure the instructions are not incorrect. You - will need to replace the 'xxx' here with the correct values from your - files. - - - - - Installation Instructions (Apache Shared Module Version) for PHP - - - - - - - - Depending on your Apache install and Unix variant, there are many - possible ways to stop and restart the server. Below are some typical - lines used in restarting the server, for different apache/unix - installations. You should replace /path/to/ with - the path to these applications on your systems. - - - - Example commands for restarting Apache - - - - - - - The locations of the apachectl and http(s)dctl binaries often - vary. If your system has locate or - whereis or which commands, - these can assist you in finding your server control programs. - - - - Different examples of compiling PHP for apache are as follows: - - - - - - - - This will create a libphp4.so shared - library that is loaded into Apache using a LoadModule line in - Apache's &httpd.conf; file. The PostgreSQL - support is embedded into this libphp4.so - library. - - - - - - - - - - This will create a libphp4.so shared - library for Apache, but it will also create a - pgsql.so shared library that is loaded into - PHP either by using the extension directive in - &php.ini; file or by loading it explicitly in - a script using the dl function. - - - - - - - - - - This will create a libmodphp4.a library, a - mod_php4.c and some accompanying files and - copy this into the src/modules/php4 directory - in the Apache source tree. Then you compile Apache using - --activate-module=src/modules/php4/libphp4.a - and the Apache build system will create - libphp4.a and link it statically into the - httpd binary. The PostgreSQL support is - included directly into this httpd binary, - so the final result here is a single httpd - binary that includes all of Apache and all of PHP. - - - - - - - - - - Same as before, except instead of including PostgreSQL support - directly into the final httpd you will get - a pgsql.so shared library that you can load - into PHP from either the &php.ini; file or - directly using dl. - - - When choosing to build PHP in different ways, you should consider - the advantages and drawbacks of each method. Building as a shared - object will mean that you can compile apache separately, and don't - have to recompile everything as you add to, or change, PHP. - Building PHP into apache (static method) means that PHP will - load and run faster. For more information, see the Apache - webpage on DSO support. - - - - Apache's default &httpd.conf; currently ships with a section that looks - like this: - - - - - - Unless you change that to "Group nogroup" or something like that ("Group daemon" is - also very common) PHP will not be able to open files. - - - - - Make sure you specify the installed version of apxs when using - . - You must NOT use the apxs version that is in the apache sources but the one - that is actually installed on your system. - - - - - Installing PHP on Windows with Apache 1.3.x - - - 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), - the other is to use the Apache module DLL. In either case - you need to stop the Apache server, and edit your - &httpd.conf; to configure Apache to work with PHP. - - - 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 Docs for further - configuration directives. - - - - If you unziped 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: - - - - - ScriptAlias /php/ "c:/php/" - - - - - - - AddType application/x-httpd-php .php .phtml - - - - - - - Action application/x-httpd-php "/php/php.exe" - - - - - 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. - - - - - By using the CGI setup, your server is open - to several possible attacks. Please read - our CGI security - section to learn how to defend yourself from attacks. - - - - - If you would like to use PHP as a module in Apache, be sure to copy - php4ts.dll to the windows/system - (for Windows 9x/Me), winnt/system32 (for Windows - NT/2000) or windows/system32 (for Windows XP) - directory, overwriting any older file. Then you should add the following - lines to your Apache &httpd.conf; file: - - - - Open &httpd.conf; with your favorite editor and locate the - LoadModule directive and add the following line - at the end of the list for PHP 4: - LoadModule php4_module "c:/php/sapi/php4apache.dll" - or the following for PHP 5: - LoadModule php5_module "c:/php/sapi/php5apache.dll" - - - - - You may find after using the Windows installer for Apache that you need - to define the AddModule directive for - mod_php4.c. This is especially important if the - ClearModuleList directive is defined, which you will - find by scrolling down a few lines. You will see a list of - AddModule entries, add the following line - at the end of the list: - AddModule mod_php4.c For PHP 5, instead use - AddModule mod_php5.c - - - - - Search for a phrase similar to - # AddType allows you to tweak mime.types. You will - see some AddType entries, add the following line - at the end of the list: - AddType application/x-httpd-php .php. - You can choose any extension you want to parse through PHP here. .php - is simply the one we suggest. You can even include .html, and .php3 - can be added for backwards compatibility. - - - - - - - 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. - - - - There are two ways you can use the source code highlighting feature, - however their ability to work depends on your installation. If you have - configured Apache to use PHP as an SAPI module, then by adding the - following line to your &httpd.conf; (at the same place you inserted - AddType application/x-httpd-php .php, see above) you can - use this feature: - AddType application/x-httpd-php-source .phps. - - - If you chose to configure Apache to use PHP as a CGI binary, you - will need to use the show_source function. To - do this simply create a PHP script file and add this code: - <?php show_source ("original_php_script.php"); ?>. - Substitute original_php_script.php with - the name of the file you wish to show the source of. - - - - - On Win-Apache all backslashes in a path statement such - as "c:\directory\file.ext", must be converted to - forward slashes, as "c:/directory/file.ext". - - - - - - diff --git a/chapters/install.apache2.xml b/chapters/install.apache2.xml deleted file mode 100644 index 9b2c663ff1..0000000000 --- a/chapters/install.apache2.xml +++ /dev/null @@ -1,304 +0,0 @@ - - - - Servers-Apache 2.0 - - This section contains notes and hints specific to Apache 2.0 installs - of PHP, both for - Unix - and Windows versions. - - - &warn.apache2.compat; - - - You are highly encouraged to take a look at the - Apache Documentation to get - a basic understanding of the Apache 2.0 Server. - - - - PHP and Apache 2.0 compatibility notes - - The following versions of PHP are known to work with the most recent - version of Apache 2.0: - - - - PHP 4.3.0 or later available at - &url.php.downloads;. - - - - - the latest stable development version. - Get the source code - &url.php.snapshots;php4-latest.tar.gz or download binaries - for Windows - &url.php.snapshots;win32/php4-win32-latest.zip. - - - - - a prerelease version downloadable from - &url.php.prerelease;. - - - - - you have always the option to obtain PHP through - anonymous CVS. - - - - These versions of PHP are compatible to Apache 2.0.40 and later. - - - - Apache 2.0 SAPI-support started with PHP 4.2.0. - PHP 4.2.3 works with Apache 2.0.39, don't use any other version of Apache with - PHP 4.2.3. However, the recommended setup is to use PHP 4.3.0 or later with - the most recent version of Apache2. - - - All mentioned versions of PHP will work still with - Apache 1.3.x. - - - - - - PHP and Apache 2 on Linux - - Download the most recent version of - Apache 2.0 and a fitting PHP version from the above mentioned places. - This quick guide covers only the basics to get started with Apache 2.0 - and PHP. For more information read the - Apache Documentation. - The version numbers have been omitted here, to ensure the - instructions are not incorrect. You will need to replace the 'NN' here with the - correct values from your files. - - - - Installation Instructions (Apache 2 Shared Module Version) - - - - - - - - Following the steps above you will have a running Apache 2.0 with - support for PHP as SAPI module. - Of course there are many more configuration options available for both, - Apache and PHP. For more information use - ./configure --help in the corresponding source - tree. In case you wish to build a multithreaded version of Apache 2.0 - you must overwrite the standard MPM-Module prefork - either with worker or perchild. - To do so append to your configure line in step 6 above either the option - or - . Take care about - the consequences and understand what you are doing. For more information - read the Apache documentation about the - MPM-Modules. - - - - To build a multithreaded version of Apache your system must support threads. - This also implies to build PHP with experimental - Zend Thread Safety (ZTS). Therefore not all extensions might be available. - The recommended setup is to build Apache with the standard - prefork MPM-Module. - - - - - - PHP and Apache 2.0 on Windows - - Consider to read the - Windows specific notes for Apache 2.0. - - - - Apache 2.0 is designed to run on Windows NT 4.0, Windows 2000 or - Windows XP. At this time, support for Windows 9x is incomplete. - Apache 2.0 is not expected to work on those platforms at this time. - - - - Download the most recent version of - Apache 2.0 and a fitting PHP version from the above mentioned places. - Follow the Manual Installation Steps - and come back to go on with the integration of PHP - and Apache. - - - There are two ways to set up PHP to work with - Apache 2.0 on Windows. One is to use the CGI binary the other is to - use the Apache module DLL. In either case you need to stop the Apache - server, and edit your &httpd.conf; to configure Apache - to work with PHP. - - - You need to insert these three lines to your Apache &httpd.conf; - configuration file to set up the CGI binary: - - PHP and Apache 2.0 as CGI - - - - - - - If you would like to use PHP as a module in Apache 2.0, - be sure to move php4ts.dll for PHP 4, or - php5ts.dll for PHP 5, to - winnt/system32 (for Windows NT/2000) or - windows/system32 (for Windows XP), - overwriting any older file. You need to insert these two lines to your - Apache &httpd.conf; configuration file to set up the - PHP-Module for Apache 2.0: - - PHP and Apache 2.0 as Module - - - - - - - - Remember to substitute the c:/php/ for your actual - path to PHP in the above examples. Take care to use - either php4apache2.dll or - php5apache2.dll in your LoadModule directive and - notphp4apache.dll or - php5apache.dll as the latter ones are designed to - run with Apache 1.3.x. - - - - - Don't mix up your installation with dll files from - different PHP versions . You have the only choice - to use the dll's and extensions that ship with your downloaded PHP version. - - - - - - - diff --git a/chapters/install.caudium.xml b/chapters/install.caudium.xml deleted file mode 100644 index ca05f01304..0000000000 --- a/chapters/install.caudium.xml +++ /dev/null @@ -1,72 +0,0 @@ - - - - Servers-Caudium - - PHP 4 can be built as a Pike module for the - Caudium webserver. - Note that this is not supported with PHP 3. Follow the simple - instructions below to install PHP 4 for Caudium. - - - Caudium Installation Instructions - -PHP4.so. Also make sure that - caudium/server/lib/[pike-version]/PHP4.so - is present. -10. Configure the PHP Script Support module if needed. -]]> - - - - You can of course compile your Caudium module with support for the - various extensions available in PHP. See the chapter on - configure options for more details. - - - - When compiling PHP 4 with MySQL support you must make sure that - the normal MySQL client code is used. Otherwise there might be - conflicts if your Pike already has MySQL support. You do this by - specifying a MySQL install directory the - option. - - - - - diff --git a/chapters/install.commandline.xml b/chapters/install.commandline.xml deleted file mode 100644 index 339923f3f8..0000000000 --- a/chapters/install.commandline.xml +++ /dev/null @@ -1,96 +0,0 @@ - - - - Servers-CGI/Commandline - - The default is to build PHP as a CGI program. This creates a - commandline interpreter, which can be used for CGI processing, or - for non-web-related PHP scripting. If you are running a web - server PHP has module support for, you should generally go for - that solution for performance reasons. However, the CGI version - enables Apache users to run different PHP-enabled pages under - different user-ids. Please make sure you read through the Security chapter if you are going to - run PHP as a CGI. - - - As of PHP 4.3.0, some important additions have happened to PHP. A new - SAPI named CLI also exists and it has the same name as the CGI binary. - What is installed at {PREFIX}/bin/php depends on your - configure line and this is described in detail in the manual section - named Using PHP from the command - line. For further details please read that section of the manual. - - - - Testing - - If you have built PHP as a CGI program, you may test your build - by typing make test. It is always a good idea - to test your build. This way you may catch a problem with PHP on - your platform early instead of having to struggle with it later. - - - - - Benchmarking - - If you have built PHP 3 as a CGI program, you may benchmark your - build by typing make bench. Note that if - &safemode; is on by default, the benchmark may not be able to finish if - it takes longer then the 30 seconds allowed. This is because the - set_time_limit can not be used in - &safemode;. Use the max_execution_time - configuration setting to control this time for your own - scripts. make bench ignores the configuration file. - - - - make bench is only available for PHP 3. - - - - - - Using Variables - - Some server supplied - environment variables are not defined in the - current CGI/1.1 specification. - Only the following variables are defined there; everything else - should be treated as 'vendor extensions': AUTH_TYPE, - CONTENT_LENGTH, CONTENT_TYPE, - GATEWAY_INTERFACE, PATH_INFO, - PATH_TRANSLATED, QUERY_STRING, - REMOTE_ADDR, REMOTE_HOST, - REMOTE_IDENT, REMOTE_USER, - REQUEST_METHOD, SCRIPT_NAME, - SERVER_NAME, SERVER_PORT, - SERVER_PROTOCOL, and SERVER_SOFTWARE - - - - - - diff --git a/chapters/install.fhttpd.xml b/chapters/install.fhttpd.xml deleted file mode 100644 index 112a088930..0000000000 --- a/chapters/install.fhttpd.xml +++ /dev/null @@ -1,40 +0,0 @@ - - - - Servers-fhttpd - - To build PHP as an fhttpd module, answer "yes" to "Build as an - fhttpd module?" to the --with-fhttpd=[DIR] - configure option and specify the fhttpd - source base directory. The default directory is /usr/local/src/fhttpd. If you are - running fhttpd, building PHP as a module will give better - performance, more control and remote execution capability. - - - - Support for fhttpd is no longer available as of PHP 4.3.0. - - - - - diff --git a/chapters/install.general.xml b/chapters/install.general.xml deleted file mode 100644 index 19f9d2b798..0000000000 --- a/chapters/install.general.xml +++ /dev/null @@ -1,97 +0,0 @@ - - - - General Installation Considerations - - Before installing first, you need to know what do you - want to use PHP for. There are three main fields you - can use PHP, as described in the - What can PHP do? - section: - - Server-side scripting - Command line scripting - Client-side GUI applications - - - - For the first and most common form, you need three things: - PHP itself, a web server and a web browser. You - probably already have a web browser, and depending on - your operating system setup, you may also have a web - server (e.g. Apache on Linux or IIS on Windows). - You may also rent webspace at a company. This way, you - don't need to set up anything on your own, only write - your PHP scripts, upload it to the server you rent, and - see the results in your browser. - - - While setting up the server and PHP on your own, you have - two choices for the method of connecting PHP to the - server. For many servers PHP has a direct module - interface (also called SAPI). These servers include - Apache, Microsoft Internet Information Server, - Netscape and iPlanet servers. Many other servers - have support for ISAPI, the Microsoft module - interface (OmniHTTPd for example). If PHP has no - module support for your web server, you can always - use it as a CGI processor. This means you set up - your server to use the command line executable of - PHP (php.exe on Windows) to - process all PHP file requests on the server. - - - If you are also interested to use PHP for command line - scripting (e.g. write scripts autogenerating some images - for you offline, or processing text files depending - on some arguments you pass to them), you always need - the command line executable. For more information, read - the section about writing - command line PHP applications. In this case, - you need no server and no browser. - - - With PHP you can also write client side GUI applications - using the PHP-GTK extension. This is a completely - different approach than writing web pages, as you - do not output any HTML, but manage windows and objects - within them. For more information about PHP-GTK, please - visit the site dedicated to - this extension. PHP-GTK is not included in the - official PHP distribution. - - - From now on, this section deals with setting up PHP - for web servers on Unix and Windows with server module - interfaces and CGI executables. - - - Downloading PHP, the source code, and binary - distributions for Windows can be found at - &url.php.downloads;. - We recommend you to choose a - mirror nearest - to you for downloading the distributions. - - - - diff --git a/chapters/install.hpux.xml b/chapters/install.hpux.xml deleted file mode 100644 index 7c28ab5aec..0000000000 --- a/chapters/install.hpux.xml +++ /dev/null @@ -1,141 +0,0 @@ - - - - Unix/HP-UX installs - - This section contains notes and hints specific to installing PHP - on HP-UX systems. (Contributed by paul_mckay at clearwater-it dot co dot - uk). - - - - These tips were written for PHP 4.0.4 and Apache 1.3.9. - - - - - - - You need gzip, download a binary distribution from - http://hpux.connect.org.uk/ftp/hpux/Gnu/gzip-1.2.4a/gzip-1.2.4a-sd-10.20.depot.Z - uncompress the file and install using swinstall. - - - - - You need gcc, download a binary distribution from - http://gatekeep.cs.utah.edu/ftp/hpux/Gnu/gcc-2.95.2/gcc-2.95.2-sd-10.20.depot.gz. - uncompress this file and install gcc using swinstall. - - - - - You need the GNU binutils, you can download a binary distribution from - http://hpux.connect.org.uk/ftp/hpux/Gnu/binutils-2.9.1/binutils-2.9.1-sd-10.20.depot.gz. - uncompress this file and install binutils using swinstall. - - - - - You now need bison, you can download a binary distribution from - http://hpux.connect.org.uk/ftp/hpux/Gnu/bison-1.28/bison-1.28-sd-10.20.depot.gz, - install as above. - - - - - You now need flex, you need to download the source from one of the - http://www.gnu.org mirrors. It is in the non-gnu directory of the ftp - site. Download the file, gunzip, then - tar -xvf it. Go into the newly created flex directory - and run ./configure, followed by - make, and then make install. - - - If you have errors here, it's probably because gcc etc. are not in your - PATH so add them to your PATH. - - - - - Download the PHP and apache sources. - - - - - gunzip and tar -xvf them. We - need to hack a couple of files so that they can compile OK. - - - - - Firstly the configure file needs to be hacked because it seems to lose - track of the fact that you are a hpux machine, there will be a better - way of doing this but a cheap and cheerful hack is to put - lt_target=hpux10.20 on line 47286 of the configure - script. - - - - - Next, the Apache GuessOS file needs to be hacked. Under - apache_1.3.9/src/helpers change line 89 from echo - "hp${HPUXMACH}-hpux${HPUXVER}"; exit 0 to: echo - "hp${HPUXMACH}-hp-hpux${HPUXVER}"; exit 0 - - - - - You cannot install PHP as a shared object under HP-UX so you must - compile it as a static, just follow the instructions at the Apache - page. - - - - - PHP and Apache should have compiled OK, but Apache won't start. you - need to create a new user for Apache, e.g. www, or apache. You then - change lines 252 and 253 of the conf/httpd.conf in - Apache so that instead of - - -User nobody -Group nogroup - - - you have something like - - -User www -Group sys - - - This is because you can't run Apache as nobody under hp-ux. Apache and - PHP should then work. - - - - - - - - diff --git a/chapters/install.iis.xml b/chapters/install.iis.xml deleted file mode 100644 index 7045bfccfb..0000000000 --- a/chapters/install.iis.xml +++ /dev/null @@ -1,362 +0,0 @@ - - - - Servers-IIS/PWS - - This section contains notes and hints specific to IIS (Microsoft - Internet Information Server). Installing PHP for - PWS/IIS 3, - PWS 4 or newer and - IIS 4 or newer versions. - - - - Important for CGI users - - Read the faq - on cgi.force_redirect for important details. This - directive needs to be set to 0. - - - - - Windows and PWS/IIS 3 - - - The recommended method for configuring these servers is to use - the REG file included with the distribution - (pws-php4cgi.reg). You may want to edit this file and make sure - the extensions and PHP install directories match your - configuration. Or you can follow the steps below to do it - manually. - - - - These steps involve working directly with the Windows - registry. One error here can leave your system in an unstable - state. We highly recommend that you back up your registry - first. The PHP Development team will not be held responsible if - you damage your registry. - - - - - - - - Run Regedit. - - - - - Navigate to: HKEY_LOCAL_MACHINE /System - /CurrentControlSet /Services /W3Svc /Parameters - /ScriptMap. - - - - - On the edit menu select: New->String Value. - - - - - Type in the extension you wish to use for your php - scripts. For example .php - - - - - Double click on the new string value and enter the path to - php.exe in the value data field. ex: - c:\php\php.exe. - - - - - Repeat these steps for each extension you wish to associate - with PHP scripts. - - - - - - The following steps do not affect the web server installation - and only apply if you want your PHP scripts to be executed when - they are run from the command line (ex. run - c:\myscripts\test.php) or by double clicking - on them in a directory viewer window. You may wish to skip these - steps as you might prefer the PHP files to load into a text - editor when you double click on them. - - - - - - Navigate to: HKEY_CLASSES_ROOT - - - - - On the edit menu select: New->Key. - - - - - Name the key to the extension you setup in the previous - section. ex: .php - - - - - Highlight the new key and in the right side pane, double click - the "default value" and enter phpfile. - - - - - Repeat the last step for each extension you set up in the - previous section. - - - - - Now create another New->Key under - HKEY_CLASSES_ROOT and name it - phpfile. - - - - - Highlight the new key phpfile and in the - right side pane, double click the "default value" and enter - PHP Script. - - - - - Right click on the phpfile key and select - New->Key, name it Shell. - - - - - Right click on the Shell key and select - New->Key, name it open. - - - - - Right click on the open key and select - New->Key, name it - command. - - - - - Highlight the new key command and in the - right side pane, double click the "default value" and enter - the path to php.exe. ex: - c:\php\php.exe -q %1. (don't forget the - %1). - - - - - Exit Regedit. - - - - - If using PWS on Windows, reboot to reload the registry. - - - - - - PWS and IIS 3 users now have a fully operational system. IIS 3 - users can use a nifty tool - from Steven Genusa to configure their script maps. - - - - - - Windows and PWS 4 or newer - - - When installing PHP on Windows with PWS 4 or newer version, - you have two options. One to set up the PHP CGI binary, - the other is to use the ISAPI module DLL. - - - - If you choose the CGI binary, do the following: - - - - Edit the enclosed pws-php4cgi.reg - file (look into the SAPI dir) to reflect the location of - your php.exe. Backslashes should be - escaped, for example: - [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters\Script Map] ".php"="c:\\php\\php.exe" - Now merge this registery file into your system; you may do - this by double-clicking it. - - - - - In the PWS Manager, right click on a given directory you want - to add PHP support to, and select Properties. Check the 'Execute' - checkbox, and confirm. - - - - - - - If you choose the ISAPI module, do the following: - - - - Edit the enclosed pws-php4isapi.reg - file (look into the SAPI dir) to reflect the location of - your php4isapi.dll. Backslashes should - be escaped, for example: - [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters\Script Map] ".php"="c:\\php\\sapi\\php4isapi.dll" - Now merge this registery file into your system; you may do - this by double-clicking it. - - - - - In the PWS Manager, right click on a given directory you want to - add PHP support to, and select Properties. Check the 'Execute' - checkbox, and confirm. - - - - - - - - - Windows NT/2000/XP and IIS 4 or newer - - - To install PHP on an NT/2000/XP Server running IIS 4 or newer, - follow these instructions. You have two options to set up - PHP, using the CGI binary (php.exe) or with the ISAPI module. - - - - In either case, you need to start the Microsoft Management - Console (may appear as 'Internet Services Manager', either - in your Windows NT 4.0 Option Pack branch or the Control - Panel=>Administrative Tools under Windows 2000/XP). Then - right click on your Web server node (this will most probably - appear as 'Default Web Server'), and select 'Properties'. - - - - If you want to use the CGI binary, do the following: - - - - Under 'Home Directory', 'Virtual Directory', or - 'Directory', click on the 'Configuration' button, - and then enter the App Mappings tab. - - - - - Click Add, and in the Executable box, type: - c:\php\php.exe (assuming - that you have unziped PHP in c:\php\). - - - - - In the Extension box, type the file name extension you want - associated with PHP scripts. Leave 'Method exclusions' - blank, and check the Script engine checkbox. You may also - like to check the 'check that file exists' box - for a small - performance penalty, IIS (or PWS) will check that the script - file exists and sort out authentication before firing up php. - This means that you will get sensible 404 style error messages - instead of cgi errors complaining that PHP did not output any data. - - - You must start over from the previous step for each - extension you want associated with PHP scripts. - .php and .phtml - are common, although .php3 may be - required for legacy applications. - - - - - Set up the appropriate security. (This is done in Internet - Service Manager), and if your NT Server uses NTFS file system, - add execute rights for I_USR_ to the directory that contains - php.exe. - - - - - - - To use the ISAPI module, do the following: - - - - If you don't want to perform HTTP Authentication using PHP, - you can (and should) skip this step. Under ISAPI Filters, - add a new ISAPI filter. Use PHP as the filter name, and - supply a path to the php4isapi.dll. - - - - - Under 'Home Directory', click on the 'Configuration' button. - Add a new entry to the Application Mappings. Use the path - to the php4isapi.dll as the Executable, supply - .php as the extension, leave Method - exclusions blank, and check the Script engine checkbox. - - - - - Stop IIS completely (NET STOP iisadmin) - - - - - Start IIS again (NET START w3svc) - - - - - - - - diff --git a/chapters/install.iplanet.xml b/chapters/install.iplanet.xml deleted file mode 100644 index fd2a6ccde6..0000000000 --- a/chapters/install.iplanet.xml +++ /dev/null @@ -1,515 +0,0 @@ - - - - Servers-Netscape, iPlanet and SunONE - - This section contains notes and hints specific to Netscape, iPlanet and SunONE webserver - installs of PHP, both for Sun Solaris - and Windows versions. - - - From PHP 4.3.3 on you can use PHP scripts with the NSAPI module to - generate custom directory listings and - error pages. Additional functions for Apache compatibility are also available. - For support in current webservers read the - note about subrequests. - - - You can find more information about setting up PHP for the Netscape - Enterprise Server (NES) here: - &url.netscape.nsapi; - - - Installing PHP with NES/iPlanet/SunONE Webserver on Sun Solaris - - To build PHP with NES/iPlanet/SunONE webservers, enter the proper install - directory for the --with-nsapi=[DIR] option. The - default directory is usually - /opt/netscape/suitespot/. - Please also read /php-xxx-version/sapi/nsapi/nsapi-readme.txt. - - - - - - Install the following packages from - &url.sun.freeware; or another download site: - - autoconf-2.13 - automake-1.4 - bison-1_25-sol26-sparc-local - flex-2_5_4a-sol26-sparc-local - gcc-2_95_2-sol26-sparc-local - gzip-1.2.4-sol26-sparc-local - m4-1_4-sol26-sparc-local - make-3_76_1-sol26-sparc-local - - mysql-3.23.24-beta (if you want mysql support) - - perl-5_005_03-sol26-sparc-local - tar-1.13 (GNU tar) - - - - - - Make sure your path includes the proper directories - PATH=.:/usr/local/bin:/usr/sbin:/usr/bin:/usr/ccs/bin - and make it available to your system export PATH. - - - - - gunzip php-x.x.x.tar.gz (if you have a .gz dist, - otherwise go to 4). - - - - - tar xvf php-x.x.x.tar - - - - - Change to your extracted PHP directory: - cd ../php-x.x.x - - - - - For the following step, make sure - /opt/netscape/suitespot/ is - where your netscape server is installed. Otherwise, change to the - correct path and run: - - - - - - - - Run make followed by make install. - - - - - - After performing the base install and reading the appropriate readme file, - you may need to perform some additional configuration steps. - - - Configuration Instructions for NES/iPlanet/SunONE - - Firstly you may need to add some paths to the LD_LIBRARY_PATH environment - for SunONE to find all the shared libs. This can best done in the start - script for your SunONE webserver. Windows users can probably skip this - step. The start script is often located in: /path/to/server/https-servername/start. - You may also need to edit the configuration files that are - located in: /path/to/server/https-servername/config/. - - - - Add the following line to mime.types (you can do - that by the administration server): - - - - - - - - Edit magnus.conf (for servers >= 6) or - obj.conf (for servers < 6) and add the following, shlib will - vary depending on your OS, for Unix it will be something like - /opt/netscape/suitespot/bin/libphp4.so. You should - place the following lines after mime types init. - - - - (PHP >= 4.3.3) The php_ini parameter is optional but with it you can place your - &php.ini; in your webserver config directory. - - - - - Configure the default object in obj.conf - (for virtual server classes [SunONE 6.0+] in their vserver.obj.conf): - - -. -. -. -.#NOTE this next line should happen after all 'ObjectType' and before all 'AddLog' lines -Service fn="php4_execute" type="magnus-internal/x-httpd-php" [inikey=value inikey=value ...] -. -. - -]]> - - (PHP >= 4.3.3) As additional parameters you can add some special &php.ini;-values, for example you - can set a docroot="/path/to/docroot" specific to the context php4_execute - is called. For boolean ini-keys please use 0/1 as value, not "On","Off",... - (this will not work correctly), e.g. zlib.output_compression=1 instead of - zlib.output_compression="On" - - - - - This is only needed if you want to configure a directory that only consists of - PHP scripts (same like a cgi-bin directory): - - -ObjectType fn="force-type" type="magnus-internal/x-httpd-php" -Service fn=php4_execute [inikey=value inikey=value ...] - -]]> - - After that you can configure a directory in the Administration server and assign it - the style x-httpd-php. All files in it will get executed as PHP. - This is nice to hide PHP usage by renaming files to .html. - - - - - Setup of authentication: PHP authentication cannot be used with any - other authentication. ALL AUTHENTICATION IS PASSED TO YOUR PHP SCRIPT. - To configure PHP Authentication for the entire server, add the - following line to your default object: - - -AuthTrans fn=php4_auth_trans -. -. -. - -]]> - - - - - - To use PHP Authentication on a single directory, add the following: - - -AuthTrans fn=php4_auth_trans - -]]> - - - - - - - - - The stacksize that PHP uses depends on the configuration of the webserver. If you get - crashes with very large PHP scripts, it is recommended to raise it with the Admin Server - (in the section "MAGNUS EDITOR"). - - - - - Installing PHP with NES/iPlanet/SunONE on Windows - - To Install PHP as CGI (for Netscape Enterprise Server, - iPlanet, SunONE, perhaps Fastrack), do the following: - - - - - Copy php4ts.dll to your systemroot - (the directory where you installed Windows) - - - - - Make a file association from the command line. - Type the following two lines: - - - - - - - - In the Netscape Enterprise Administration Server create - a dummy shellcgi directory and remove it just after (this - step creates 5 important lines in obj.conf and allow the - web server to handle shellcgi scripts). - - - - - In the Netscape Enterprise Administration Server create - a new mime type (Category: type, - Content-Type: magnus-internal/shellcgi, File Suffix:php). - - - - - Do it for each web server instance you want PHP to run - - - - - More details about setting up - PHP as a CGI executable can be found here: - &url.netscape.cgi; - - - To Install PHP as NSAPI (for Netscape Enterprise Server, - iPlanet, SunONE, perhaps Fastrack), do the following: - - - - - Copy php4ts.dll to your systemroot - (the directory where you installed Windows) - - - - - Make a file association from the command line. - Type the following two lines: - - - - - - - - In the Netscape Enterprise Administration Server create - a new mime type (Category: type, - Content-Type: magnus-internal/x-httpd-php, File Suffix: php). - - - - - Edit magnus.conf (for servers >= 6) or - obj.conf (for servers < 6) and add the following: - You should - place the lines after mime types init. - - - - (PHP >= 4.3.3) The php_ini parameter is optional but with it you can place your - &php.ini; in your webserver config directory. - - - - - Configure the default object in obj.conf - (for virtual server classes [SunONE 6.0+] in their vserver.obj.conf): - In the <Object name="default"> - section, place this line necessarily after all 'ObjectType' - and before all 'AddLog' lines: - - - - (PHP >= 4.3.3) As additional parameters you can add some special &php.ini;-values, for example you - can set a docroot="/path/to/docroot" specific to the context php4_execute - is called. For boolean ini-keys please use 0/1 as value, not "On","Off",... - (this will not work correctly), e.g. zlib.output_compression=1 instead of - zlib.output_compression="On" - - - - - This is only needed if you want to configure a directory that only consists of - PHP scripts (same like a cgi-bin directory): - - -ObjectType fn="force-type" type="magnus-internal/x-httpd-php" -Service fn=php4_execute [inikey=value inikey=value ...] - -]]> - - After that you can configure a directory in the Administration server and assign it - the style x-httpd-php. All files in it will get executed as PHP. - This is nice to hide PHP usage by renaming files to .html. - - - - - Restart your web service and apply changes - - - - - Do it for each web server instance you want PHP to run - - - - - - More details about setting up - PHP as an NSAPI filter can be found here: - &url.netscape.nsapi; - - - - - The stacksize that PHP uses depends on the configuration of the webserver. If you get - crashes with very large PHP scripts, it is recommended to raise it with the Admin Server - (in the section "MAGNUS EDITOR"). - - - - - CGI environment and recommended modifications in php.ini - - Important when writing PHP scripts is the fact that iPlanet/SunONE/Netscape is a multithreaded web server. - Because of that all requests are running in the same process space (the space of the webserver itsself) and - this space has only one environment. If you want to get CGI variables like PATH_INFO, - HTTP_HOST etc. it is not the correct way to try this in the old PHP 3.x way with - getenv or a similar way (register globals to environment, $_ENV). - You would only get the environment of the running webserver without any valid CGI variables! - - - - Why are there (invalid) CGI variables in the environment? - - - Answer: This is because you started the webserver process from the admin server which runs the startup - script of the webserver, you wanted to start, as a CGI script - (a CGI script inside of the admin server!). This is why the environment of the started webserver - has some CGI environment variables in it. You can test this by - starting the webserver not from the administration server. Use the Unix command line as root user and - start it manually - you will see there are no CGI-like environment variables. - - - - Simply change your scripts to get CGI variables in the correct way for PHP 4.x by using the superglobal - $_SERVER. If you have older scripts which use $HTTP_HOST,..., - you should turn on register_globals in &php.ini; and change the variable order - to (important: remove "E" from it, because you do not need the environment here): - - - - - - - Special use for error pages or self-made directory listings (PHP >= 4.3.3) - - You can use PHP to generate the error pages for "404 Not Found" - or similar. Add the following line to the object in obj.conf for - every error page you want to overwrite: - - - - where XXX is the HTTP error code. Please delete any other Error - directives which could interfere with yours. - If you want to place a page for all errors that could exist, leave - the code parameter out. Your script can get the HTTP status code - with $_SERVER['ERROR_TYPE']. - - - Another possibility is to generate self-made directory listings. - Just create a PHP script which displays a directory listing and - replace the corresponding default Service line for - type="magnus-internal/directory" in obj.conf with the following: - - - - For both error and directory listing pages the original URI and - translated URI are in the variables $_SERVER['PATH_INFO'] and - $_SERVER['PATH_TRANSLATED']. - - - - Note about <function>nsapi_virtual</function> and subrequests (PHP >= 4.3.3) - - The NSAPI module now supports the nsapi_virtual function - (alias: virtual) - to make subrequests on the webserver and insert the result in the webpage. - The problem is, that this function uses some undocumented features from - the NSAPI library. - - - Under Unix this is not a problem, because the module automatically looks - for the needed functions and uses them if available. If not, nsapi_virtual - is disabled. - - - Under Windows limitations in the DLL handling need the use of a automatic - detection of the most recent ns-httpdXX.dll file. This is tested for servers - till version 6.1. If a newer version of the SunONE server is used, the detection - fails and nsapi_virtual is disabled. - - - If this is the case, try the following: - Add the following parameter to php4_init in - magnus.conf/obj.conf: - - - - where XX is the correct DLL version number. To get it, look in the server-root - for the correct DLL name. The DLL with the biggest filesize is the right one. - - - You can check the status by using the phpinfo function. - - - - But be warned: Support for nsapi_virtual is EXPERIMENTAL!!! - - - - - - diff --git a/chapters/install.linux.xml b/chapters/install.linux.xml deleted file mode 100644 index be3c70c0d4..0000000000 --- a/chapters/install.linux.xml +++ /dev/null @@ -1,43 +0,0 @@ - - - - Unix/Linux installs - - This section contains notes and hints specific to installing - PHP on Linux distributions. - - - Using Packages - - Many Linux distributions have some sort of package installation - system, such as RPM. This can assist in setting up a standard - configuration, but if you need to have a different set of features - (such as a secure server, or a different database driver), you may - need to build PHP and/or your webserver. If you are unfamiliar - with building and compiling your own software, it is worth - checking to see whether somebody has already built a packaged - version of PHP with the features you need. - - - - - diff --git a/chapters/install.macosx.xml b/chapters/install.macosx.xml deleted file mode 100644 index 051ce170df..0000000000 --- a/chapters/install.macosx.xml +++ /dev/null @@ -1,239 +0,0 @@ - - - - Unix/Mac OS X installs - - This section contains notes and hints specific to installing - PHP on Mac OS X Server. - - - Using Packages - - There are a few pre-packaged and pre-compiled versions of PHP for - Mac OS X. This can help in setting up a standard - configuration, but if you need to have a different set of features - (such as a secure server, or a different database driver), you may - need to build PHP and/or your web server yourself. If you are unfamiliar - with building and compiling your own software, it's worth - checking whether somebody has already built a packaged - version of PHP with the features you need. - - - - Compiling for OS X server - - There are two slightly different versions of Mac OS X, client and - server. The following is for OS X Server. - - - Mac OS X server install - - - - Get the latest distributions of Apache and PHP. - - - - Untar them, and run the configure program on Apache - like so. - - - - - - - - If you want the compiler to do some optimization., you may also want to - add this line: - - - - - - - - Next, go to the PHP 4 source directory and configure it. - - - - If you have any other additions (MySQL, GD, etc.), be sure to add them - here. For the string, put - in the path to your apache source directory, for example - /src/apache_1.3.12. - - - - - Type make and make install. This - will add a directory to your Apache source directory under - src/modules/php4. - - - - - Now, reconfigure Apache to build in PHP 4. - - - - You may get a message telling you that libmodphp4.a is out of date. If - so, go to the src/modules/php4 - directory inside your apache source directory and run this command: - ranlib libmodphp4.a. Then go back to the root of the - apache source directory and run the above configure - command again. That'll bring the link table up to date. Run - make and make install again. - - - - - Copy and rename the php.ini-dist file to your - bin directory from your PHP 4 - source directory: - cp php.ini-dist /usr/local/bin/php.ini - or (if your don't have a local directory) - cp php.ini-dist /usr/bin/php.ini. - - - - - - - - - - Compiling for MacOS X client - - Those tips are graciously provided by Marc Liyanage. - - - The PHP module for the Apache web server included in Mac OS X. - This version includes support for the MySQL and PostgreSQL databases. - - - NOTE: Be careful when you do this, you could screw up your Apache web server! - - - Do this to install: - - - - Open a terminal window. - - - - - Type - wget http://www.diax.ch/users/liyanage/software/macosx/libphp4.so.gz, - wait for the download to finish. - - - - - Type gunzip libphp4.so.gz. - - - - - Type sudo apxs -i -a -n php4 libphp4.so - - - - - Now type sudo open -a TextEdit /etc/httpd/httpd.conf. - TextEdit will open with the web server configuration file. Locate these - two lines towards the end of the file: (Use the Find command) - - - - Remove the two hash marks (#), then save the file and - quit TextEdit. - - - - - Finally, type sudo apachectl graceful to restart - the web server. - - - - - - PHP should now be up and running. You can test it by dropping a file into - your Sites folder which is called - test.php. Into that file, write this line: - <?php phpinfo() ?>. - - - Now open up 127.0.0.1/~your_username/test.php in your web - browser. You should see a status table with information about the PHP module. - - - - - diff --git a/chapters/install.omnihttpd.xml b/chapters/install.omnihttpd.xml deleted file mode 100644 index c6535c463d..0000000000 --- a/chapters/install.omnihttpd.xml +++ /dev/null @@ -1,105 +0,0 @@ - - - - Servers-OmniHTTPd Server - - This section contains notes and hints specific to - OmniHTTPd. - - - OmniHTTPd 2.0b1 and up for Windows - - - You need to complete the following steps to make PHP - work with OmniHTTPd. This is a CGI executable setup. - SAPI is supported by OmniHTTPd, but some tests have shown - that it is not so stable to use PHP as an ISAPI module. - - - - Important for CGI users - - Read the faq - on cgi.force_redirect for important details. This - directive needs to be set to 0. - - - - - - - - Install OmniHTTPd server. - - - - - Right click on the blue OmniHTTPd icon in the system - tray and select Properties - - - - - Click on Web Server Global Settings - - - - - On the 'External' tab, enter: virtual = .php - | actual = c:\path-to-php-dir\php.exe, and use the Add - button. - - - - - On the Mime tab, enter: - virtual = wwwserver/stdcgi | actual = .php, - and use the Add button. - - - - - Click OK - - - - - - - Repeat steps 2 - 6 for each extension you want to associate with PHP. - - - - Some OmniHTTPd packages come with built in PHP support. - You can choose at setup time to do a custom setup, and - uncheck the PHP component. We recommend you to use the latest - PHP binaries. Some OmniHTTPd servers come with PHP 4 beta - distributions, so you should choose not to set up - the built in support, but install your own. If the server - is already on your machine, use the Replace button in Step - 4 and 5 to set the new, correct information. - - - - - - diff --git a/chapters/install.openbsd.xml b/chapters/install.openbsd.xml deleted file mode 100644 index 1b81d44586..0000000000 --- a/chapters/install.openbsd.xml +++ /dev/null @@ -1,121 +0,0 @@ - - - - Unix/OpenBSD installs - - This section contains notes and hints specific to installing - PHP on OpenBSD 3.4. - - - Using Binary Packages - - Using binary packages to install PHP on OpenBSD is the recommended - and simplest method. The core package has been separated from the various - modules, and each can be installed and removed independently from the others. - The files you need can be found on your OpenBSD CD or on the FTP site. - - - The main package you need to install is php4-core-4.3.3.tgz, - which contains the basic engine (plus gettext and iconv). Next, take a look - at the module packages, such as php4-mysql-4.3.3.tgz - or php4-imap-4.3.3.tgz. You need to use the phpxs - command to activate and deactivate these modules in your &php.ini;. - - - OpenBSD Package Install Example - - - - - - Read the packages(7) - manual page for more information about binary packages on OpenBSD. - - - - Using Ports - - You can also compile up PHP from source using the ports tree. - However, this is only recommended for users familiar with OpenBSD. The PHP 4 port - is split into two sub-directories: core and extensions. The - extensions directory generates sub-packages for all of the supported - PHP modules. If you find you do not want to create some of these modules, - use the no_* FLAVOR. For example, to skip building - the imap module, set the FLAVOR to no_imap. - - - - Common Problems - - - The default install of Apache runs inside a - chroot(2) jail, which will restrict PHP scripts to - accessing files under /var/www. You will therefore need to create a - /var/www/tmp directory for PHP session files to be stored, or use an - alternative session backend. In addition, database sockets need to be placed inside the - jail or listen on the localhost interface. If you use network functions, - some files from /etc such as /etc/resolv.conf and - /etc/services will need to be moved into /var/www/etc. - The OpenBSD PEAR package automatically installs into the correct chroot directories, so - no special modification is needed there. More information on the OpenBSD Apache is available - in the OpenBSD FAQ. - - - - - The OpenBSD 3.4 package for the gd extension requires - XFree86 to be installed. If you do not wish to use some of the font features that - require X11, install the php4-gd-4.3.3-no_x11.tgz package instead. - - - - - - - Older Releases - - Older releases of OpenBSD used the FLAVORS system to compile up - a statically linked PHP. Since it is hard to generate binary packages using - this method, it is now deprecated. You can still use the old stable - ports trees if you wish, but they are unsupported by the OpenBSD team. - If you have any comments about this, the current maintainer for the port - is Anil Madhavapeddy (avsm at openbsd dot org). - - - - - diff --git a/chapters/install.otherhttpd.xml b/chapters/install.otherhttpd.xml deleted file mode 100644 index 4da9db7d65..0000000000 --- a/chapters/install.otherhttpd.xml +++ /dev/null @@ -1,38 +0,0 @@ - - - - Servers-Other web servers - - PHP can be built to support a large number of web servers. Please - - see the configure options chapter for - more details. The PHP CGI binaries are compatible with almost all - webservers supporting the CGI standard. - - - - diff --git a/chapters/install.problems.xml b/chapters/install.problems.xml deleted file mode 100644 index 3f44007d3e..0000000000 --- a/chapters/install.problems.xml +++ /dev/null @@ -1,78 +0,0 @@ - - - - - Problems? - - - Read the FAQ - - Some problems are more common than others. The most - common ones are listed in the PHP - FAQ, part of this manual. - - - - - Other problems - - - If you are still stuck, someone on the PHP installation mailing list may be - able to help you. You should check out the archive first, in case - someone already answered someone else who had the same problem as - you. The archives are available from the support page on &url.php.support;. To subscribe to the PHP installation - mailing list, send an empty mail to &email.php.install.subscribe;. - The mailing list address is &email.php.install;. - - - If you want to get help on the mailing list, please try to be - precise and give the necessary details about your environment - (which operating system, what PHP version, what web server, if - you are running PHP as CGI or a server module, &safemode;, etc...), and - preferably enough code to make others able to reproduce and test - your problem. - - - - - Bug reports - - If you think you have found a bug in PHP, please report it. The - PHP developers probably don't know about it, and unless you - report it, chances are it won't be fixed. You can report bugs - using the bug-tracking system at &url.php.bugs;. Please do not - send bug reports in mailing list or personal letters. The - bug system is also suitable to submit feature requests. - - - Read the How to report a bug - document before submitting any bug reports! - - - - - diff --git a/chapters/install.sambar.xml b/chapters/install.sambar.xml deleted file mode 100644 index cd6116ace7..0000000000 --- a/chapters/install.sambar.xml +++ /dev/null @@ -1,70 +0,0 @@ - - - - Servers-Sambar - - This section contains notes and hints specific to the - Sambar server for Windows. - - - Sambar Windows - - - 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. - - - - - - - - diff --git a/chapters/install.solaris.xml b/chapters/install.solaris.xml deleted file mode 100644 index 4fcdd2502d..0000000000 --- a/chapters/install.solaris.xml +++ /dev/null @@ -1,106 +0,0 @@ - - - - Unix/<productname>Solaris</productname> installs - - This section contains notes and hints specific to installing - PHP on Solaris systems. - - - Required software - - Solaris installs often lack C compilers and their related tools. - Read this FAQ - for information on why using GNU versions for some of these - tools is necessary. The required software is as follows: - - - - gcc (recommended, other C compilers may work) - - - - - make - - - - - flex - - - - - bison - - - - - m4 - - - - - autoconf - - - - - automake - - - - - perl - - - - - gzip - - - - - tar - - - - - GNU sed - - - - In addition, you will need to install (and possibly compile) any - additional software specific to your configuration, such as Oracle - or MySQL. - - - - Using Packages - - You can simplify the Solaris install process by using pkgadd to - install most of your needed components. - - - - - diff --git a/chapters/install.unix.xml b/chapters/install.unix.xml deleted file mode 100644 index bcce23fe83..0000000000 --- a/chapters/install.unix.xml +++ /dev/null @@ -1,162 +0,0 @@ - - - - Installation on Unix systems - - This section will guide you through the general configuration and - installation of PHP on Unix systems. Be sure to investigate any - sections specific to your platform or web server before you begin - the process. - - - Prerequisite knowledge and software: - - - - Basic Unix skills (being able to operate "make" and a C - compiler, if compiling) - - - - - An ANSI C compiler (if compiling) - - - - - flex (for compiling) - - - - - bison (for compiling) - - - - - A web server - - - - - Any module specific components (such as gd, pdf libs, etc.) - - - - - - - There are several ways to install PHP for the Unix platform, either - with a compile and configure process, or through various - pre-packaged methods. This documentation is mainly focused around - the process of compiling and configuring PHP. - - - - The initial PHP setup and configuration process is controlled by the - use of the commandline options of the configure - script. This page outlines the usage of the most common options, - but there are many others to play with. Check out the chapter on - configure options for more details. - There are several ways to install PHP: - - - - As an Apache 1.x module or - an Apache 2.x module. - - - - - As an Pike module for Caudium - - - - - For use with AOLServer, NSAPI, - phttpd, Pi3Web, Roxen, thttpd, or Zeus. - - - - - As a CGI executable - - - - - - - Apache Module Quick Reference - - - PHP can be compiled in a number of different ways, but one of - the most popular is as an Apache module. The following is a quick - installation overview. - - - - - Quick Installation Instructions for PHP 4 (Apache Module Version) - - - - - - - - - Building - - When PHP is configured, you are ready to build the CGI executable. - The command make should - take care of this. If it fails and you can't figure out why, see - the Problems section. - - - - - - diff --git a/chapters/install.windows.xml b/chapters/install.windows.xml deleted file mode 100644 index d5df3b6756..0000000000 --- a/chapters/install.windows.xml +++ /dev/null @@ -1,1176 +0,0 @@ - - - - Installation on Windows systems - - This section applies to Windows 98/Me and Windows NT/2000/XP. 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 95 - is no longer supported as of PHP 4.3.0. - - - There are two main ways to install PHP for Windows: either - manually - or by using the installer - installer. - - - If you have 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. - - - - Windows Installer - - - The Windows PHP installer is available from the downloads page at - &url.php.downloads;. This - installs the CGI version of PHP - and, for IIS, PWS, and Xitami, configures the web server as well. - - - - While the windows installer is an easy way to make - PHP work, it is restricted in many aspects, as - automatic setup of extensions for example is not supported. The whole set - of supported extensions is only available by downloading the zip binary - distribution. - - - - - Install your selected HTTP server on your system and - make sure that it works. - - - - Run the executable installer and follow the instructions provided by the - installation wizard. Two types of installation are supported - standard, - which provides sensible defaults for all the settings it can, and advanced, - which asks questions as it goes along. - - - - The installation wizard gathers enough information to set up the &php.ini; - file and configure the web server to use PHP. For IIS and also PWS on NT - Workstation, a list of all the nodes on the server with script map settings - is displayed, and you can choose those nodes to which you wish to add the - PHP script mappings. - - - - Once the installation has completed the installer will inform you if you - need to restart your system, restart the server, or just start using PHP. - - - - - Be aware, that this setup of PHP is not secure. If you would like to have - a secure PHP setup, you'd better go on the manual way, and set every - option carefully. This automatically working setup gives you an instantly - working PHP installation, but it is not meant to be used on online servers. - - - - - - Manual Installation Steps - - This install guide will help you manually install and configure PHP on your - Windows webserver. The original version of this guide was compiled by - &link.bob;, and can be found at - &url.win32install;. - You need to download the zip binary distribution from the downloads page at - &url.php.downloads;. - - - - PHP 4 for Windows comes in three flavours - a CGI executable (php.exe), a - CLI executable (sapi/php.exe) and some other SAPI modules: - - - php4apache.dll - Apache 1.3.x module - - - php4apache2.dll - Apache 2.0.x module - - - php4isapi.dll - ISAPI Module for ISAPI compliant - webservers like IIS 4.0/PWS 4.0 or newer. - - - php4nsapi.dll - Netscape/iPlanet module - - - The latter form is new to PHP 4, and provides significantly improved - performance and some new functionality. The CLI version is designed to use - PHP for command line scripting. More information about CLI is available in - the chapter about - using PHP from the command line - - - - The SAPI modules have been significantly improved in the 4.1 release, - however, you may find that you encounter possible server errors or - other server modules such as ASP failing, in older systems. - - - - DCOM and MDAC requirements - - If you choose one of the SAPI modules and use - Windows 95, be sure to download and install the DCOM - update from the Microsoft DCOM pages. - If you use Microsoft Windows 9x/NT4 download the - latest version of the Microsoft Data Access Components (MDAC) for your - platform. MDAC is available at &url.mdac;. - - - - The following steps should be performed on all installations before any - server specific instructions. - - - - Extract the distribution file to a directory of your choice, - c:\ is a good start. The zip package expands to a - foldername like php-4.3.1-Win32 which is assumed to - be renamed to php. For the sake of convenience and - to be version independent the following steps assume your extracted - version of PHP lives in c:\php. You might choose - any other location but you probably do not want to use a path in which - spaces are included (for example: - C:\Program Files\PHP is not a good idea). Some web - servers will crash if you do. The structure of your directory you - extracted the zip file will look like: - - - - - - Windows system directory - | | - | |-expat.dll - | | - | |-fdftk.dll - | | - | |-... - | - +--extensions -- extension dlls for PHP - | | - | |-php_bz2.dll - | | - | |-php_cpdf.dll - | | - | |-.. - | - +--mibs -- support files for SNMP - | - | - +--openssl -- support files for Openssl - | - | - +--pdf-related -- support files for PDF - | - | - +--sapi -- SAPI dlls - | | - | |-php4apache.dll - | | - | |-php4apache2.dll - | | - | |-php4isapi.dll - | | - | |-.. - | - |-install.txt - | - |-.. - | - |-php.exe -- CGI executable - | - |-.. - | - |-php.ini-dist - | - |-php.ini-recommended - | - |-php4ts.dll -- main dll --> Windows system directory - | - |-... - - -]]> - - - - - The CGI binary - c:\php\php.exe -, the CLI binary - - c:\php\cli\php.exe -, and the SAPI modules - - c:\php\sapi\*.dll - rely on the main dll - c:\php\php4ts.dll. You have to make sure, that this - dll can be found by your PHP installation. The search order for this dll - is as follows: - - - The same directory from where php.exe is called. - In case you use a SAPI module the same directory from where your - webserver loads the dll (e.g. php4apache.dll). - - - Any directory in your Windows PATH environment variable. - - - - - - The best bet is to make php4ts.dll available, - regardless which interface (CGI or SAPI module) you plan to use. To do so, - you have to copy this dll to a directory on your Windows path. The best - place is your Windows system directory: - - - C:\Windows\System for Windows 9x/ME - - - C:\WINNT\System32 for Windows NT/2000 or - C:\WINNT40\System32 for NT/2000 server - - - C:\Windows\System32 for Windows XP - - - If you plan to use a SAPI module from c:\php\sapi - and do not like to copy dlls to your Windows system directory, you have - the alternative choice to simply copy php4ts.dll to - the sapi folder of your extracted zip package, - c:\php\sapi. - - - - - The next step is to set up a valid configuration file for PHP, &php.ini;. - There are two ini files distributed in the zip file, - php.ini-dist and - php.ini-recommended. We advise you to use - php.ini-recommended, because we optimized the - default settings in this file for performance, and security. Read this - well documented file carefully and in addition study the - ini settings and set every - element manually yourself. If you would like to achieve the best - security, then this is the way for you, although PHP works fine with - these default ini files. Copy your chosen ini-file to a directory where - PHP is able to find and rename it to &php.ini;. By default PHP searches - &php.ini; in your Windows directory: - - - On Windows 9x/ME/XP copy your chosen ini file to your - %WINDIR%, which is typically - C:\Windows. - - - On Windows NT/2000 copy your chosen ini file to your - %WINDIR% or %SYSTEMROOT%, - which is typically C:\WINNT or - C:\WINNT40 for NT/2000 servers. - - - - - - - If you're using NTFS on Windows NT, 2000 or XP, make sure that - the user running the webserver has read permissions to your - &php.ini; (e.g. make it readable by Everyone). - - - - - - The following steps are optional. - - - - Edit your new &php.ini; file. - If you plan to use OmniHTTPd, - do not follow the next step. Set the - doc_root to point to your webservers - document_root. For example: - - - - - - - - - - Choose which extensions you would like to load when PHP starts. See - the section about - Windows extensions, - about how to set up one, and what is already built in. Note that on - a new installation it is advisable to first get PHP working and tested - without any extensions before enabling them in &php.ini;. - - - - - On PWS and IIS, you can set the - browscap configuration setting - to point to: - c:\windows\system\inetsrv\browscap.ini on - Windows 9x/Me, - c:\winnt\system32\inetsrv\browscap.ini on - NT/2000, and - c:\windows\system32\inetsrv\browscap.ini - on XP. - - - - - - Following this instructions you are done with the basic steps to setup PHP - on Windows. The next step is to choose a webserver and enable it to run - PHP. Installation instructions for the following webservers are available: - - - - .. the Windows server family, Personal - Web server (PWS) 3 and 4 or newer; Internet Information Server (IIS) 3 - and 4 or newer. - - - - - .. the Apache servers - Apache 1.3.x, and - Apache 2.x. - - - - - - .. the - Netscape/iPlanet servers. - - - - - - .. the OmniHTTPd server. - - - - - - .. the Sambar server. - - - - - - .. the Xitami server. - - - - - - - - Building from source - - Before getting started, it is worthwhile answering the question: - "Why is building on Windows so hard?" Two reasons come to mind: - - - - - Windows does not (yet) enjoy a large community of developers - who are willing to freely share their source. As a direct - result, the necessary investment in infrastructure required - to support such development hasn't been made. By and large, - what is available has been made possible by the porting of - necessary utilities from Unix. Don't be surprised if some of - this heritage shows through from time to time. - - - - - Pretty much all of the instructions that follow are of the - "set and forget" variety. So sit back and try follow the - instructions below as faithfully as you can. - - - - - - &reftitle.required; - - To compile and build PHP you need a Microsoft - Development Environment. Microsoft Visual C++ 6.0 is recommended. - To extract the downloaded files you need a extraction utility - (e.g.: Winzip). If you don't already have an unzip utility, you - can get a free version from InfoZip. - - - Before you get started, you have to download... - - - - - ..the win32 buildtools from the PHP site - at &url.win32.buildtools;. - - - - - ..the source code for the DNS name resolver used by PHP - from - &url.win32.dnsresolver;. This is a replacement for the - resolv.lib library included in - win32build.zip. - - - - - If you plan to compile PHP as a Apache - module you will also need the Apache - sources. - - - - - Finally, you are going to need the source to PHP 4 itself. You can get - the latest development version using - anonymous CVS, a - snapshot or the most recent released - source tarball. - - - - - Putting it all together - - After downloading the required packages you have to extract them in a - proper place. - - - - Create a working directory where all files end up after extracting, e.g: - C:\work. - - - - - Create the directory win32build under your - working directory (C:\work) and unzip - win32build.zip into it. - - - - - Create the directory bindlib_w32 under your - working directory (C:\work) and unzip - bindlib_w32.zip into it. - - - - - Extract the downloaded PHP source code into your working directory - (C:\work). - - - - Following this steps your directory structure looks like this: - - - - - - Create the directories c:\usr\local\lib. Copy - bison.simple from c:\work\win32build\bin - to c:\usr\local\lib. - - - - Cygwin users may omit the last - step. A properly installed Cygwin environment provides the mandatory - files bison.simple and - bison.exe. - - - - - - Configure MVC ++ - - The next step is to configure MVC ++ to prepare for compiling. - Launch Microsoft Visual C++, and from the menu select - Tools => Options. In the dialog, select the - directories tab. Sequentially change the dropdown - to Executables, Includes, and Library files. Your entries should look - like this: - - - - Executable files: c:\work\win32build\bin, - Cygwin users: cygwin\bin - - - - - Include files: c:\work\win32build\include - - - - - Library files: c:\work\win32build\lib - - - - - - - - Build resolv.lib - - You must build the resolv.lib library. - Decide whether you want to have debug symbols available - (bindlib - Win32 Debug) or not (bindlib - Win32 Release). - Build the appropriate configuration: - - - - For GUI users, launch VC++, and then select File => Open - Workspace, navigate to c:\work\bindlib_w32 and - select bindlib.dsw. Then select Build=>Set - Active Configuration and select the desired configuration. - Finally select Build=>Rebuild All. - - - - - For command line users, make sure that you either have the C++ - environment variables registered, or have run - vcvars.bat, and then execute one of the following - commands: - - - - - msdev bindlib.dsp /MAKE "bindlib - Win32 Debug" - - - - - msdev bindlib.dsp /MAKE "bindlib - Win32 Release" - - - - - - At this point, you should have a usable resolv.lib - in either your c:\work\bindlib_w32\Debug or - Release subdirectories. Copy this file into your - c:\work\win32build\lib directory over the file - by the same name found in there. - - - - - Compiling - - The best way to get started is to build the CGI version. - - - - - For GUI users, launch VC++, and then select File => Open - Workspace and select c:\work\php-4.x.x\win32\php4ts.dsw - . Then select Build=>Set Active - Configuration and select the desired configuration, either - php4ts - Win32 Debug_TS or - php4ts - Win32 Release_TS. Finally select - Build=>Rebuild All. - - - - - For command line users, make sure that you either have - the C++ environment variables registered, or have run - vcvars.bat, and then execute one of the - following commands from the c:\work\php-4.x.x\win32 - directory: - - - - - msdev php4ts.dsp /MAKE "php4ts - Win32 Debug_TS" - - - - - msdev php4ts.dsp /MAKE "php4ts - Win32 Release_TS" - - - - - At this point, you should have a usable php.exe - in either your c:\work\php-4.x.x.\Debug_TS or - Release_TS subdirectories. - - - - - - - It is possible to do minor customization to the build process by editing - the main/config.win32.h file. For example you can - change the default location of &php.ini;, the built-in extensions, and the - default location for your extensions. - - - Next you may want to build the CLI version which is designed to use - PHP from the command line. - The steps are the same as for building the CGI version, except you have - to select the php4ts_cli - Win32 Debug_TS or - php4ts_cli - Win32 Release_TS project file. After a - successful compiling run you will find the php.exe - in either the directory Release_TS\cli\ or - Debug_TS\cli\. - - - - If you want to use PEAR and the comfortable command line installer, - the CLI-SAPI is mandatory. For more information about PEAR and the - installer read the documentation at the - PEAR website. - - - - In order to build the SAPI module (php4isapi.dll) - for integrating PHP with Microsoft IIS, set your active configuration to - php4isapi-whatever-config and build the desired dll. - - - - - - Installation of Windows extensions - - After installing PHP and a webserver 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_' in PHP 4 (and - 'php3_' in PHP 3). This prevents confusion between PHP extensions - and their supporting libraries. - - - - In PHP 4.3.1 BCMath, Calendar, COM, Ctype, FTP, MySQL, ODBC, Overload, - PCRE, Session, Tokenizer, WDDX, XML and Zlib support is - built in. You don't need to load any additional - extensions in order to use these functions. See your distributions - README.txt or install.txt - or this table - for a list of built in modules. - - - - - The default location PHP searches for extensions is - c:\php4\extensions. 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. Please do not - forget the last backslash. 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 ; form the extension you want to load. - - Enable <link linkend="ref.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 - c:\php\dlls\ folder but some, for example Oracle - (php_oci8.dll) require DLLs which are not bundled - with the distribution package. Copy the bundled DLLs from - c:\php\dlls folder to your Windows - PATH, safe places are: - - c:\windows\system for Windows 9x/Me - c:\winnt\system32 for Windows NT/2000 - c:\windows\system32 for Windows XP - - If you have them already installed on your system, overwrite them only - if something doesn't work correctly (Before overwriting them, it is a - good idea to make a backup of them, or move them to another folder - - just in case something goes wrong). - - - - - - If you are running a server module version of PHP - remember to restart your webserver 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 - Built in since PHP 4.0.3 - - - php_cpdf.dll - ClibPDF functions - None - - - php_crack.dll - Crack functions - None - - - php3_crypt.dll - Crypt functions - unknown - - - php_ctype.dll - ctype family functions - Built in since PHP 4.3.0 - - - php_curl.dll - CURL, Client URL library functions - Requires: libeay32.dll, - ssleay32.dll (bundled) - - - php_cybercash.dll - Cybercash payment functions - PHP <= 4.2.0 - - - php_db.dll - DBM functions - Deprecated. Use DBA instead (php_dba.dll) - - - php_dba.dll - DBA: DataBase (dbm-style) - Abstraction layer functions - None - - - php_dbase.dll - dBase functions - None - - - php3_dbm.dll - Berkeley DB2 library - unknown - - - php_dbx.dll - dbx functions - - - - php_domxml.dll - DOM XML functions - - PHP <= 4.2.0 requires: libxml2.dll (bundled) - PHP >= 4.3.0 requires: iconv.dll (bundled) - - - - php_dotnet.dll - .NET functions - PHP <= 4.1.1 - - - php_exif.dll - Read EXIF headers from JPEG - None - - - php_fbsql.dll - FrontBase functions - PHP <= 4.2.0 - - - php_fdf.dll - FDF: Forms Data Format functions. - Requires: fdftk.dll (bundled) - - - php_filepro.dll - filePro functions - Read-only access - - - php_ftp.dll - FTP functions - Built-in since PHP 4.0.3 - - - php_gd.dll - GD library image functions - - Removed in PHP 4.3.2. Also note that truecolor functions are not - available in GD1, instead, use php_gd2.dll. - - - - 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), - PHP >=4.2.1 iconv.dll - - - php_ifx.dll - Informix functions - Requires: Informix libraries - - - php_iisfunc.dll - IIS management functions - None - - - php_imap.dll - IMAP POP3 and NNTP functions - PHP 3: php3_imap4r1.dll - - - php_ingres.dll - Ingres II functions - Requires: Ingres II libraries - - - php_interbase.dll - InterBase functions - Requires: gds32.dll (bundled) - - - php_java.dll - Java functions - PHP <= 4.0.6 requires: jvm.dll (bundled) - - - php_ldap.dll - LDAP functions - - PHP <= 4.2.0 requires libsasl.dll (bundled), - PHP >= 4.3.0 requires libeay32.dll, - ssleay32.dll (bundled) - - - - php_mbstring.dll - Multi-Byte String functions - None - - - php_mcrypt.dll - Mcrypt Encryption functions - Requires: libmcrypt.dll - - - php_mhash.dll - Mhash functions - PHP >= 4.3.0 requires: libmhash.dll (bundled) - - - php_mime_magic.dll - Mimetype functions - Requires: magic.mime (bundled) - - - php_ming.dll - Ming functions for Flash - None - - - php_msql.dll - mSQL functions - Requires: msql.dll (bundled) - - - php3_msql1.dll - mSQL 1 client - unknown - - - php3_msql2.dll - mSQL 2 client - unknown - - - php_mssql.dll - MSSQL functions - Requires: ntwdblib.dll (bundled) - - - php_mysql.dll - MySQL functions - Needed for PHP 5 and requires libmySQL.dll - (bundled), Built into PHP 4. - - - - php3_nsmail.dll - Netscape mail functions - unknown - - - php3_oci73.dll - Oracle functions - unknown - - - php_oci8.dll - Oracle 8 functions - Requires: Oracle 8.1+ client libraries - - - php_openssl.dll - OpenSSL functions - Requires: libeay32.dll (bundled) - - - php_oracle.dll - Oracle functions - Requires: Oracle 7 client libraries - - - php_overload.dll - Object overloading functions - Built in since PHP 4.3.0 - - - php_pdf.dll - PDF functions - None - - - php_pgsql.dll - PostgreSQL functions - None - - - php_printer.dll - Printer functions - None - - - php_shmop.dll - Shared Memory functions - None - - - php_snmp.dll - SNMP get and walk functions - NT only! - - - php_sockets.dll - Socket functions - None - - - php_sybase_ct.dll - Sybase functions - Requires: Sybase client libraries - - - php_tokenizer.dll - Tokenizer functions - Built in since PHP 4.3.0 - - - php_w32api.dll - W32api functions - None - - - php_xmlrpc.dll - XML-RPC functions - PHP >= 4.2.1 requires: iconv.dll (bundled) - - - php_xslt.dll - XSLT functions - - PHP <= 4.2.0 requires sablot.dll, - expat.dll (bundled). PHP >= 4.2.1 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 - Built in since PHP 4.3.0 - - - -
- - - - - diff --git a/chapters/install.xitami.xml b/chapters/install.xitami.xml deleted file mode 100644 index 9f5e72f4a5..0000000000 --- a/chapters/install.xitami.xml +++ /dev/null @@ -1,83 +0,0 @@ - - - - Servers-Xitami - - This section contains notes and hints specific to - Xitami. - - - Xitami for Windows - - - 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. - - - - - - - - Make sure the webserver 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 executable i.e. c:\php\php.exe. - - - - - Press the 'Save' icon. - - - - - Restart the server to reflect changes. - - - - - - - - diff --git a/chapters/intro.xml b/chapters/intro.xml index 804daab88c..b6a853cbc2 100644 --- a/chapters/intro.xml +++ b/chapters/intro.xml @@ -1,5 +1,5 @@ - + Introduction @@ -91,7 +91,7 @@ viewing the PHP page through the server. All these can run on your home machine if you are just experimenting with PHP programming. See the - installation instructions + installation instructions section for more information. @@ -229,7 +229,7 @@ As you can see this page is not enough to list all the features and benefits PHP can offer. Read on in - the sections about installing + the sections about installing PHP, and see the function reference part for explanation of the extensions mentioned here. diff --git a/chapters/tutorial.xml b/chapters/tutorial.xml index be29a55826..0ea7022081 100644 --- a/chapters/tutorial.xml +++ b/chapters/tutorial.xml @@ -1,5 +1,5 @@ - + A simple tutorial @@ -44,7 +44,7 @@ You can either install these individually or choose a simpler way. Our - manual has installation instructions for + manual has installation instructions for PHP (assuming you already have some webserver set up). In case you have problems with installing PHP yourself, we would suggest you ask your questions on our installation @@ -120,7 +120,7 @@ for download, or you see the whole file as text, chances are that the server you are on does not have PHP enabled, or is not configured properly. Ask your administrator to enable it for you using the - Installation chapter + Installation chapter of the manual. If you are developing locally, also read the installation chapter to make sure everything is configured properly. Make sure that you access the file via http with the server diff --git a/install/windows/manual.xml b/install/windows/manual.xml index ba57284c4a..157b1ecc9c 100644 --- a/install/windows/manual.xml +++ b/install/windows/manual.xml @@ -1,5 +1,5 @@ - + Manual Installation Steps @@ -41,7 +41,7 @@ If you use Microsoft Windows 98/NT4 download the latest version of the Microsoft Data Access Components (MDAC) for your platform. MDAC is available at &url.mdac;. - This requirement exists because ODBC is + This requirement exists because ODBC is built into the distributed Windows binaries. diff --git a/language/functions.xml b/language/functions.xml index 69515e4cda..95116dd021 100644 --- a/language/functions.xml +++ b/language/functions.xml @@ -1,5 +1,5 @@ - + Functions @@ -547,7 +547,7 @@ $foo->$funcname(); // This calls $foo->Variable() extensions are loaded into your PHP. Also note that many extensions are enabled by default and that the PHP manual is split up by extension. See the configuration, - installation, and individual + installation, and individual extension chapters, for information on how to setup your PHP. diff --git a/reference/mbstring/configure.xml b/reference/mbstring/configure.xml index a9e6d89dff..efc6eca76a 100644 --- a/reference/mbstring/configure.xml +++ b/reference/mbstring/configure.xml @@ -1,12 +1,12 @@ - +
&reftitle.install; mbstring is a non-default extension. This means it is not enabled by default. You must explicitly enable the module with the configure option. See the - Install section for details. + Install section for details. The following configure options are related to the