|Page name ||Page id ||Page title ||Content ||Keywords ||Language ||Original page |
| sql_delegate_method|| 87|| __sql__ Delegate Method|| return to [[Delegate class methods]]
The __sql__ delegate class method can be defined in any delegate class to specify the SQL query that should be used to fetch records for a given table. This method overrides the [[__sql__]] direct|| __sql__, SQL queries, delegate class|| en|| |
| __global__|| 106|| __global__ section for the fields.ini file|| Return to [[fields.ini file]]
The fields.ini file supports a __global__ section that applies to all fields in the current table. This is particularly useful for setting up default functionality that you wish to see on all || __global__, fields.ini, visibility:list|| en|| |
| _auth|| 97|| _auth section of the conf.ini file|| [[conf.ini file|Return to conf.ini file]]
The ''_auth'' section of the conf.ini file includes configuration directives to enable authentication in a Xataface application. For more information about authentication and regis|| _auth,authentication,conf.ini file,allow_register|| en|| |
| XataJax_Compiler|| 114|| Introduction to the XataJax Compiler|| Return to [[XataJax]]
'''DISCLAIMER''': This page introduces features that require Xataface 1.3 or higher. At present (Jan. 2011) only Xataface 1.2.6 has been released to the public.
| XataJax|| 113|| Introduction to XataJax|| [[toc]]
| Introduction_to_the_Xataface_API|| 101|| Introduction to the Xataface API|| Back to [http://xataface.com/wiki the wiki]
Xataface is provides an API to help in developing your own custom actions. This API includes objects and functions to more easily interact with the database (i.e. search, edit, d|| xataface api, df_get_record, df_get_records_array, Dataface_Record, Editing, Saving, Loading, Searching|| en|| |
| GettingStarted:customizing|| 76|| Customizing Field labels, descriptions, and widgets|| ==Customizing Field labels, descriptions, and widgets==
Using simple INI configuration files, you can customize the look and feel of your application. You can change widgets, labels, field descriptions, and more.
In the previous 2 sections we learned || widget labels descriptions onclick handlers|| en|| |
| GettingStarted:valuelists|| 77|| Using Valuelists|| ==Using Value-lists==
Value-lists serve as vocabularies that can be used for fields such as select lists, checkbox groups, and auto-complete fields.
So far we have not used any enumerated fields such as select lists, checkbox groups, or auto-complet|| valuelists, __sql__, select lists, checkbox options,checkbox groups,vocabularies|| en|| |
| valuelists.ini_file|| 5|| valuelists.ini_file|| ==valuelists.ini file Reference==
The valuelists.ini file stores value lists that can be used as [[vocabulary|vocabularies]] for select lists, checkbox groups, and other widgets the provide the user with options to choose from.
Each table|| valuelists, dynamic valuelists, programmatically defined valuelists|| en|| 0|
| validators|| 95|| validators:NAME fields.ini directive|| Return to [[fields.ini file]]
In the fields.ini file you can specify validation rules to be applied to any field by adding the validators:NAME directive in that field's section of the [[fields.ini file]].
===Available Va|| validation, form validation, validators,validator:name|| en|| |
| validators:VALIDATOR_NAME:message|| 96|| validators:VALIDATOR_NAME:message directive for the fields.ini file|| Return to [[fields.ini file]]
If you want to customize the error message associated with a particular [[validator|validation rule]] you can use the validators:VALIDATOR_NAME:message directive in the fields.ini file.
===F|| validation messages,error messages,form validation rules|| en|| |
| fieldname__validate|| 94|| fieldname__validate Delegate Class Method|| Return to [[Delegate class methods]]
Xataface allows you to add validation on any particular field in table by adding a fieldname__validate method to the table's delegate class of the form:
function myfield__valida|| validate, validation, delegate class validation, custom validator|| en|| |
| URL_Conventions|| 37|| URL_Conventions|| ==Xataface URL Conventions==
Xataface adheres to a few simple URL conventions for all of its actions. When you understand how Xataface URLs work you begin to get far more out of your applications. By specifying the appropriate query parame|| URL Conventions, GET Parameters, POST parameters, Request Parameters|| en|| 0|
| How_to_build_a_PHP_MySQL_Application_with_4_lines_of_code|| 38|| How to build a PHP MySQL Application with 4 lines of code|| '''The [http://xataface.com Xataface Application Framework] allows you to convert your existing MySQL database into a full-fledged with as little as 4 lines of code. And it's Not a code generator.'''
This article is intended to spark intere|| tutorial, getting started, installation, first app, 4 lines of code|| en|| 0|
| GettingStarted:triggers|| 81|| Triggers|| ==Triggers==
Triggers are methods that can be defined to carry out custom behaviors when certain events occur in the application (e.g., when records are saved, inserted, or deleted).
Triggers are generally regarded as one of the more advanced featur|| triggers, beforeSave, afterSave, beforeInsert, afterInsert,sending email|| en|| |
| beforeSave|| 109|| beforeSave Trigger|| Back to [[Delegate class methods]]
The beforeSave trigger can be implemented in any table's [[delegate class|Delegate Class Methods]] to perform functionality that should be run *before* a record of that table is saved.|| triggers, beforeSave,|| en|| |
| Contribute_to_Xataface_Translation_Project|| 110|| How to Contribute Translations|| [[toc]]
Xataface stores its translations in INI files in its lang directory, one for each language. You can develop your own translation by first copying the en.ini file to xx.ini (where xx is the ISO language code for the language you|| Translations, Google Spreadsheets, en.ini, fr.ini|| en|| |
| timestamp|| 44|| timestamp|| Return to [[fields.ini file]]
A very simple sample of this could be your table contains the table date_created as a type of date. In your fields.ini, you would include this:
T|| timestamp, date, datetime|| en|| 0|
| xataface_templates|| 23|| xataface_templates|| ==Xataface Templates==
Xataface uses the [http://smarty.php.net Smarty Template Engine] to power all of its templates. Templates are stored in the one of the following locations:
* %SITE_ROOT%/templa|| templates, plugins, smarty|| en|| 0|
| secure|| 88|| secure fields.ini directive|| [[fields.ini file]] directive used only with [[container fields]]. If this flag is set, then the field contents will be treated in a secure manner and will obey the application permissions. If this directive is not set, then uploaded files in [[containe|| secure,fields.ini file|| en|| |
| Delegate_class_methods|| 7|| Delegate_class_methods|| ==Delegate Class Reference==
A delegate class is a PHP class that complements a particular table with custom bahaviors. Basic table metadata can be supplied using the [[fields.ini file]], however some things are better customized using PHP.|| RSS,Feeds,delegate classes, triggers|| en|| 0|
| Introduction_to_RSS_Feeds_in_Xataface|| 40|| Introduction_to_RSS_Feeds_in_Xataface|| ==Introduction to RSS Feeds in Xataface==
A default Xataface application provides RSS feeds to any found set in your application. This article explains a little bit about RSS and how you can configure Xataface to give you the desired result|| RSS Feeds|| en|| 0|
| relationships.ini_file|| 20|| relationships.ini_file|| ==relationships.ini File Reference==
The relationship.ini file is a configuration file which is associated with a single table of a database application. It provides metadata about the table's relationships to other tables|| relationships.ini file, relationships|| en|| 0|
| Relationship_Permissions|| 111|| Relationship Permissions|| [[toc]]
As relationships are a core feature of Xataface, it is helpful to understand how to handle permissions on related records. Even if you apply permissions to every table individually, you need to take into account the relationshi|| relationships, permissions, rel_relationshipname__permissions, getPermissions, permissions.ini|| en|| |
| GettingStarted:relationships|| 78|| Relationships|| ==Relationships==
Xataface allows you to define relationships between tables using the relationships.ini file.
Xataface applications without relationships between tables can be quite boring. In our FacultyOfWidgetry application, we have implicitly d|| relationships|| en|| |
| after_action_activate|| 181|| after_action_activate Delegate Class Method|| Return to [[Application Delegate Class]]
The '''after_action_activate''' hook is a method that can be defined in the [[Application Delegate Class]] which is called after an account has been activated via the registration process. The full|| Registration, activation, register, activate, users|| en|| |
| registration_form|| 98|| Setting up User Registration|| [[toc]]
Xataface optionally enables you to allow users to register for an account in your application. If your ''users'' table includes a column for email, it will also perform email validation before the account is activated. Befor|| registration form, _auth, authentication|| en|| |
| Using_RecordGrid|| 115|| Using RecordGrid|| ==Xataface RecordGrid Class and Template==
Also see [http://lamp.weblite.ca/dataface-0.6/docs/index.php?-table=Classes&-action=browse&ClassID=30| RecordGrid in the API Doc].
As we learned in '''[http://xat|| RecordGrid, Dataface_RecordGrid, data in tabular form|| en|| |
| field__pullValue|| 104|| field__pullValue delegate class method|| [[toc]]
The field__pullValue() delegate class method can be used to transform database from the database for use in an edit/new record form. Sometimes it is the case that we want users to be able to work with data differently than it is stored in the || pushValue, pullValue|| en|| |
| field__pushValue|| 105|| || [[toc]]
The field__pushValue() delegate class method can be used to transform a field value as entered in the edit form into a format that can be stored in the database.. Sometimes it is the case that we want users to be able to work with data differe|| pullValue, pushValue|| en|| |