Wiki - Xataface Wiki

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

Page name	Page id	Page title	Content	Language	Original page
How_to_Add_Custom_Sections_to_View_Tab	52	How_to_Add_Custom_Sections_to_View_Tab	==How to Add Custom Sections to the View tab== [[toc]] The ''View'' tab is intended to give the user a detailed view of the contents of a record. By default it shows the values of each non-empty field grouped into their appropriate field groups. I	en	0

How_to_authenticate_users_with_LDAP_or_Active_Directory	64	How_to_authenticate_users_with_LDAP_or_Active_Directory	==How to authenticate users with LDAP or Active Directory==	en	0

How_to_granulate_permissions_on_each_field	63	How_to_granulate_permissions_on_each_field	==How to granulate permissions on each field== To reach this aim, there is the method fieldname__permissions to place into the delegate class of the table. ===Getting the role=== First it is necessary to know the user's role. For this, the metho	en	0

http://xataface.com/documentation/how-to/site_with_backoffice	85	How to build a site with an optional login form	==How to build a site with an optional login form== To publish a public site with data without any need to login to access, here is the code : function getPermissions(&$record){ if ( isAdmin() ) return Dataface_PermissionsTool::ALL();	en

http://xataface.com/documentation/how-to/site_with_backoffice_How_to_build_a_site_with_a_backoffice_	84	A site with a backoffice	==A site with a backoffice== To create a site with a backoffice for the administrator, so that the visitors do not have to log in to read the pages, you add this code in the ApplicationDelegate.php file in the conf directory : function getPerm	en

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

init	140	init() Delegate Class Method	== Synopsis == This method is called once, just after the table is loaded for the first time. It allows you to specify initialization details, such as [[setSecurityFilters\|security filters]]. Note that it takes a single parameter: a Dataface_Table o	en

list:type	128	list:type relationships.ini file directive	Return to [[relationships.ini file]] [[toc]] The list:type directive allows you to override the default list that is used to display related records. As of Xataface 1.3 there is only one possible value that will have any effect on this directive: "	en

meta:class	127	meta:class relationships.ini file directive	Return to [[relationships.ini file]] [[toc]] The ''meta:class'' directive allows you to ascribe special meaning to a relationship which Xataface can use in various parts of your application to provide enhanced capabilities. For example you can sp	en

no_access_text	59	no_access_text	Whenever the NO_ACCESS permission is given for a field, normally the text NO ACCESS appears. But we might want to display another text. Here is an example of the text subscribe is used instead of NO ACCESS whenever the NO_ACCESS permissions is given.	en	0

Selected_Records_Actions	58	Selected_Records_Actions	==Creating a Custom ''Selected Records'' Action== [[toc]] If you view the ''list'' tab in any of your Xataface applications, you'll notice that there is a checkbox next to each row of the list, and there are a number of actions listed at the bottom	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

setSecurityFilters	91	setSecurityFilter() method	== Example == In the delegate class for the users table:	en

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

site_with_backoffice	86		==How to build a site with an optional login form== To publish a public site with data without any need to login to access, here is the code : function getPermissions(&$record){ if ( isAdmin() ) return Dataface_PermissionsTool::ALL();	en

struct	56	struct		en	0

tab	48	tab	==tab directive of the fields.ini file== [[toc]] The ''tab'' directive of the [[fields.ini file]] specifies which tab of the record edit form a field should be displayed on. Xataface supports multiple tabs on the edit form by way of this ''tab'' di	en	0

table	66	table	When using widget:type table, it will store the data as XML. So the field type must be TEXT (or varchar... but text is better). You can decide which columns you want in the table by creating sub-fields in your fields.ini file as follows: Suppose you	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

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

test_page_34	177	Hello World	Hello world	en

Troubleshooting	49	Troubleshooting	==Xataface Troubleshooting== This document is intended to help Xataface developers through some of the most common issues. [[toc]] ==All I get is a blank white screen!== The most common issue mentioned in the forums is that an application come	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

viewable_editable_fields	180	How to make a field editable for some users and only viewable for some other users	If we want only some users to edit a field and some other users only to view that field, then we need to define a '''fieldX__permissions()''' method for that field which gives desired permissions for specific users. One solution is as below. ==permi	en

visibility:fieldName	47	visibility:fieldName	==Example== visibility:ConferenceID = hidden This will make the ConferenceID in the relationship list view disappear.	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

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

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

widget:type_textarea	60	widget:type_textarea		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

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