Wiki - Xataface Wiki

Found 135 records
1
2
3
4
5
Next
Showing Results per page

Page name	Page id	Page title	Content	Keywords	Language	Original page
index_page	1	index_page	==Documentation== [[toc]] ===Introductory=== * [[about\|About Xataface]] * [http://xataface.com/documentation/tutorial/getting_started Getting Started Tutorial] * [[How to build a PHP MySQL Application with 4 lines of code]] * [[Troubleshooting		en	0

testpage2	2	testpage2	Another test page [[testpage]]		en	0

fields.ini_file	3	fields.ini_file	==fields.ini File Reference== [[toc]] ===Overview=== The fields.ini file is a configuration file which is associated with a single table of a database application. It provides metadata about the table's fields to help Xataface dictate how they s	fields.ini directives	en	0

widget:type	4	widget:type	==widget:type Directive Reference== The widget:type directive in the [[fields.ini file]] specifies the type of widget that should be used to edit a particular field in HTML forms. Xataface uses [http://pear.php.net/package/HTML_QuickForm/ HTML_QuickFo		en	0

valuelists.ini_file	5	valuelists.ini_file	==valuelists.ini file Reference== [[toc]] 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

actions.ini_file	6	actions.ini_file	==actions.ini file Reference== [[toc]] The actions.ini file stores information about the various [[action]]s that can be performed by your application. An action may be manifested in two ways: # As a web page # As a menu item And there is no		en	0

Delegate_class_methods	7	Delegate_class_methods	==Delegate Class Reference== [[toc]] 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

Internet_Media_Manager	8	Internet Media Manager	'''Manage your videos and photos all in one place''' [[toc]] ===Watch the Guided Tour (6 minutes)===	Internet Media Manager,resize photos,image gallery,photo gallery,video gallery	en	0

calendar	100	Calendar Widget	Back to [[widget:type]] [[toc]] ===Synopsis=== The calendar widget is the default widget for editing date and datetime fields. It is javascript pop-up calendar that allows users to select date and time visually. It can be configured to allow di	calendar widget, fields.ini file, widget:type	en

__prefs__	9	__prefs__	==__prefs__ fields.ini Section== A global section of the [[fields.ini file]] that sets the preferences for the given table and its records. E.g. [__prefs__] hide_posted_by=1 ; Hides the "Posted by" text in glance lists (e.g. related re		en	0

preferences	10	preferences	==Xataface Preferences== [[toc]] Xataface preferences can be defined in 3 ways: # In the ''[_prefs]'' section of rhe [[conf.ini file]] for global static preferences. # Implementing the [[getPreferences]] method in the [[Application Delegate Clas	preferences, prefs, getPreferences	en	0

block__blockname	11	block__blockname	===Available Blocks=== This is a grep to show the blocks that are defined in Xataface templates: * Dataface_ActionsMenu.html:actions_menu_head * Dataface_ActionsMenu.html:actions_menu_tail * Dataface_Add_Existing_Related_Record.html:before_add_exi		en	0

Application_Delegate_Class	12	Application Delegate Class	[[toc]] ===Synopsis=== The application delegate class is similar to the [[Delegate_class_methods\|table_delegate_class]] except that it is applicable to the application as a whole, not just one table. It allows the developer to implement hooks that	application delegate class	en	0

beforeRegister	13	beforeRegister	==beforeRegister() Trigger== A trigger that can be implemented in the [[Application Delegate Class]] or the [[Table Delegate Class]], to be executed before the registration form is saved. This can be used to perform some custom actions like emailing t		en	0

afterRegister	14	afterRegister	==afterRegister() Trigger== A trigger that can be implemented in the [[Application Delegate Class]] or the [[Table Delegate Class]], to be executed after the registration form is saved. This can be used to perform some custom actions like emailing the		en	0

validateRegistrationForm	15	validateRegistrationForm	==validateRegistrationForm() hook== A hook that validates the input into the user registration form to make sure that the input is valid. ===Signature=== function validateRegistrationForm( array $values ) : mixed ====Parameters==== {\| class		en	0

sendRegistrationActivationEmail	16	sendRegistrationActivationEmail	==sendRegistrationActivationEmail() Hook== A hook that can be implemented in the [[Application Delegate Class]] or the [[Table Delegate Class]] to override the sending of an activation email to the user. ===Signature=== function sendRegistrationA		en	0

getRegistrationActivationEmailInfo	17	getRegistrationActivationEmailInfo	==getRegistrationActivationEmailInfo() Hook== A hook that can be implemented in the [[Application Delegate Class]] or the [[Table Delegate Class]] to override the default information that is used to send the registration activation email (the email tha		en	0

getRegistrationActivationEmailSubject	18	getRegistrationActivationEmailSubject	==getRegistrationActivationEmailSubject() Hook== A hook that can be implemented in the [[Application Delegate Class]] or the [[Table Delegate Class]] to override the default registration activation email subject line (the email that the user receives w		en	0

getRegistrationActivationEmailMessage	19	getRegistrationActivationEmailMessage	==getRegistrationActivationEmailSubject() Hook== A hook that can be implemented in the [[Application Delegate Class]] or the [[Table Delegate Class]] to override the default registration activation email message body (the email that the user receives w		en	0

relationships.ini_file	20	relationships.ini_file	==relationships.ini File Reference== [[toc]] ===Overview=== 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

authentication	21	authentication	==Xataface Authentication== [[toc]] Xataface comes with authentication ready to roll out of the box. With a couple of [[_auth\|configuration options]] in the [[conf.ini file]], you can activate the default authentication scheme which uses a table (o	authentication, [_auth], CAS Authentication, Authentication Modules, Basic Authentication, Security	en	0

Writing_Custom_Authentication_Plugins	22	Writing_Custom_Authentication_Plugins	==Writing a Custom Authentication Plugin for Xataface== [[toc]] Xataface has a pluggable [[authentication]] framework that allows you to easily write your own custom [[authentication]] modules to tie in with other systems. Several plugins have alre		en	0

xataface_templates	23	xataface_templates	==Xataface Templates== [[toc]] 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: * %XATAFACE_ROOT%/Dataface/templates * %SITE_ROOT%/templa	templates, plugins, smarty	en	0

templates:tags:use_macro	24	templates:tags:use_macro	==use_macro Template Tag== ===Synopsis=== The use_macro tag includes another template into the current template with the option to override certain sections. ===Parameters=== {\| class="listing listing2" \|- ! Name ! Description ! Version \|		en	0

conf.ini_file	25	conf.ini_file	==conf.ini File== [[toc]] The conf.ini file is where most of the application-level configuration information is stored for a Xataface application. It contains information such as: * database connection information * which tables should appear i		en	0

permissions.ini_file	26	permissions.ini_file	==The permissions.ini File== [[toc]] The permissions.ini file stores custom permissions and roles that can be used by an application. It is an optional file that should be placed in the application root directory (i.e. the same directory where your	permissions.ini, getPermissions, permissions	en	0

filter	27	filter	==The filter attribute of the [[fields.ini file]]== The filter attribute with a value of 1 specifies that a field should be used as a filter field in list view. In list view, any filter fields will provide a select list with all of the possible values		en	0

group	28	group	==group directive in [[fields.ini file]]== The group directive allows you to declare that certain fields of your table should be grouped together on the edit form and the view tab (and other logical places). For example, fields like address, city, sta		en	0

encryption	29	encryption	==encryption [[fields.ini file]] directive== The '''encryption''' directive is meant to be used on password fields only. It specifies that a certain type of encryption is to be used in the storing of values in this field. For example, many PHP/MySQL		en	0

Found 135 records
1
2
3
4
5
Next
Showing Results per page