PHP Settings

 

General Options

 

No Cache Whether caching is required on browser
Multi-Language

Enable multi-language project. If enabled, a combobox will appear on the top of the generated scripts for user to select language. See Tools for selecting languages for the multi-language project.

Important
  1. Multi-Language project must use utf-8 encoding. The charset of the project must be "utf-8".
  2. The data in your database must be stored in unicode, otherwise your data will not be displayed properly.
Default Language

Default language of the project. It must be compatible with Charset (see HTML Settings). Default is English.

There is always one default language for a project. Only the English language file (english.xml) is shipped with PHPMaker. If your project is single language but you use another language, create a language file for your language (see Making Language Files), put it in the "languages" subfolder under the installation folder and then select your default language using this combobox.

If you enable Multi-Language, you must select one of the selected languages as the default language.

File Upload

Upload folder - The global folder where the uploaded files resides. If you do not enter a specific folder for a file upload field in the Edit Tag panel of the Field Setup page, all the uploaded files will be put in this folder.

Notes
  1. Always specify an upload folder if you allow file upload. This folder is used as the root folder of temporary folders for file upload fields during Add/Edit. It is also used as the root folder of the user files folder of CKEditor.
  2. Unlike the field specific upload folder setting (which is a PHP expression), this field specific setting must be a constant string (without double quotes). If you want dynamic upload folders for different fields, specify upload folder for each field (see Field Setup).
  3. The path is relative to application root. Use slashes "/" as path delimiter, no leading slash. e.g. If the application root of your website is C:\Inetpub\wwwroot\demo and you enter "uploads/" in this textbox, the folder for the uploaded files will be C:\Inetpub\wwwroot\demo\uploads. If you are not sure which folder is application root, please read Application Root. If for some reasons you must use another absolute path, use the Advanced Setting File upload path (absolute) for temporary files.
  4. The path supports AWS S3 bucket, e.g. you can enter "s3://my-bucket/" (no double quotes). (In this special case, the path is not relative to application root.) To use S3 bucket, make sure you register the Amazon S3 Stream Wrapper in the Global Code server event. If you use S3 bucket, it will also be used as upload folder for temporary files. If you are only using S3 but your website is not hosted by AWS, you may want to use a local upload folder on the same server as the web server for better performance, then you can also use the Advanced Setting File upload path (absolute) for temporary files.
  5. Make sure that the Web server user have read/write access to the folder. If you use S3 bucket, note that the uploaded files in the bucket are not public by default. Remember to configure bucket permissions so that the uploaded files are accessible by users.

Max File Size - Maximum file upload size in bytes. If <= 0, there is no checking on file size.

Notes File upload also depends on your PHP, web server and database configuration:

  1. PHP - Check your php.ini, related configurations are file_uploads, upload_max_filesize, upload_tmp_dir, post_max_size, max_input_time, memory_limit, and max_execution_time directives in php.ini.
  2. Apache - If you use Apache web server, check LimitRequestBody directive.
  3. MySQL - Check the max_allowed_packet setting in your MySQL configuration.

Allowed file types - The allowed file extensions of the uploaded files. Separate the file extensions (without ".") by comma without space, e.g. gif,png,png. If blank, all file types are allowed.

Delete file on update/delete - Option to delete the uploaded file when the field value is replaced, removed or if the record is deleted.

Note If Delete file on update/delete 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 Advanced Setting Create upload file on copy (see Advanced Settings) to duplicate the uploaded file when copying a record.
Audit Trail

You can choose to log activities in a log file or in a database table.

Log file folder - The folder where the audit trail log file resides.

Notes
  1. Make sure that the Web server user have read/write access to the folder.
  2. The path is relative to application root. Use slashes "/" as path delimiter, no leading slash. e.g. If the application root of your website is C:\Inetpub\wwwroot\demo and you enter "uploads/" in this textbox, the folder for the log file will be C:\Inetpub\wwwroot\demo\uploads. If you are not sure which folder is application root, please read Application Root.

Use database table - Log the activities in the specified table instead of log file. The table must have the following fields: (actual data types depend on database type)

  • DateTime (DateTime)
  • Script (VarChar)
  • User (VarChar)
  • Action (VarChar)
  • Table (VarChar)
  • Field (VarChar)
  • KeyValue (Long VarChar)
  • OldValue (Long VarChar)
  • NewValue (Long VarChar)

You can create the database yourselves and select the table in the combobox, then click the [...] button to select the fields in your table. Alternatively, if you have not created the table yet, you can click [Create Table] and let PHPMaker creates the table and setup the settings for you.

Track login/logout activities - If security feature is enabled, login/logout activities will also be logged.

Validation

Server-side - Enable server-side form validation.

Client-side (JavaScript) - Enable client-side form validation.

Note If the available validation format in the Edit Tag panel (see Field Setup) does not fulfil your requirements, you can use your own server-side and/or client-side validation code using Server Event and Client Scripts.

 

Page Options (Global)

The following page options are global for all tables. If you want different settings for a particular table, you can use table-specific options available in the Table Setup page.

 

