Conventions Install Learn Advanced Alphabetical
Fake FAQ TODO File List

pabulumba

The manual

Core configuration files

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 namePurposeForm
action.xmlTypes of action performed by usersYes
custom_report.xmlAny ad hoc reportsYes
database.phpConnection details for the MySQL databaseNo
email_template.xmlAny templates used when sending automated emailsYes
file_extension.xmlAllowable extensions when files are uploadedYes
help.xmlEntire contents of the help fileNo
language.xmlLanguages supported by pabulumbaYes
log.xmlUsers actions are recorded in the log and accessed via this fileYes
main.xmlEntry point on logging in - the Main pageNo
maintenance.xmlWhere links to all configuration files should be locatedNo
menu.xmlCommon location for the links (buttons) across the top of the pagesNo
message.xmlFeedback, error, and validation messages in all supported languagesYes
pabulumba.xslMain XSL fileNo
personal_details.xmlDifferent "view" of the user file to allow limited access to a user's own recordsYes
reports.xmlPreferred location of listing of all standard, custom, and special reportsNo
role.xmlSystem roles within pabulumbaYes
rule.xmlDefinition of rules, if usedYes
rule_role.xmlLinks rules and roles for flexibility if rules are usedYes
search.xmlTemplate for searching in pabulumbaYes
setting.xmlEvery single system-wide setting; treat with cautionYes
user.xmlDetails of system users, including credentialsYes

Demonstration configuration files

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 namePurposeForm
animal_class.xmlClasses of animalsYes
animal_diet.xmlWhat animals eatYes
animal_habitat.xmlWhere animals liveYes
animal_predator.xmlWhat eats animalsYes
attendee.xmlPeople's namesYes
car.xmlToy car partsYes
car_car.xmlToy car part relationshipsYes
demo.xmlPage listing all the demonstration forms and reportsYes
demo_reference_1.xmlAustralian statesYes
demo_reference_2.xmlAustralian (?) birdsYes
demonstration.xmlForm showing all functionality of pabulumba on a single formYes
grid_data.xmlRepresents a two-dimensional structure on the demonstration formYes
item.xmlFake nuclear power plant componentsYes
item_item.xmlFake nuclear power plant component relationshipsYes
meeting.xmlThe completed form built up progressively in LearnYes
meeting_type.xmlReference data for the "meeting" formYes
office_bearer.xmlRoles within a fake community organisationYes
office_bearer_office_bearer.xmlFake community organisation structureYes
project.xmlProject grid information to populate "meeting"Yes
project_status.xmlReference data for the "project" formYes
species_diet.xmlLinks what eats whoYes
species_predator.xmlLinks who eats whatYes
time_table.xmlTimes of the day in half-hour increments to be used in a drop down listYes

Database tables with no configuration files

These tables are either administrative, or store information capable of being used in any forms.

Table namePurpose
configLocation of imported config file contents
dummyThe database table "used" by forms that don't write information to the database, such as Reports, Help, e.t.c.
fileInformation about uploaded files
historyForm field change information
urlInformation about URLs attached to a form