By default, PHP saves all the data of the user's sessions in a file in the directory specified by the session.save_path INI option (see http://www.php.net/session). When you execute PHP from a CD/DVD on a unknown PC, you have to set the session.save_path at runtime to make sessions work correctly. You can achieve this by calling the session_save_path() (see http://www.php.net/manual/en/function.session-save-path.php) function before starting a session.

Here it is an example of session_save_path() usage:

<?php
session_save_path(dwebpro_getvar('DWEBPRO_TEMP'));
session_start();
?>

In the above sample, PHP will save the session data in the temporary directory specified by the DWEBPRO_TEMP internal constant (refer to the DWebPro Internal Constants topic). Using the DWEBPRO_TEMP internal constant guarantees that the temporary directory will be readable and writable by the user that is executing DWebPro, even if that user has low privileges (for example, a user that is a member of the Users or Guest group under Windows 2000 or Windows XP).

Of course you can. All of our preconfigured PHP packages (see Add-On Packages topic) include the standard PHP extensions and the official collection of PECL modules. To enable a PHP extension, you have to open the php.ini file and add an extension statement for the extension you want to enable. For example, if you want to activate the GD extension, add the following code in the php.ini file:

extension=php_gd2.dll

If you are using PHP as ISAPI module you have to stop DWebPro and restart it to make the PHP engine aware of the configuration change.

We suggest that you to add this code in the Dynamic Extensions section. To correctly identify the php.ini to modify, refer to the Where is the php.ini File? FAQ. You can find more information on PHP extension activation in the PHP official manual located online at: http://www.php.net/manual/en/install.pecl.php.

When you install PHP with one of our preconfigured packages (see Add-On Packages topic), you can decide to install it as ISAPI or CGI. We recommend you to install PHP as ISAPI because it is much faster than CGI, especially when you execute DWebPro and PHP on a CD/DVD.

Depending on the way you have installed PHP, you can find the php.ini file in two different locations:

• With PHP installed as ISAPI, the php.ini file is read from the deploy folder

• With PHP installed as CGI, the php.ini file is read from the PHP folder (for example, deploy\engine\php5)

If you are using PHP as ISAPI module you have to stop DWebPro and restart it to make the PHP engine aware of the configuration change.

Our preconfigured packages are provided with the default PHP configuration, except for some minor changes required for the stand alone behavior. This configuration includes the following directive:

register_globals = Off

