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
1
2
3
4
5
Next
Showing
Results per page
Page name
Page id
Page title
Content
Keywords
Language
Original page
__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
__global__
106
__global__ section for the fields.ini file
Return to [[fields.ini file]] [[toc]] ===Synopsis=== 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
__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
_output_cache
45
The Xataface Output Cache
Note: There was a bug in the output cache affecting Xataface version 1.0 to 1.3rc1. If you are using a version of Xataface older than 1.3rc2 then you should either disable the output cache, or replace the Dataface/Outpu
output cache
en
0
_auth
97
_auth section of the conf.ini file
[[conf.ini file|Return to conf.ini file]] [[toc]] ===Synopsis=== 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. [[toc]] ===Synopsis=== The XataJax compiler is a Javascript
XataJax, compiler, javascript, css, compiler
en
XataJax
113
Introduction to XataJax
[[toc]] Xataface 1.3 comes with a new module [[XataJax]] which comes installed standard. [[XataJax]] serves as a foundation for Javascript/AJAX powered Xataface applications and will hopefully usher in a new fresh generation of Xataface powered applic
XataJax, Ajax, Web 2.0
en
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
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
widget:type_textarea
60
widget:type_textarea
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: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: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
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
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
validators:VALIDATOR_NAME:message
96
validators:VALIDATOR_NAME:message directive for the fields.ini file
Return to [[fields.ini file]] [[toc]] ===Synopsis=== 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
validators
95
validators:NAME fields.ini directive
Return to [[fields.ini file]] [[toc]] ===Synopsis=== 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
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
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]. [[toc collapse=0]] ===Introduction=== As we learned in '''[http://xat
RecordGrid, Dataface_RecordGrid, data in tabular form
en
URL_Conventions
37
URL_Conventions
==Xataface URL Conventions== [[toc]] 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
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
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: [date_created] timestamp=insert widget:type=hidden T
timestamp, date, datetime
en
0
test_page_34
177
Hello World
Hello world
en
testpage2
2
testpage2
Another test page [[testpage]]
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
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
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
struct
56
struct
en
0
sql_delegate_method
87
__sql__ Delegate Method
return to [[Delegate class methods]] ===Synopsis=== 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
Found 135 records
1
2
3
4
5
Next
Showing
Results per page
Powered by Xataface
(c) 2005-2010 All rights reserved