The comma separated PHP function names for the Auto-Update feature (see Field Setup)

You can add your own functions by putting your functions in the server side Global Code section (see Server Events and Client Scripts) and then add your function name here. The function name must follow the standard rules for naming variables in PHP.

The comma separated function names for the Validate feature (see Field Setup)

You can add your own PHP/JavaScript functions for custom server/client-side validation. The function name is used for both PHP and JavaScript, so it must be a valid function name for both languages. You can put your server-side and client-side validation function in the Global Code (see Server Events and Client Scripts) section of server-side and client-side respectively.

The code editor in the UI. Possible values: "Default" or "Classic". The "Default" editor is a browser-based editor, WebView2 Runtime is required. If you prefer the old editor, switch to "Classic", then close and open PHPMaker again.

Project name. See Project File for more info.

Unique ID of the project. Do not change the project ID unless absolutely necessary. See Project File for more info.

Memory limit of Node.js (MB). If your project is large, you may need to increase the memory limit, e.g. you can set it to 2048, 3072, 4096, etc.

PHPMaker uses PHP-DI, the dependency injection container can be compiled into PHP code optimized especially for your configuration and your classes. If the environment (see above) is set as production, and this setting is enabled, then compilation will be enabled.

Whether to generate route groups so that user can also use alternative route for table, e.g. /cars/list instead of /carslist. Default is true.

If that is unnecessary or you have a large number of tables, you can turn it off for better routing performace.

Do not generate the project stylesheet.

Specify the encoding for Ajax/iconv

Some features such as Ajax require conversion between your encoding and utf-8. If you use non English languages, you may need to set character encoding for these features. By default PHPMaker will setup the encoding automatically based on your project's Charset setting. If that is incorrect, you can specify yours. Make sure either iconv functions or multibyte string functions are enabled and your encoding is supported. See PHP manual for details.

The encoding of the file system of the server.

When saving a file to the server, the file name need to be converted to the file system encoding. If your project charset/encoding is different from the file system encoding and you accepts non alphanumeric file names, enter the file system encoding of the server

Allow passing username and password to the login page as URL parameters.

By default the login page accepts HTTP POST only. If this setting is enabled, it accepts HTTP GET also, then user can login by URL , e.g.

login?username=xxx&password=yyy (where "yyy" is a plain text password)

For example, this allows user login by using PHP cURL from your own scripts.

For example, this allows login by your own scripts.

For security, you should pass encrypted username and password whenever possible. You can decrypt them with your code by User_CustomValidate server event before validation, see Server Events and Client Scripts.

Allow passing username and password to the login page via session variables.

By default the login page accepts HTTP POST only. If this setting is enabled, it accepts session variables also, then user can auto-login by setting some session variables , e.g.

$_SESSIONPROJECT_NAME . "_Username" = "xxx"; // where PROJECT_NAME is the constant of your project name (see above) and "xxx" is user name
$_SESSIONPROJECT_NAME . "_Password" = "yyy"; // where "yyy" is a plain text password

Specify if sensitive keywords allowing XSS attack should be removed.

If enabled, all user input string will be checked against an array of sensitive keywords. If discovered, those keywords will be removed to prevent XSS attack. If this behavior is unwanted, you can disable this feature at your own risk. Re-generate and re-upload the config.php after changing this setting.

XSS removal is done by HTML Purifier with default configuration, if you just want to customize the configuration, you can use server side Global Code (see Server Events and Client Scripts) to modify the global variable $PurifierConfig which is used to create instance of HTMLPurifier, e.g.

$PurifierConfig = \HTMLPurifier_Config::createDefault();
$PurifierConfig->set('Filter', 'ExtractStyleBlocks', true);

Read HTML Purifier configuration documentation for details.

Check synchronizer token for forms with method="post".

Synchronizer token is used to prevent Cross-Site Request Forgery (CSRF). If you add your own HTML forms with method="post", you should add the token to your form by a hidden tag, e.g.

<input type="hidden" name="token" value="<?= CurrentPage()->Token ?>">

Specify the session time-out period if the user does not refresh or request a page.

PHP has its own settings for session timeout, you can configure them in php.ini, read Runtime Configuration, but sometimes you may want to control the session period yourself, then you can setup BOTH this setting and the Session keep alive interval (seconds) setting (see below) to a positive value.

