Wiki - Xataface Wiki

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

Page name	Page id	Page title	Content	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

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

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

__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

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

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

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

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

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

ShoppingCart	31	ShoppingCart	==Xataface Shopping Cart Module== [[toc]] Status: Under development Current Version: 0.2 ===Synopsis=== Add a shopping cart to your xataface application. You can treat any record as a product that can be sold. Includes Paypal connectivity,	en	0

DataGrid	32	DataGrid	==Xataface DataGrid Module== Created by Steve Hannah, [http://weblite.ca Web Lite Solutions Corp.] ===Synopsis=== The Xataface DataGrid module uses the Ext DataGrid component (http://extjs.com) to add an editable grid component to your Xataface a	en	0

after_action_new	33	after_action_new	==after_action_new trigger== [[toc]] This trigger is called after the '''new''' action is successfully completed. This trigger can be defined in the table [[Delegate class methods\|delegate class]] and is often used to redirect to a particular page	en	0

widget:editor	35	widget:editor	==widget:editor fields.ini directive== Return to [[fields.ini file]] [[toc]] The widget:editor directive is applicable in the [[fields.ini file]]. It specifies the type of HTML editor that should be used. This directive is only used when [[widg	en	0

about	36	about	==About Xataface== [[toc]] Xataface is a flexible and shapable skin that sits on top of MySQL, making it accessible to every-day users. It automatically generates the appropriate forms, lists, and menus for a user to interact with the database witho	en	0

Drag_and_Drop_Reordering_of_Relationships	39	Drag_and_Drop_Reordering_of_Relationships	==Drag and Drop Reordering of Related Records in Xataface== One powerful aspect of Xataface is its abstraction of relationships between tables. Once you define a relationship users can browse related records, add new and existing related records, and	en	0

getFeedItem	41	getFeedItem	==getFeedItem() Delegate Class Method== [[toc]] ===Synopsis:=== The getFeedItem() method of a table [[Delegate class methods\|delegate class]] returns an associative array of parameters for a record as it should appear as part of an [[Introduction	en	0

getFeed	42	getFeed	==getFeed() Delegate Class Method== [[toc]] ===Synopsis:=== The getFeed() method of a table [[Delegate class methods\|delegate class]] or [[Application Delegate Class\|application delegate class]] returns an associative array of parameters to confi	en	0

Calendar_Action	43	Calendar_Action	==Calendar Action== [[toc]] Xataface 1.0 includes a built-in calendar action that is disabled by default. If enabled, it allows you to view the records in any found set as a calendar of events, as follows:	en	0

widget:atts	46	widget:atts	==widget:atts Directive Reference== The widget:atts directive in the fields.ini file allows any arbitrary HTML attributes to be added to any of the fields. It may also be used to specify javascript event handler functions that the widget should call u	en	0

visibility:fieldName	47	visibility:fieldName	==Example== visibility:ConferenceID = hidden This will make the ConferenceID in the relationship list view disappear.	en	0

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