index.html

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="utf-8" />
    <title>Lazy Mofo Datagrid for PHP &amp; MySQL CRUD</title>
    <meta name="keywords" content="PHPGrid Free, PHP DataGrid, Automatic CRUD, PHP CRUD" />
    <meta name="description" content="Lazy Mofo is a SQL meta driven form and grid generator for PHP and MySQL." />
    <meta name="robots" content="noindex,nofollow">
    <style>
        *     { font-family: sans-serif; }
        body  { margin: 40px; }
        pre   { font-family: monospace, courier; color: blue; margin-left: 10px; padding: 10px; border: 1px solid #999; border-radius: 2px; border-right: 0; background-color: #ffd; width: 100%; font-size: 70%; }
        li    { margin: 6px; }
        .gray { color: #555; }
    </style>
</head>
<body>

<img src='https://i.imgur.com/CGDTkQL.png' alt='logo' align='left' style='margin: 10px; clear: both;' />


<h1 style='clear:left;'>Lazy Mofo (LM) PHP Datagrid</h1>
<div>
    <a href='https://github.com/lazymofo/datagrid'>github</a> |
    <a href='http://lazymofo.pcmad.ro'>live demo</a> |
    <a href='mailto:iansoko@gmail.com'>email</a>
</div>
<p>LM is a single PHP class for performing CRUD (create, read, update and delete) operations on a MySQL database table.</p>
<p><b>No new features will be added, this project is in maintenance mode.</b></p>
    
<ul>
    <li>Define grids and forms by SQL statements or table name</li>
    <li>Populate select, radio, and checkbox inputs with data from SQL statements</li>
    <li>Upload documents, resize or crop images</li>
    <li>Grid features include pagination, sorting, and inline editing. Searching can be added.</li>
    <li>Grid uses SQL_CALC_FOUND_ROWS, limit + offset for efficiency and low memory usage on large datasets</li>
    <li>Built-in validation, error reported next to input</li>
    <li>i18n/internationalization enabled. See i18n/template.php to submit your county-language file.</li>
    <li>Lightweight; a single class</li>
</ul>

<h1>Contents</h1>
<ul>
    <li><a href='#whats_new'>What's New</a></li>
    <li><a href='#requirements'>Requirements</a></li>
    <li><a href='#example_1'>Example 1 - Basic Usage</a></li>
    <li><a href='#example_2'>Example 2 - Advanced Usage</a></li>
    <li><a href='#hiding_or_altering_links_and_buttons'>Hiding or Altering Links and Buttons</a></li>
    <li><a href='#redirect_to_edit_screen_after_update_and_insert'>Redirect to Grid Screen After Update and Insert</a></li>
    <li><a href='#input_and_output_controls'>Input and Output Controls - define how a field is rendered</a></li>
    <ul>
        <li><a href='#native_input_controls'>Native Input Controls</a></li>
        <li><a href='#native_output_controls'>Native Output Control</a></li>
        <li><a href='#defining_custom_input_and_output_controls'>Defining Custom Input and Output Controls</li>
        <li><a href='#Automatically Populated Controls'>Automatically Populated Controls</li>
    </ul>
    <li><a href='#adding_search'>Adding Search</a></li>
    <li><a href='#customizing_the_search_form'>Customizing the Search Form</a></li>
    <li><a href='#defining_separate_add_and_edit_forms'>Defining Separate Add and Edit Forms</a></li>
    <li><a href='#validation'>Validation</a></li>
    <li><a href='#on_insert_update_delete_events'>On Insert/Update/Delete Events</a></li>
    <li><a href='#cross_site_request_forgery_protection_token'>Cross Site Request Forgery Protection Token</a></li>
    <li><a href='#i18n'>i18n/Internationalization</a></li>
    <li><a href='#date_formats'>Date Formats</a></li>
    <li><a href='#decimal_separator'>Decimal Separator</a></li>
    <li><a href='#adding_jquery_ui_datepicker'>Adding JQuery UI Datepicker</a></li>
    <li><a href='#export_to_csv'>Export to CSV</a></li>
    <li><a href='#more_features_and_settings'>More Features and Settings</a></li>
</ul>


<h1 style='clear:left;'><a name='whats_new'>What's New</a></h1>
<ul>
    <li>PHP 5 support dropped, better PHP 8 compatibility added</li>
    <li>Fix to support <a href='#decimal_separator'>comma as decimal separator</a>.</li>
    <li>Live demo restored. Thanks Horatiu!</li>
    <li>See i18n/template.php if want to submit your county + language file.</li>
</ul>


<h1><a name='requirements'>Requirements</a></h1>
<ul>
<li>PHP 7+ and MySQL/MariaDB</li>
<li>PHP Modules: mysql, mbstring, gd</li>
<li>Database table must have an auto increment primary key identity</li>
</ul>


<h1><a name='example_1'>Example 1 - Basic Usage</a></h1>
<pre>
include('lazy_mofo.php');

// required for csv export
ob_start();

// connect to database with pdo
$dbh = new PDO("mysql:host=localhost;dbname=test;", 'user', 'password');

// create LM object, pass in PDO connection, see i18n folder for language + country options 
$lm = new lazy_mofo($dbh, 'en-us'); 

// table name for updates, inserts and deletes
$lm-&gt;table = 'market';

// identity / primary key column name
$lm-&gt;identity_name = 'market_id';

// use the lm controller 
$lm-&gt;run();

</pre>


<h1><a name='example_2'>Example 2 - Advanced Usage</a></h1>

<pre>
// enter your database host, name, username, and password
$db_host = 'localhost';
$db_name = 'test';
$db_user = 'root';
$db_pass = '';


// connect with pdo 
try {
	$dbh = new PDO("mysql:host=$db_host;dbname=$db_name;", $db_user, $db_pass);
}
catch(PDOException $e) {
	die('pdo connection error: ' . $e-&gt;getMessage());
}

// create LM object, pass in PDO connection, see i18n folder for country + language options 
$lm = new lazy_mofo($dbh, 'en-us');


// table name for updates, inserts and deletes
$lm-&gt;table = 'market';


// identity / primary key for table
$lm-&gt;identity_name = 'market_id';


// optional, make friendly names for fields
$lm-&gt;rename['country_id'] = 'Country';


// optional, define input controls on the form
$lm-&gt;form_input_control['photo'] = array('type' =&gt; 'image');
$lm-&gt;form_input_control['is_active'] = array('type' =&gt; 'radio', 'sql' =&gt; "select 1, 'Yes' union select 0, 'No'");
$lm-&gt;form_input_control['country_id'] = array('type' =&gt; 'select', 'sql' =&gt; 'select country_id, country_name from country');


// optional, define editable input controls on the grid
$lm-&gt;grid_input_control['is_active'] = array('type' =&gt; 'checkbox');


// optional, define output control on the grid 
$lm-&gt;grid_output_control['contact_email'] = array('type' =&gt; 'email'); // make email clickable
$lm-&gt;grid_output_control['photo'] = array('type' =&gt; 'image');         // make image clickable  


// show search box, but _search parameter still needs to be passed to query below 
$lm-&gt;grid_show_search_box = true;


// query to define grid view
// IMPORTANT - last column must be the identity/key for [edit] and [delete] links to appear
// include an 'order by' to prevent potential parsing issues
$lm-&gt;grid_sql = "
select 
  m.market_id
, m.market_name
, m.photo
, m.contact_email
, c.country_name
, m.is_active
, m.create_date
, m.market_id 
from  market m 
left  
join  country c 
on    m.country_id = c.country_id 
where coalesce(m.market_name, '')   like :_search 
or    coalesce(m.contact_email, '') like :_search 
or    coalesce(c.country_name, '')  like :_search 
order by m.market_id desc
";


// bind parameter for grid query
$lm-&gt;grid_sql_param[':_search'] = '%' . trim($_REQUEST['_search'] ?? '') . '%';


// optional, define what is displayed on edit form. identity id must be passed in also.  
$lm-&gt;form_sql = "
select 
  market_id
, market_name
, country_id
, photo
, contact_email
, is_active
, create_date
, notes 
from  market 
where market_id = :market_id
";


// bind parameter for form query
$lm-&gt;form_sql_param[':market_id'] = intval($_REQUEST['market_id'] ?? 0); 


// optional, validation - regexp, 'email' or a user defined function, all other parameters optional 
$lm-&gt;on_insert_validate['market_name']   = array('regexp' =&gt; '/.+/',  'error_msg' =&gt; 'Missing Market Name', 'placeholder' =&gt; 'this is required', 'optional' =&gt; false); 
$lm-&gt;on_insert_validate['contact_email'] = array('regexp' =&gt; 'email', 'error_msg' =&gt; 'Invalid Email',       'placeholder' =&gt; 'this is optional', 'optional' =&gt; true);


// copy validation rules, same rules when updating
$lm-&gt;on_update_validate = $lm-&gt;on_insert_validate;  


// run the controller
$lm-&gt;run();
</pre>

<h1><a name='hiding_or_altering_links_and_buttons'>Hiding or Altering Links and Buttons</a></h1>
Most links, buttons, and messages can be hidden or altered. View the class source code to see all the member variables.<br>
i18n/internationalization are in the process of being added. Check the i18n folder for your language + country. Set the i18n by passing the language + country code into the constructor.
<pre>
Example:

// change back button to read "Cancel"
$lm-&gt;form_back_button = "&lt;input type='button' value='Cancel' class='lm_button dull' onclick='_back();'&gt;";

// alter link text
$lm-&gt;grid_add_link = str_replace('Add a Record', 'Add New', $lm-&gt;grid_add_link);
$lm-&gt;grid_edit_link = str_replace('[edit]', 'Edit', $lm-&gt;grid_edit_link);

// hide delete and export links
$lm-&gt;grid_delete_link = "";
$lm-&gt;grid_export_link = "";

// change success message
$lm-&gt;form_text_record_added = "New Record Added";
$lm-&gt;grid_text_record_added = "New Record Added";
</pre>


<h1><a name='redirect_to_edit_screen_after_update_and_insert'>Redirect to Grid Screen After Update and Insert</a></h1>
<p>By default the user is redirected back to the edit form after making updates or inserting a record. Redirect users to the opening grid screen by setting the following variables to false:</p>

<pre>

    $lm-&gt;return_to_edit_after_insert = false;
    $lm-&gt;return_to_edit_after_update = false;

</pre>


<h1><a name='input_and_output_controls'>Input and Output Controls - define how a field is rendered</a></h1>
<p>Input and Output Controls are associative arrays used to define how to render input or output for a field.</p>
<p><b>Inputs</b> render form inputs such as textarea, select, or checkbox. </p>
<p><b>Outputs</b> render text, links, and images. Output controls only apply to the grid view and are defined in grid_output_control.</p>

For inputs where sql statements are used, the first column in the sql statement corresponds to the select/checkbox/radio value, the second column is the displayed text.

<pre>
Define Inputs on edit form()
$lm-&gt;form_input_control["field_name"] = array("type" => string [, "sql" => string [, "sql_param" => array]]);

Define Inputs on grid()
$lm-&gt;grid_input_control["field_name"] = array("type" => string [, "sql" => string [, "sql_param" => array]]);

Define Output on grid()
$lm-&gt;grid_output_control["field_name"] = array("type" => string);
</pre>

<pre class="gray">
// legacy syntax still supported (changed in version 2019-01-10)
// optional sql string depending on control, type is prefixed with --
$lm-&gt;form_input_control["field_name"] = "[sql]--type";

// legacy examples
$lm-&gt;form_input_control["country_id"] = "select country_id as val, country_name as opt from country;--select";
$lm-&gt;form_input_control["is_active"] = "--checkbox";
</pre>

<pre>

Examples: 

    $lm-&gt;form_input_control['client_pic'] = array("type" => "image");

    $lm-&gt;form_input_control['pdf'] = array("type" => "document");

    $lm-&gt;form_input_control['is_active'] = array("type" => "checkbox"); 

    $lm-&gt;form_input_control['will_you_attend'] = array("type" => "radio", "sql" => "select 1 as key, 'Yes' as val union select 0, 'No'");

    $lm-&gt;form_input_control['country_id'] = array("type" => "select", sql => "select country_id as val, country_name as opt from country");

</pre>

<h2><a name='native_input_controls'>Native Input Controls</a></h2>
<p>For use with form_input_control and grid_input_control arrays.</p>

<table border='1'>
    <tr><th>type</th><th>description</th></tr>
    <tr><td>text</td><td>text input (default)</td></tr>
    <tr><td>password</td><td>password input</td></tr>
    <tr><td>number</td><td>text input for number, when cast numbers are filtered through restricted_numeric_input pattern.</td></tr>
    <tr><td>date</td><td>text input, date is formatted according to public $date_format variable</td></tr>
    <tr><td>datetime</td><td>text input, date is formatted according to public $date_format variable</td></tr>
    <tr><td>textarea</td><td>textarea input</td></tr>
    <tr><td>readonly</td><td>plain text (not an input, just displays data)</td></tr>
    <tr><td>readonly_date</td><td>plain text formatted with date settings (not an input, just displays data)</td></tr>
    <tr><td>readonly_datetime</td><td>plain text formatted with datetime settings (not an input, just displays data)</td></tr>
    <tr><td>image</td><td>file input for uploading, if image exists then image is displayed with 'delete' checkbox.</td></tr>
    <tr><td>document</td><td>file input for uploading, if document exists then display link with 'delete' checkbox.</td></tr>
    <tr><td>select</td><td>select dropdown, sql statement is optional.</td></tr>
    <tr><td>selectmultiple</td><td>select dropdown with multiple options. values are stored in a delimited list. sql is optional. sql_param is optional.</td></tr>
    <tr><td>checkbox</td><td>input checkboxes. values are stored in a delimited list. sql is optional. sql_param is optional. </td></tr>
    <tr><td>radio</td><td>radio buttons. sql is optional. sql_param is optional.</td></tr>
</table>

<h2><a name='native_output_controls'>Native Output Controls</a></h2>
<p>For use with form_output_control and grid_output_control arrays.</p>

<table border='1'>
    <tr><th>type</th><th>description</th></tr>
    <tr><td>text</td><td>outputs plain text (default)</td></tr>
    <tr><td>date</td><td>outputs date according to date_out setting</td></tr>
    <tr><td>datetime</td><td>outputs datetime according to datetime_out setting</td></tr>
    <tr><td>email</td><td>outputs a clickable email link</td></tr>
    <tr><td>image</td><td>outputs a clickable link to the image, or display image if grid_show_images = true</td></tr>
    <tr><td>document</td><td>outputs a clickable link to the document</td></tr>
    <tr><td>html</td><td>outputs text without escaping</td></tr>
</table>

<h2><a name='defining_custom_input_and_output_controls'>Defining Custom Input and Output Controls</h2>
<p>User defined functions can be defined to render an input or output control. </p>

<pre>
Example: 

$lm->form_input_control['weird_data'] = array("type" => "my_user_function");

function my_user_function($column_name, $value, $command, $called_from){

    // $column_name: field name
    // $value: field value  
    // $command: array defined in the control, or string with legacy syntax; rarely needed
    // $called_from: origin of call; 'form', or 'grid'; rarely needed

    global $lm;
    $val = $lm-&gt;clean_out($value);
    return "&lt;input type='text' name='$column_name' value='$val' size='100'&gt;";

}
</pre>


<h2><a name='Automatically Populated Controls'>Automatically Populated Controls</h2>
<p>By default form_input_control and grid_output_control will populate with date, datetime, number and textarea according to meta data. To disable this behavior set auto_populate_controls = false.</p>


<h1><a name='adding_search'>Adding Search</a></h1>
In versions &lt;= 2015-02-27 search was automatic. Now search requires grid_sql and grid_sql_param to be defined.

<pre>
Example:

$lm->grid_show_search_box = true;

$lm->grid_sql = "select m.market_id, m.market_name, m.photo, m.contact_email, c.country_name, m.is_active, m.create_date, market_id from market m left join country c on m.country_id = c.country_id where coalesce(m.market_name, '') like :_search or coalesce(m.contact_email, '') like :_search or coalesce(c.country_name, '') like :_search order by m.market_id desc";
$lm->grid_sql_param[':_search'] = '%' . trim($_REQUEST['_search'] ?? '') . '%';
</pre>


<h1><a name='customizing_the_search_form'>Customizing the Search Form</a></h1>
Sample of custom search form with <b>two</b> search boxes.
<pre>
Example:

$lm-&gt;grid_show_search_box = true; // show html defined in grid_search_box

$new_search_1 = $lm->clean_out($_REQUEST['new_search_1'] ?? '');
$new_search_2 = $lm->clean_out($_REQUEST['new_search_2'] ?? '');

// redefine our own search form with two inputs instead of the default one
$lm-&gt;grid_search_box = "
&lt;form class='lm_search_box'&gt;
    &lt;input type='text' name='new_search_1' value='$new_search_1' size='20' class='lm_search_input' placeholder='market'&gt;
    &lt;input type='text' name='new_search_2' value='$new_search_2' size='20' class='lm_search_input' placeholder='email'&gt;
    &lt;input type='submit' value='Search' class='lm_button'&gt;
    &lt;input type='hidden' name='action' value='search'&gt;
&lt;/form&gt;
"; 

$lm->query_string_list = "new_search_1,new_search_2"; // add variable names to querystring so search is saved while paging, sorting, and editing

// set name parameters
$lm-&gt;grid_sql_param[':new_search_1'] =  '%' . trim($_REQUEST['new_search_1'] ?? '') . '%';
$lm-&gt;grid_sql_param[':new_search_2'] =  '%' . trim($_REQUEST['new_search_2'] ?? '') . '%';

// define sql
$lm-&gt;grid_sql = "
select 
  m.market_id
, m.market_name
, m.photo
, m.contact_email
, c.country_name
, m.is_active
, m.create_date
, m.market_id 
from  market m 
left  
join  country c 
on    m.country_id = c.country_id 
where coalesce(m.market_name, '')   like :new_search_1
and   coalesce(m.contact_email, '') like :new_search_2
order by m.market_id desc
";

</pre>


<h1><a name='defining_separate_add_and_edit_forms'>Defining Separate Add and Edit Forms</a></h1>
<p>Different forms may be defined for adding records versus editing records.</p>

<pre>
Example:

if(!isset($_REQUEST['market_id'])){
    // form for adding records
    $lm->form_sql = 'select * from market where market_id = :market_id';
}
else{
    // form for editing records
    $lm->form_sql = 'select market_id, market_name, country_id, photo, is_active, create_date, notes from market where market_id = :market_id';
}

$lm->form_sql_param[':market_id'] = $_REQUEST['market_id'] ?? 0; 

</pre>


<h1><a name='validation'>Validation</a></h1>
<p>Server-side validation displays an error message next to the form input. <br>A general error message is displayed at the top and can be defined with the $lm-&gt;validate_text_general string setting. </p>
<p>Separate arrays are used for inserts and updates. If the validate needs are the same for both inserts and updates then just copy the existing array to duplicate the rules.</p>
<p>Alternatively, validation can be handled in On Insert/Update/Delete events <a href='#on_insert_update_delete_events'>(see below)</a>.</p>
<pre>
$lm-gt;on_insert_validate["field_name"] = array("regexp" => string, "error_msg" => string [, "placeholder" => string [, "optional" => boolean]]);

$lm-gt;on_update_validate["field_name"] = array("regexp" => string, "error_msg" => string [, "placeholder" => string [, "optional" => boolean]]);
</pre>

<pre class="gray">
// old style syntax still supported (changed in version 2019-01-10)
// same values, without keys 
$lm-gt;on_insert_validate["field_name"] = array(string regexp, string error_msg, string placeholder, boolean optional);
</pre>


<ul>
<li><b>regexp</b> regular expression /slashes required/, 'email', or user defined function name.</li>
<li><b>error_msg</b> Error message to be displayed next to the element.</li>
<li><b>placeholder</b> Populate placeholder attribute of input with a tip. If placeholder is not applicable, text is displayed along side input. </li>
<li><b>optional</b> Is this input optional? Default is false. </li>

</ul>

<pre>
Example: 

// validation using regular expression, slashes required
$lm->on_insert_validate["market_name"]   = array("regexp" => "/.+/", "error_msg" => "Missing Market Name", "placeholder" => "This is Required"); 

// built-in "email" validation
$lm->on_insert_validate["contact_email"] = array("regexp" => "email", "error_msg" => "Missing or invalid Email", "placeholder" => "Optional Email", "optional" => true);

// user defined validation
$lm->on_insert_validate["country_id"]    = array("regexp" => "my_validate", "error_msg" => "Missing or invalid country", "placeholder" => "Required"); 

// copy array - same setting for updates
$lm->on_update_validate = $lm->on_insert_validate;

// user defined validation example
function my_validate(){

    if(empty($_POST['country_id'])
        return false; // fail
    else
        return true; // success

}
</pre>


<h1><a name='on_insert_update_delete_events'>On Insert/Update/Delete Events</a></h1>
<p>On Insert/Update/Delete functions are useful for validation and data manipulation.</p>
<p>These functions can be also be used for validation. Strings returned by the user defined functions are displayed at the top as error messages and the insert/update/delete action is halted.</p>

<ul>
<li>on_insert_user_function</li>
<li>on_update_user_function</li>
<li>on_delete_user_function</li>
<li>on_update_grid_user_function</li>
</ul>

<pre>
Example: 

$lm-&gt;on_update_user_function = 'my_hash_update';

function my_hash_update(){

    // form_sql had an additional blank string column, example: "select '' as password_reset ..."
    $password = $_POST['password_reset'] ?? '';

    // no password sent, nothing to do
    if(mb_strlen($password) == 0)
        return "";

    // returned string will be displayed as an error message
    if(mb_strlen($password) &gt; 100)
        return "Password too long";

    if(mb_strlen($password) &lt; 5)
        return "Password too short";

    // set optional password      
    $_POST['password'] = password_hash($password, PASSWORD_DEFAULT);
    
}


$lm-&gt;on_insert_user_function = 'my_hash_insert';

function my_hash_insert(){

    $password = $_POST['password'] ?? '';

    // returned string will be displayed as an error message
    if(mb_strlen($password) &gt; 100)
        return "Password too long";

    if(mb_strlen($password) &lt; 5)
        return "Password too short";

    // overwrite password field     
    $_POST['password'] = password_hash($password, PASSWORD_DEFAULT);
    
}

</pre>


<a name='after_insert_update_delete_events'></a>
<h1>After Insert/Update/Delete Events</h1>

<p>User define functions can be defined in the properties listed below.</p>
<p>after_ events are useful for running trigger-like actions. The after_insert_user_function event uniquely receives the identity id of the newly added record.</p>

<ul>
<li>after_insert_user_function</li>
<li>after_update_user_function</li>
<li>after_delete_user_function</li>
<li>after_update_grid_user_function</li>
</ul>

<pre>
Example: 

$lm->after_insert_user_function = 'my_after_insert';

function my_after_insert($id){
    
    // after_insert_user_function is the only action to get the identity id
    // now that the record is added we can do anything we need to

    global $lm;

    $sql_param = array(':market_id' =&gt; $id);
    $sql = "insert into related_table(field1, market_id) values (now(), :market_id)";
    $lm->query($sql, $sql_param);

}
</pre>


<a name='cast_user_function'></a>
<h1>Cast Data Based on Colunm Name</h1>

<p>The cast_user_function array is used for storing column names and their corresponding cast function.</p>

<pre>
Example: 

// when using the checkbox input maybe we'd want unchecked to be 0 instead of null 
$lm->cast_user_function['is_active'] = 'my_cast';

function my_cast($val){
    
    return intval($val);
    
}
</pre>


<h1><a name='cross_site_request_forgery_protection_token'>Cross Site Request Forgery Protection Token</a></h1>
<p>This script does not validate csrf itself but has a placeholder csrf variable from loaded from $_SESSION['_csrf']. To protect from csrf, place your nonce token in $_SESSION['_csrf'] and validate the csrf on POST commands.</p>

<pre>
Example: 

// in your login script give the user a random string token
$_SESSION['_csrf'] = base64_encode(openssl_random_pseudo_bytes(15));

// somewhere else, before the page is processed, run some code like this 
if($_SERVER['REQUEST_METHOD'] === 'POST' && $_SESSION['_csrf'] != $_POST['_csrf'])
    die('Invalid csrf token');
</pre>


<h1><a name='i18n'>i18n/Internationalization</a></h1>
<p>By default LM datagrid is us-en (United States - English).
At this time very few country-language files are available. Check the i18n folder to see what is available.
If your coutry-language is not available consider making an open source contribution using i18n/template.php</p>
<pre>
Example: 

// create LM object, pass in PDO connection, see i18n folder for language + country options 
$lm = new lazy_mofo($dbh, 'en-us'); 

</pre>


<h1><a name='date_formats'>Date Formats</a></h1>
<p>Lazy Mofo will automatically identify date and datetime fields. All output of dates and datetimes are output in the format defined by member variables date_out and datetime_out.</p>
<pre>
Example: 

// default US format
$lm-&gt;date_out = 'm/d/Y';
$lm-&gt;datetime_out = 'm/d/Y h:i A';

// or set non US date format
$lm-&gt;date_out = 'd/m/Y';
$lm-&gt;datetime_out = 'd/m/Y H:i';

// or use a ISO-ish date format for html5 date inputs
$lm-&gt;date_out = 'Y-m-d';
$lm-&gt;datetime_out = 'Y-m-d H:i';

</pre>


<h1><a name='decimal_separator'>Decimal Separator</a></h1>
<p>Comma can be used as a decimal separator, this affects input only.
<br>Output must be localized using mysql's format() function.</p>

<pre>
Example: 

// using comma for separator, this affects input only, not displayed format
$lm-&gt;decimal_separator = ',';


// using mysql's format() for decimal output localization
$lm->form_sql = "
select
  market_id 
, format(price, 2, 'es_ES') as price 
, market_name
from  market
where market_id = :market_id
";

<a href='https://dev.mysql.com/doc/refman/8.0/en/locale-support.html' target='_blank'>https://dev.mysql.com/doc/refman/8.0/en/locale-support.html</a>

</pre>


<h1><a name='adding_jquery_ui_datepicker'>Adding JQuery UI Datepicker</a></h1>
<pre>

&lt;link rel='stylesheet' href='//ajax.googleapis.com/ajax/libs/jqueryui/1.10.4/themes/smoothness/jquery-ui.css'&gt;
&lt;script src='//ajax.googleapis.com/ajax/libs/jquery/1.11.0/jquery.min.js'&gt;&lt;/script&gt;
&lt;script src='//ajax.googleapis.com/ajax/libs/jqueryui/1.10.4/jquery-ui.min.js'&gt;&lt;/script&gt;
&lt;script src='//ajax.googleapis.com/ajax/libs/jqueryui/1.10.4/i18n/jquery-ui-i18n.min.js'&gt;&lt;/script&gt;
&lt;script&gt;
$(function() {

    
    $('input[name=create_date]').datepicker(); 
    

    // non US date example dd/mm/yy and week starting on monday(1) instead of sunday(0)
    // also set date_out and datetime_out properties with the desired date format $lm-&gt;date_out = 'd/m/Y'; $lm-&gt;datetime_out = 'd/m/Y H:i';
    /*
    var options = $.extend({},
        $.datepicker.regional['it'], {
            dateFormat: 'mm/dd/yyyy',
            changeMonth: true,
            changeYear: true,
            highlightWeek: true,
            firstDay: 1,
        }
    );
    $('input.lm_create_date').datepicker(options);
    */    


});
&lt;/script&gt;

</pre>


<h1><a name='export_to_csv'>Export to CSV</a></h1>
<p>Clicking the Export link will convert the grid output to a CSV file for downloading.
Output buffering (ob_start) must be used at the beginning of the script for the export to CSV feature to function properly.</p>


<h1><a name='more_features_and_settings'>More Features and Settings</a></h1>
<p>View class source code to see all the property settings.</p>


</body>
</html>