Search:
This Site
Wiki
Home
Forum
Documentation
Videos
Bug Tracker
Wiki
Login
You are here:
Wiki :: List
Twitter Feed
Xataface Maillist
Sign up to receive the Xataface news letter with weekly updates and development tips.
Email:
Export CSV
Export XML
RSS
Found 135 records
Prev
1
2
3
4
5
Next
Showing
Results per page
Page name
Page id
Page title
Content
Keywords
Language
Original page
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
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
__field__permissions
50
__field__permissions
This method can be used to set the default permissions for all fields in a designated table, when specified in that table's delegate class. It comes in handy in situations when you want to deny access to all fields except for those designated, rather then
en
0
fieldgroup_template
51
fieldgroup_template
==Using a custom template for a field group on the edit form== [[toc]] Xataface allows you to partition your fields into ''groups'' so that similar fields are grouped together on the edit form. The default layout of the fields remains simply vertic
en
0
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
fieldname__permissions
53
fieldname__permissions
==fieldname__permissions() method== [[toc]] The fieldname__permissions() methods will allow you to define custom permissions on a particular field in the [[delegate class]]. For example to specify permissions on a field named ''foo'' you would defi
en
0
blob
55
blob
en
0
struct
56
struct
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
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
widget:type_textarea
60
widget:type_textarea
en
0
Customizing_the_look_and_feel_of_a_row_or_a_cell
62
Customizing_the_look_and_feel_of_a_row_or_a_cell
==How to customize the look and feel of elements in the list view== ===Create a method in a delegate class=== In the delegate class, the method ''css__tableRowClass'' is implemented, like in this example : class tables_journal_interventions
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
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
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
grid
67
grid
==widget:type = grid== Suppose we have two tables, tbl_organisation and tbl_individuals, in the edit view for a record in the organisations table (tbl_organisations) we also want to be able to view and edit the individuals within this organisation we c
en
0
checkbox
69
checkbox
==The checkbox widget== In the [[fields.ini file]] you can specify a field to be edited using a checkbox widget by setting [[widget:type]] to [[checkbox]]. A checkbox widget can function in 2 different ways depending on the parameters that you assign
en
0
Creating_Printable_Reports
82
Creating a Custom Printable Report
==Creating a Printable Report== [[toc]] It is often useful to provide your users with a printable report that is generated from your database. Although Xataface doesn't include an explicit reporting module to allow the end users to create their own
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
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
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
file
89
==Dynamic select boxes== To create two select boxes whose one is dependent (slave) of the other (master), we need to use some javascript with Jason. Create the valuelists.ini: ;valuelist for the slave [slaves_list] __sql__ = "select sla
en
Dynamic_select_boxes
90
==Dynamic select boxes== To create two select boxes whose one is dependent (slave) of the other (master), we need to use some javascript with Jason. Create the valuelists.ini: ;valuelist for the slave [slaves_list] __sql__ = "select sla
en
setSecurityFilters
91
setSecurityFilter() method
== Example == In the delegate class for the users table:
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
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
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
Clean_the_html_for_the_export
178
Clean the HTML to export data
==Clean HTML tags and entities to export your data== #Override the display() of the field to strip the tags... but this would affect all parts of the application where the HTML fields are displayed. #Create a grafted field, then override its display to
en
test_page_34
177
Hello World
Hello world
en
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
Found 135 records
Prev
1
2
3
4
5
Next
Showing
Results per page
Powered by Xataface
(c) 2005-2010 All rights reserved