These files are required to assist pabulumba in administrative tasks, such as handling users, roles, and settings. Where they represent forms available for user input, they have a matching database table name; if they are just text, everything is stored in the file itself.
Once the structure of your system has stabilised, import the files into the database, and then into session variables to dramatically increase page load times (See "Maintenance, Settings, Config data source" and "Import recently changed config files").
File name | Purpose | Form |
---|---|---|
action.xml | Types of action performed by users | Yes |
custom_report.xml | Any ad hoc reports | Yes |
database.php | Connection details for the MySQL database | No |
email_template.xml | Any templates used when sending automated emails | Yes |
file_extension.xml | Allowable extensions when files are uploaded | Yes |
help.xml | Entire contents of the help file | No |
language.xml | Languages supported by pabulumba | Yes |
log.xml | Users actions are recorded in the log and accessed via this file | Yes |
main.xml | Entry point on logging in - the Main page | No |
maintenance.xml | Where links to all configuration files should be located | No |
menu.xml | Common location for the links (buttons) across the top of the pages | No |
message.xml | Feedback, error, and validation messages in all supported languages | Yes |
pabulumba.xsl | Main XSL file | No |
personal_details.xml | Different "view" of the user file to allow limited access to a user's own records | Yes |
reports.xml | Preferred location of listing of all standard, custom, and special reports | No |
role.xml | System roles within pabulumba | Yes |
rule.xml | Definition of rules, if used | Yes |
rule_role.xml | Links rules and roles for flexibility if rules are used | Yes |
search.xml | Template for searching in pabulumba | Yes |
setting.xml | Every single system-wide setting; treat with caution | Yes |
user.xml | Details of system users, including credentials | Yes |
These files assist in demonstrating the flexibility of pabulumba, and can be useful both as a reference and a template to create new files from. They are initially stored in the "demo" folder, and have no effect until copied into the "config" folder. The "demo/menu.xml" file will overwrite the existing "config/menu.xml" files; if it has been modified, make a copy first to restore later if required.
File name | Purpose | Form |
---|---|---|
animal_class.xml | Classes of animals | Yes |
animal_diet.xml | What animals eat | Yes |
animal_habitat.xml | Where animals live | Yes |
animal_predator.xml | What eats animals | Yes |
attendee.xml | People's names | Yes |
car.xml | Toy car parts | Yes |
car_car.xml | Toy car part relationships | Yes |
demo.xml | Page listing all the demonstration forms and reports | Yes |
demo_reference_1.xml | Australian states | Yes |
demo_reference_2.xml | Australian (?) birds | Yes |
demonstration.xml | Form showing all functionality of pabulumba on a single form | Yes |
grid_data.xml | Represents a two-dimensional structure on the demonstration form | Yes |
item.xml | Fake nuclear power plant components | Yes |
item_item.xml | Fake nuclear power plant component relationships | Yes |
meeting.xml | The completed form built up progressively in Learn | Yes |
meeting_type.xml | Reference data for the "meeting" form | Yes |
office_bearer.xml | Roles within a fake community organisation | Yes |
office_bearer_office_bearer.xml | Fake community organisation structure | Yes |
project.xml | Project grid information to populate "meeting" | Yes |
project_status.xml | Reference data for the "project" form | Yes |
species_diet.xml | Links what eats who | Yes |
species_predator.xml | Links who eats what | Yes |
time_table.xml | Times of the day in half-hour increments to be used in a drop down list | Yes |
These tables are either administrative, or store information capable of being used in any forms.
Table name | Purpose |
---|---|
config | Location of imported config file contents |
dummy | The database table "used" by forms that don't write information to the database, such as Reports, Help, e.t.c. |
file | Information about uploaded files |
history | Form field change information |
url | Information about URLs attached to a form |