Records per page Number of records to be displayed on the list page of all tables. If blank or 0, default setting of 20 will be used.
Selectable page sizes

Number of records to be selected by user. Comma separated values, e.g. 10,20,50,ALL.

Note "ALL" (without quotes) is supported, other values must be integers.
Paging section style "NumericPages" or "NextPrev"
Sort type None, Single column or Multiple column. If Multiple column is selected, the generated list page supports multi-column sorting by Ctrl-clicking the table header.
Multiple column

Show multiple records per row. Default is 0. This feature will only take effect if the value is > 0. Possible values: 1, 2, 3, 4, 6, 12

Paging section at top Show the paging section at top (also applies to View page)
Paging section at bottom Show the paging section at bottom (also applies to View page)
Paging section in View page Show paging section in View page also
Paging section in Edit page Show paging section in Edit page also
Multiple delete Show checkboxes in the list page for selecting multiple records to delete
Links on left side Show the links in record row on the left instead of right
Use buttons as links Show the links in record row as a button group instead of individual icons or links.
Use button dropdown for links Show the links in record row as a button with dropdown menu instead of individual icons or links.
Use button dropdown in paging section Show the links in paging section as buttons with dropdown menu instead of individual links.
Export

Enable export in List page - allow export in List pages

Enable export in View page - allow export in View pages also

Use button dropdown - show the export links as a button with dropdown menu. Default is showing the export links as a row of icons.

Print/CSV/HTML/Excel/Word/XML/PDF/Email - Records can be exported to Print (printer-friendly), CSV, HTML, Excel, Word, XML, PDF format or sent as HTML email content.

Note The fields in printer friendly version are same as in List/View page, while the fields in other format are determined by the Export setting of the field in Field Setup page.

Note that the fields in printer friendly version are same as in List/View page, while the fields in other format are determined by the Export setting of the field in Field Setup page.

Export type - Determines which records to export. The follows are supported:

  • All Pages - Records in all pages are exported
  • Current Page - All records in current page are exported
  • Selected Record - If selected, a checkbox will be displayed in each row for selection. Only selected records in the current page are exported. (Selecting records in different pages is not allowed.) To select records primary key is required, Current Page export type will be used for tables without primary key.
Notes
  1. Binary data (BLOB fields) cannot be exported.
  2. Export to HTML/CSV/XML/PDF are not applicable to reports.
  3. Export to XML requires PHP DOM (which should be already enabled by default).
  4. Export to Word/Excel works by exporting data in HTML format for Word/Excel to convert/import, the exported file is not native .doc/.xls format. However, registered users can use the PhpSpreadsheet/PHPWord extension which outputs native Excel/Word file format.
  5. Images cannot be exported to Word/Excel/CSV/XML. However, registered users can use the PhpSpreadsheet/PHPWord extension which outputs images also.
  6. Export to PDF (for all users) and PhpSpreadsheet/PHPWord extensions (for registered users) support images (jpg, gif and png only), but a temporary folder is required during export, the extensions use the Upload folder (see File Upload above) because write permission for the folder should be already setup properly. Even you do not use file upload to folder, if you want to export with images, make sure you still specify an upload folder and set up write permission.
Notes (Export to PDF)
  1. The extension is an experimental extension only. There are known issues, see Third-party Tools and read the note in the extension setup page (see Tools -> Extensions) for more information before use. Only enable it if necessary.
  2. The extension performs best if you are using non-unicode alphanumerical characters (e.g. iso-8859-1) only. If you use unicode, configure advanced settings for the extension, read the note in the extension setup page (see Tools -> Extensions) for more information.
  3. By default export is only enabled in View page. If you want to enable it in the List page also (the number of records to be exported is not large), you can set the advanced settings of the extension (see Tools -> Extensions).

 

Email Settings

PHPMaker supports many features that can send emails. If you use these features, you'll need to specify a SMTP server.

Note PHPMailer (see Third-party Tools) is always used as the email component.

SMTP server

The host name or IP of the SMTP server.

Note Some servers do not support "localhost" as SMTP server, in such case you need to specify a valid SMTP server in the network.
SMTP server port Port number of SMTP server. Default is 25.
SMTP server username

User name for SMTP server authentication. If your SMTP server does not require authentication, leave it blank.

SMTP server password

Password for SMTP server authentication. If your SMTP server does not require authentication, leave it blank.

Sender (Email address)

Email address of the sender of all emails

Recipient (Email address)

Email address of the recipient(s) for notification emails when a record is added/edited/deleted (if enabled, see Table Setup). If there are multiple recipients, separate them by comma.

Security

Protocol used by the SMTP server. Possible values are: SSL or TLS.

Notes

  1. Leave this setting empty if your SMTP server does not use such protocols.
  2. If you enable this, make sure you have enabled OpenSSL support in your php.ini, see Introduction to PHP and MySQL.
  3. If you use gmail, read Allowing less secure apps to access your account.

 

 ©2002-2018 e.World Technology Ltd. All rights reserved.