Changes

From Studiosg
Jump to navigationJump to search
Partial page redesign
Line 1: Line 1: −
Welcome to Simone Giustetti's wiki pages.
+
{{header_en|title=Customizing VtigerCRM date fields| keyword={{Template:keyword_en_vtigercrm}}| description=A guide explaining how to customize the standard behavior of VtigerCRM date fields | link_page=vtigercrm_modificare_il_comportamento_dei_campi_data}}
    +
== '''datefield''' Standard Behavior ==
   −
Languages: '''English''' - [[vtigercrm_modificare_il_comportamento_dei_campi_data | Italiano]]
  −
  −
----
  −
  −
== '''datefield''' Standard Behavior ==
   
Dates are managed through a '''dedicated calendar control''' in VtigerCRM. The control '''automatically suggests the current date''' while inserting new data or updating old ones. The suggestion is usually useful, but could prove annoying in specific contexts: forms containing a lot of date fields for example. Were the form filled with many date fields the user would be pressed to enter each one to correct or remove the unwanted suggestion. A similar scenario requires '''to update the calendar control standard behavior into suggesting a null value'''. The current date should be suggested only upon control explicit selection. Let's see how to update the standard date field behavior in '''release 5.2.1 of VtigerCRM'''.
 
Dates are managed through a '''dedicated calendar control''' in VtigerCRM. The control '''automatically suggests the current date''' while inserting new data or updating old ones. The suggestion is usually useful, but could prove annoying in specific contexts: forms containing a lot of date fields for example. Were the form filled with many date fields the user would be pressed to enter each one to correct or remove the unwanted suggestion. A similar scenario requires '''to update the calendar control standard behavior into suggesting a null value'''. The current date should be suggested only upon control explicit selection. Let's see how to update the standard date field behavior in '''release 5.2.1 of VtigerCRM'''.
       
== VtigerCRM Internals ==
 
== VtigerCRM Internals ==
 +
 
Data processing code is split apart from presentation one in VtigerCRM. Information are retrieved from database, configuration files and other sources, processed then passed to sections of code dedicated to HTML page formatting. '''All web pages provided by the software are based on template models'''. VtigerCRM uses template engine '''Smarty''' to manage templates. All templates consist of text files with a syntax reminiscent of '''HTML''' with the addition of variables and control structures. All template files are saved in directory '''Smarty/templates''' a sub-directory of the VtigerCRM installation tree. The directory contains:
 
Data processing code is split apart from presentation one in VtigerCRM. Information are retrieved from database, configuration files and other sources, processed then passed to sections of code dedicated to HTML page formatting. '''All web pages provided by the software are based on template models'''. VtigerCRM uses template engine '''Smarty''' to manage templates. All templates consist of text files with a syntax reminiscent of '''HTML''' with the addition of variables and control structures. All template files are saved in directory '''Smarty/templates''' a sub-directory of the VtigerCRM installation tree. The directory contains:
 
   bash-4.1# '''ls''' ''-la'' ./Smarty
 
   bash-4.1# '''ls''' ''-la'' ./Smarty
Line 174: Line 171:       −
----
+
{{footer_en | link_page=vtigercrm_modificare_il_comportamento_dei_campi_data}}
 
  −
Languages: '''English''' - [[vtigercrm_modificare_il_comportamento_dei_campi_data | Italiano]]
 

Navigation menu