The register_globals directive (see http://www.php.net/register_globals) default value has been changed from ON to OFF beginning with PHP 4.2.0 (on 22 April 2002) due to security issues that it can raise. If your code still relies on global variables like $PHP_SELF or $GLOBALS['PHP_SELF'], you have to enable the register_globals directive in the php.ini file to make it work correctly. Refer to the Where is the php.ini File? FAQ for help in identifying the php.ini file to modify.

If you are using PHP as ISAPI module you have to stop DWebPro and restart it to make the PHP engine aware of the configuration change.

Our preconfigured packages are provided with the default PHP configuration, except for some minor changes required for the stand alone behavior. This configuration includes the following directives:

display_errors = Off
display_startup_errors = Off

With this configuration, PHP does not return any error message that can help you to solve the problem. To correct this, edit the php.ini file by setting the above directives as follows:

display_errors = On
display_startup_errors = On

Check the Where is the php.ini File? FAQ for help in identifying the php.ini file to modify.

If you are using PHP as ISAPI module you have to stop DWebPro and restart it to make the PHP engine aware of the configuration change.

This error message is raised when the PHP engine is trying to load an extension compiled for a different version of PHP (i.e. using a PHP 4.4 extension with PHP 5).

If the xxxxx module name specified in the warning message is DWebPro or registry, you can solve the problem following these steps:

1. Close DWebPro

2. Copy the PHP extensions from the extensions folder into the PHP extensions directory:

For PHP 4 copy php4_dwebpro.dll and php4_registry.dll into deploy\engine\php4\extensions.
For PHP 5.0 copy php5_dwebpro.dll and php5_registry.dll into deploy\engine\php5\ext.
For PHP 5.1 copy php51_dwebpro.dll and php51_registry.dll into deploy\engine\php5\ext.
For PHP 5.2 copy php52_dwebpro.dll and php52_registry.dll into deploy\engine\php5\ext.

Our preconfigured packages are provided with the default PHP configuration, except for some minor changes required for the stand alone behavior. This configuration includes the following directive:

error_reporting  =  E_ALL

This directive tells PHP to show any error, warning, or notice encountered by the PHP scripts. If you prefer not to see these notices, edit the php.ini file and set the error_reporting directive as follows:

error_reporting  =  E_ALL & ~E_NOTICE

You can find more information about error reporting in the PHP online manual (see http://www.php.net/error_reporting and http://www.php.net/manual/en/ref.errorfunc.php). Refer to the Where is the php.ini File? FAQ for help in identifying the php.ini file to modify.

If you are using PHP as ISAPI module you have to stop DWebPro and restart it to make the PHP engine aware of the configuration change.

DWebPro includes a stand alone SMTP server that enables you to send emails directly from the hosted Web site as you do on the Internet.

By default, DWebPro starts the SMTP server on the first empty port to avoid conflicts with other servers running on the same machine. If you want to send an email from your PHP code using the mail() function (see http://www.php.net/manual/en/function.mail.php), you need to first set the smtp_port directive with the port value on which the DWebPro SMTP server is listening. Here is sample PHP code that shows you how to achieve this:

<?php
ini_set('smtp_port', dwebpro_getvar('DWEBPRO_SMTPSERVER_PORT'));
?>

After this, you can use the mail() function exactly as you usually do.

Note that, to send emails through the DWebPro SMTP Server, you have to configure DWebPro to start the SMTP server (refer to the SMTP Server topic).

DWebPro supports almost all of the commercial and free PHP encoders available on the market, such as:

• Ioncube - http://www.ioncube.com/

• Zend Encoder – http://www.zend.com/

• SourceGuardian - http://www.sourceguardian.com/

• PHTML Encoder - http://www.rssoftlab.com/phpenc.php

• eAccelerator - http://eaccelerator.net/

• phpSHIELD - http://www.phpshield.com/

• Nu-Coder - http://www.nusphere.com/

DWebPro also includes the DWebPro Encoder Software, which is a PHP/ASP Classic 3.0 encoder that provides an entry level solution for source code protection.

Moving a Web site from one server to another typically results in problems related to includes and paths. The biggest problem is related to the use of absolute paths for inclusion and recursive inclusions.

There are various solutions to help solve the includes issue.

You can change your code to use something like the following for includes/requires:

<?php
include(dirname(__FILE__) . '/folder/include.php');
// or
include(dirname(__FILE__) . '/../include.php');
?>

Using dirname(__FILE__) you can create absolute paths relative to the folder of the current file. In this way the code will work in any environment, with any include_path directive.

An alternative is to set the PHP include_path directive at runtime to fit the new environment, like this:

<?php
ini_set('include_path', dirname(__FILE__ ) . PATH_SEPARATOR .
ini_get('include_path'));
?>

Sometimes, especially when using CMS or third party scripts, you have to edit a configuration file that contains references to absolute paths and URLs. Here is an excerpt from the Moodle (http://moodle.org/) config.php file:

$CFG->dirroot = '/home/example/public_html/moodle';

This way of configuring Web scripts works very well when you install the scripts on a Web server for the Internet. However, when you have to distribute the same script to hundreds or thousands of different machines, you have to set these configuration fields at runtime because fixed values will not work everywhere (such as because of the change of the CD/DVD drive letter and so on).

Under DWebPro there are two main ways you can achieve this runtime configuration task. The first one is the same used for the includes and consists of the use of dirname(__FILE__):

$CFG->dirroot   = dirname(__FILE__);

The second way uses DWebPro's internal functions and constants:

$CFG->dirroot   = dwebpro_getvar('DWEBPRO_DOCUMENTROOT') . '/moodle';

Another typical issue using third party scripts is related to absolute URLs. Here is another excerpt from the Moodle (http://moodle.org/) config.php file:

$CFG->wwwroot   = 'http://example.com/moodle';

By default, DWebPro starts the primary Web server on the first empty port to avoid conflicts with other servers running on the same machine. DWebPro also allows you to set a more user friendly domain name that will be shown to the user in the Web browser address bar. With these features in use, the absolute URL of the hosted Web site is not fixed and should be set at runtime. Here is how you can achieve this:

$CFG->wwwroot   = 'http://' . dwebpro_getvar('DWEBPRO_HOSTNAME') . ':' .
dwebpro_getvar('DWEBPRO_WEBSERVER_PORT') . '/moodle';

ImageMagick (see http://www.imagemagick.org/) is "a software suite to create, edit, and compose bitmap images." Many CMS and Web scripts use ImageMagick for runtime image manipulation, one CMS of which is Typo3 (see http://typo3.org/). For installing ImageMagick for Typo3, follow these steps:

1. Download the ImageMagick binary from http://typo3.sunsite.dk/software/windows/imagemagick-win-4.2.9.zip.

2. Uncompress the imagemagick-win-4.2.9.zip file contents into a subfolder of the deploy directory (such as deploy\engine\imagemagick).

3. Edit the Typo3 configuration and set the im_path directive. For instance you can set it as follows:

   'im_path' => dwebpro_getvar('DWEBPRO_PATH') . '/engine/imagemagick',

4. The last step is to edit the entire Typo3 code to replace any hard references to the typo3temp directory with a constant (such as TYPO3_TEMP) and define this constant in the configuration file as follows:

   define('TYPO3_TEMP', dwebpro_getvar('DWEBPRO_TEMP') . '/typo3temp');

This last step is required because Typo3 code contains hard coded references to the typo3temp folder and there isn't any configuration field that provides a way to change these references.

When running Typo3 from CD/DVD, the typo3temp folder will not be writable and this will prevent the Web application from executing correctly.

The "Your PHP installation does not support PostgreSQL. You need to recompile PHP using the --with-pgsql configure option." error message can be solved by editing the php.ini file and activating the PostgreSQL extension.

To do this, open the php.ini file and search for the following line:

;extension=php_pgsql.dll

Replace that line with:

extension=php_pgsql.dll

You can find more information on PHP extension activation in the official PHP manual (http://www.php.net/manual/en/install.pecl.php). Refer to the Where is the php.ini File? FAQ for help in identifying the php.ini file to modify.

If you are using PHP as ISAPI module you have to stop DWebPro and restart it to make the PHP engine aware of the configuration change.

This error occurs when DWebPro finds an incompatible libmysql.dll file in the Windows search path. You can solve this problem by coping libmysql.dll file from the PHP folder (for example, deploy\engine\php5) into the deploy folder.

DWebPro sets the SERVER_SOFTWARE server variable with the "DWebPro" strings. You can use a code like the following to identify when you web application is running under DWebPro or another web server.

<?php
if (preg_match('#dwebpro#si', @$_SERVER['SERVER_SOFTWARE'])) {
    print('This application is running under DWebPro!');
} else {
    print('This application is <b>not running</b> under DWebPro!');
}
?>

This feature is useful if you want to use the same code base for your online and CD based web application. For instance you can use a code like the following for your configuration file:

<?php
if (preg_match('#dwebpro#si', @$_SERVER['SERVER_SOFTWARE'])) {
    // Insert here the DWebPro configuration
    define('DB_HOST', '127.0.0.1:' . dwebpro_getvar('DWEBPRO_MYSQL_PORT'));
} else {
    // Insert here the Apache/IIS configuration 
    define('DB_HOST', '127.0.0.1');
}
?>

Of course you can! Open the http.ini file and search for the PHP reference in the ISAPI or CGI sections. You will find something like the following:

; PHP 5.2 ISAPI configuration sample
 
[ISAPI1]
Path=##DWEBPRO_PATH##\engine\php5\php5isapi.dll
Extensions=.php|.php3|.phtml|.php4

or like the following:; PHP 5.2 CGI configuration sample [CGI0] Path=##DWEBPRO_PATH##\engine\php5\php-cgi.exe Extensions=.php|.php3|.phtml|.php4 Params=

The above configurations tells DWebPro to make PHP execute the files specified in the Extensions field (.php|.php3|.phtml|.php4).

To make PHP execute the .htm and .html files you have only to add them th the Extensions field.

; PHP 5.2 ISAPI configuration sample
 
[ISAPI1]
Path=##DWEBPRO_PATH##\engine\php5\php5isapi.dll
Extensions=.php|.php3|.phtml|.php4|.htm|.html

; PHP 5.2 CGI configuration sample
  
[CGI0]
Path=##DWEBPRO_PATH##\engine\php5\php-cgi.exe
Extensions=.php|.php3|.phtml|.php4|.htm|.html
Params=

Refer to the ISAPI and CGI topics for more information about Server Side Languages support and configuration.

Distributing MySQL with a closed source software requires an OEM License otherwise it's illegal. The cost of the OEM License will prevent us to release our product under a “FREE for non commercial use” agreement.

Moreover, MySQL and PHP are both available in multiple versions, if a user want to install a different version what should we do?
Creating a different package for each combination is not very efficient.

We have found a much more flexible solution. We provide a different preconfigured package for each server side language and database so the user can decide by itself what install.

Another benefit is related to the size of the DWebPro installer that is only 9 Mb. This means less time to download, less space to archive and so on.

The use of $HTTP_POST_VARS, $HTTP_GET_VARS and the other $HTTP_*_VARS predefined arrays has been deprecated since PHP 5.0.0. From PHP 4.1.0 you can use the superglobals ($_POST, $_GET and so on) in the place of the long predefined arrays.

If your code still relays on the long predefined array you can enable them editing the php.ini. To do this, open the php.ini file and search for the following line:

register_long_arrays = Off

Replace that line with:

register_long_arrays = On

You can find more information on PHP predefined variables in the official PHP manual (http://www.php.net/variables.predefined). Refer to the Where is the php.ini File? FAQ for help in identifying the php.ini file to modify.

If you are using PHP as ISAPI module you have to stop DWebPro and restart it to make the PHP engine aware of the configuration change.

By default, PHP is distributed with the short_open_tag directive set to Off. With this configuration you must use <?php as open tag for your PHP scripts otherwise they will not work.

If your code uses the short open tag (<?) you can enable it editing the php.ini. To do this, open the php.ini file and search for the following line:

short_open_tag = Off

Replace that line with:

short_open_tag = On

You can find more information on PHP predefined variables in the official PHP manual (http://www.php.net/variables.predefined). Refer to the Where is the php.ini File? FAQ for help in identifying the php.ini file to modify.

If you are using PHP as ISAPI module you have to stop DWebPro and restart it to make the PHP engine aware of the configuration change.

DWebPro supports all of the major PHP encoders available on the market. It supports:

• Ioncube
• Zend Encoder
• SourceGuardian
• PHTML Encoder
• eAccelerator
• phpSHIELD
• Nu-Coder

In addition to these encoders, the DWebPro includes the DWebPro Encoder, a PHP and ASP Classic 3.0 encoder with AES-based encryption.

To execute a PHP script encoded with one of the above encoders you need to enable the relative extension in the php.ini file. Refer to the Where is the php.ini File? FAQ for help in identifying the php.ini file to modify.

If you are using one of our PHP preconfigured packages you need only to open the php.ini file, search for the Dynamic Extensions section and enable the extension of the encoder you are using. Here is an excerpt of the php.ini of our PHP 5.2 preconfigured package:

; PHPShield Extension
;extension=phpshield.5.2.win
 
; SourceGuardian Extension
;extension=ixed.5.2.win
 
; PHTMLEncoder Extension
; PHTMLEncoder doesn't support PHP 5.2 
;extension=phtmlenc5.1.4.dll
 
; Nu-Coder Extension (http://www.nusphere.com/products/nucoder.htm)
; Check the Nu-Coder EULA (nu-coder_eula.txt)
;extension=nu-coder-php-5.2.dll
 
; eAccelerator Extension
;zend_extension_ts = engine/php5/ext/eAccelerator095_5.2.0.dll
;eaccelerator.shm_size = "64"
;eaccelerator.cache_dir = ""
;eaccelerator.enable = "1"
;eaccelerator.optimizer = "1"
;eaccelerator.debug = "0"
;eaccelerator.check_mtime = "1"
;eaccelerator.filter = ""
;eaccelerator.shm_max = "0
;eaccelerator.shm_ttl = "0"
;eaccelerator.shm_prune_period = "0"
;eaccelerator.shm_only = "1"
;eaccelerator.compress = "1"
;eaccelerator.compress_level = "9"
;eaccelerator.keys = "shm_only" 
;eaccelerator.sessions = "shm_only" 
;eaccelerator.content = "shm_only"
;eaccelerator.admin.name="yourusername" 
;eaccelerator.admin.password="yourpassword"
 
; Ioncube Encoder
; To enable Ioncube Encoder Extension you have to disable Zend Optimizer 
;zend_extension_ts = engine/php5/ext/ioncube_loader_win_5.2.dll
 
; Zend Optimizer
[Zend]
;zend_extension_manager.optimizer_ts="engine\php5\optimizer"
;zend_extension_ts="ZendExtensionManager.dll"
;zend_optimizer.optimization_level=15

When started by DWebPro, the MySQL engine doesn’t relay on a configuration file (i.e. my.ini), instead it receives all the needed configuration settings from command line. This behavior is required to avoid any conflict with previously installed MySQL engines and make the MySQL instance bundled with DWebPro completely stand alone. If you need to set a MySQL system variable check the "How can I set a MySQL system variable?" FAQ.

When started by DWebPro, the MySQL engine doesn’t relay on a configuration file (i.e. my.ini), instead it receives all the needed configuration settings from command line.

As described in MySQL official manual (see http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html and http://dev.mysql.com/doc/refman/5.1/en/using-system-variables.html) you can change the MySQL system variables passing them as parameters.

Under DWebPro you can achieve this editing the CustomParams field in the MySQL topic.

For instance, if you want to set the lower_case_table_names system variable to 2 you have to add the "--lower_case_table_names=2" string to the CustomParams as follows:

CustomParams=--skip-innodb --lower_case_table_names=2

In the above example, "--skip-innodb" is another parameters we pass to MySQL.

Remember to restart DWebPro to make it aware of the change.

If your web site reads data with a character set different from latin1 from a MySQL database you have to configure DWebPro to start MySQL with the correct character set (and location). MySQL supports more than 30 different character sets. You can find a list of all the charsets supported by MySQL in the official manual:

http://dev.mysql.com/doc/refman/5.0/en/charset-charsets.html

For instance, if your web site uses Cyrillic characters you have to configured the CustomParams field in the MySQL section as follows:

CustomParams=--skip-innodb --character-set-server=cp1251

In the above example, "--skip-innodb" is another parameters we pass to MySQL.

Remember to restart DWebPro to make it aware of the change.