Specify the interval to send Ajax request to the server for keeping the session alive.

Specify the countdown period before session ends.

When the session is about to end, a modal dialog will show up to remind user and let the user choose to continue the session. If the user does not respond after the countdown period, the session will expire.

The separator between key values of a composite key. Default is ",".

If your primary key values are of string type and contain commas also, the commas will affect parsing of the composite key value in the script and lead to failure of locating a record, you can change the separator to avoid such problem.

Specify if master record should be exported during exporting master/detail records to CSV. Default is false.

If master record is exported, the result CSV may not be imported into other application. If you want to export it anyway, enable this setting.

Allow no paging section in List page.

If both paging section at top and that at bottom are disabled, users will not be able to go to the second or later pages of the recordset. The scripts will use paging section at bottom by default to make sure paging is possible. If you want to allow no paging section (e.g. you always have all records in one page), enable this setting.

If only one page (i.e. number of records <= page size), hide the paging section automatically.

If only one page (i.e. number of records <= current page size), hide the page size selector section automatically.

For use with Check Conflicts (see Table Setup). Specify the number of bytes for calculating the hash value . Default is 200.

Check Conflicts will increase the time required to load the page, for better performance only the first hundreds of bytes of the BLOB fields are processed by default, but there are chances that change of BLOB data is not detected (if the first nth bytes are not changed). You can increase the number of bytes, if you want to process all bytes, enter 0.

Specify if Auto-Suggest should consider Display field #2 to #4.

By default lookup only uses Display field #1 and only finds records with Display field #1 that STARTS WITH the input characters. It this setting is enabled, Auto-Suggest finds records with Display field #1 to #4 that CONTAINS the input characters

Page size of modal lookup. Modal lookup supports pagination (infinite scrolling), this setting specifies the number of records per page.

Specify if the View Tag format should be used during editing.

By default all decimal digits as outputted by the database will be used in Edit page, for example, if a number is 1.23456 in database, the Edit page will also show 1.23456 even you may have specified just 2 decimal digits in View Tag panel (see Field Setup). If you want to show the number as in the View page, you can enable this setting. However, note that after saving the record, the number will be saved as 1.23 only even you have not edited the field value.

Specify the charset for MySQL SET NAMES statement.

If actual charset encoding of your data is different from the charset of your project, you may need to specify this setting for MySQL to convert between them. Read Connection Character Sets and Collations before using this setting.

For setting Oracle's NLS_COMP parameter. Requires Oracle 10gR2 (or later). Possible values are: BINARY, LINGUISTIC, ANSI.

For example, if you want to do case insensitive search you can select LINGUISTIC.

For setting Oracle's NLS_SORT parameter. Requires Oracle 10gR2 (or later).

For example, if you want to do case insensitive search you can enter "BINARY_CI" (no double quotes).

Path of the web root relative to project folder. The project folder is the folder where the generated scripts reside. All relative paths (e.g. file upload paths) are relative to the web root. By default the web root is same as the project folder, so the value of this setting is "." (no quotes) or empty. It is recommended that you use this default value, only change it if you must use a web root folder which is not the same as the project folder.

Specify if an uploaded file should be copied when copying a record with file upload fields. (For use with file upload to folder.) Default is false.

If the option Delete file on update/delete (see PHP settings) is enabled, the uploaded file will be deleted. If the deleted record is a copied record, deleting the uploaded files will affect the original record. To prevent such possible problem, enable this setting to duplicate the uploaded file when copying a record.

Specify the file upload path (absolute) for temporary files. If this setting is used, the matching File upload URL path (absolute) for temporary files (see below) must also be set.

When working with file upload fields, some temporary files will be created and then deleted in a temporary folder. Default is empty, meaning that the global upload folder will be used. However, under some rare cases, you may want to specify your own. This path must be physical and it must be accessible by the web server, e.g. /some/real/path/ or D:\some\real\path\, and is accessible by URL (see next).

Specify the file upload URL path (absolute) for temporary files, e.g. /my/virtual/path/ (root-relative URL) or //www.mycompany.com/my/virtual/path/ (protocol-relative URL). If File upload path (absolute) for temporary files (see above) is used, this setting must also be set so that the temporary files can be accessed by URL.

For use with image resize.

If a target resize width is <= 0, this default width will be used. If this setting is also 0, the width will be auto-adjusted to keep the aspect ratio.

For use with image resize.

If a target height width is <= 0, this default height will be used. If this setting is also 0, the height will be auto-adjusted to keep the aspect ratio.

Whether to put the Quick Search input in the top navbar. By default the Quick Search input is at the bottom of the Extended Search form in the List page of a table.

If this setting is enabled, the Quick Search input will be moved to the navbar.

For use with "All words"option of Quick Search, allows searching all keywords in any fields selected for Quick Search.

When searching "All words" with Quick Search (see Table Setup), by default all keywords must be found in the same field. This option provides an alternative searching behavior.

Option for searching fields that store multiple values as comma separated string.

Valid values are: (Default is 3)
1 - no multiple value, the whole comma separated string is considered as one string
2 - all multiple values must meet the search criteria (AND condition)
3 - either one of the multiple values must meet the search criteria (OR condition)

Specify where to save the search filters. Possible values are: Server, Client, None. Default is Client, i.e. save by browser's localStorage.

For used with Hashed password (previously MD5 password), see Security Settings. If this setting is enabled, PHP password_hash function will be used to create password hash. By default CRYPT_BLOWFISH algorithm will be used. If this setting is disabled, the old md5 function will be used.

If enabled, the administrator, database and SMTP server user name and password stored in the config file will be encrypted by php-encryption.

For use with Export (Email). (see PHP Settings.) Default is 3.

To avoid abusing the export to email feature, the number of email addresses in the recipient field is limited to the specified value.

For use with Export (Email). (see PHP Settings.) Default is 3.

To avoid abusing the export to email feature, the number of emails can be sent by the user in each session is limited to the specified value.

Use Bootstrap Toasts to display messages of the application.

By default the messages are displayed above the main table. This options uses Bootstrap Toast to show the message instead. Default is true.

Bootstrap CSS class for Fullscreen Modal dialogs. Possible values are: modal-fullscreen, modal-fullscreen-sm-down, modal-fullscreen-md-down, modal-fullscreen-lg-down, modal-fullscreen-xl-down, modal-fullscreen-xxl-down. Default is modal-fullscreen-sm-down, i.e. full screen modal will be used for mobile devices.

Use native <select> HTML element for select-one fields.

By default all<select> tags (fields with SELECT Edit Tag, see Field Setup) will be replaced by Select2 tags for more features. However, if this setting is enabled, native <select> tag will be used for select-one fields.

By default Bootstrap Horizontal form is used in Add/Edit/Search/Update/Registration pages, this option makes the scripts use Bootstrap table instead.

Add placeholder attribute to form elements automatically. Possible values are:

• None - no placeholder
• Caption - use field caption (see Field Setup) as placeholder attribute value (default)
• Title - use field title (see Field Setup) as placeholder attribute value

AdminLTE layout class. Possible values are: layout-fixed, layout-top-nav, layout-boxed, layout-navbar-fixed, or layout-footer-fixed. Default is layout-fixed.

Specify the page title style. Possible values are:

• None - no page title (with Breadcrumbs)
• Caption - table caption (without Breadcrumbs)
• Breadcrumbs - table caption (with Breadcrumbs) (default)
• Title - site title (with Breadcrumbs)

Authentication mode: Possible values are: Windows, LDAP. If not specified, no authentication.

PHP array of options, for use with ldap_set_option, e.g. LDAP_OPT_XXX => "xxx". By default the following options are already set:

LDAP_OPT_PROTOCOL_VERSION => 3, LDAP_OPT_REFERRALS => 0

Enable Google Sign-In. Requires both Google client ID and Google client secret. To create client id and secret, read Creating a Google API Console project and client ID.

API actions that does not require PHP session. Comma separated value of API action names without spaces, e.g. "file,lookup". Default is "file".

By default, each session is stored in the filesystem. The session file is read once when session_start() is called and written to disk when the script ends. To avoid conflicts, session files are locked during script execution. The read/write and locking processes are expensive. This setting allows you to improve API performance by not starting session for some API actions, e.g. "file".

Number format of the locale in ICU DecimalFormat (see the Patterns section for complete information), e.g. #,##0.###

Show the menu item at the top navbar instead of the vertical menu.