Home
FieldFrame is Brandon Kelly’s framework for rapid development of fieldtype extensions in ExpressionEngine.
In order to get FieldFrame up-and-running, you will need:
- PHP 5 or later
- ExpressionEngine 1.4.2 or later
Hit the ground running with FieldFrame using these guides:
- Getting Started — covers installation and fieldtype management
FieldFrame comes bundled with a few simple fieldtypes:
View a complete list of available fieldtype extensions in the Fieldtype Catalog.
Writing your own fieldtype extension? Here are some resources that should help you along the way:
- Anatomy of a Fieldtype — Choose a class name and create the skeleton for your fieldtype
- A Simple Fieldtype — Take a look at how easy writing a fieldtype extension can be
- Functions Reference — Detailed rundown of the functions FieldFrame can call in your fieldtype extension
- Defining Your Fieldtype’s Requirements — What to do if your fieldtype is a needy bitch
- Default Settings and Tag Params — Get rid of those isset’s and get on with your life
- Built-in Convenience Functions — Functions your fieldtype comes with by extending Fieldframe_Fieldtype
- SettingsDisplay Class — Introduction to the SettingsDisplay class, and a detailed rundown of its functions
- Extension Hooks — How to tap into ExpressionEngine hooks from your fieldtype extension
- Postponed Saving — Get the entry’s ID from save_field
- Custom Tag Functions — Present your field’s data in multiple ways on the template side
Having trouble with FieldFrame? Or have an idea that could make it even better? All FieldFrame support is being handled through Get Satisfaction.
FieldFrame is, and always will be, a free extension. But if you feel compelled, I’m certainly not going to stop you from sending a little beer money my way!
1.0.3
- fixed conditional tag bugs
- fixed undefined offset bug
1.0.2
- fixed json_encode bug affecting < PHP 5.2
- FieldFrame now respects “Automatically Convert High ASCII Text to Entities” global weblog setting
-
FF Matrix’s
{count}template variable has been renamed to{row_count} - other bug fixes
1.0.0
- we’re golden!
- added a link to the Fieldtypes Manager in Admin > Utilities
- added a script that will convert LG Data Matrix fields to FF Matrix (accessible from FF Matrix’s site settings in the Fieldtypes Manager)
- removed FF Checkbox Group’s site settings
- added a single template tag option to FF Checkbox Group and FF Multi-select which returns an unordered list.
- FF Matrix now has two single variable tags: “count” and “total_rows”
- bug fixes and cleanup
0.9.9
- FF Matrix will now ignore rows that have no data
-
FF Matrix template tags now accept two additional parameters,
sortandlimit - bug fixes
0.9.8
- fixed a bug where only the first cell setting would be saved
- fieldtype site settings are now accessible immediately after being enabled
0.9.7
- fixed the “white screen of death” bug
- fieldtype site settings now match the FF Matrix field settings
0.9.6
- bundled FF Multi-select
- added Date and Select celltypes
- added Max Length setting to the Text celltype
- added Textarea Rows setting to the Textarea celltype
- added a single template tag option to FF Matrix which returns an HTML table
- fixed a bug that prevented creating new FF Matrix rows with two columns using the same celltype
0.9.5
- bundled FF Matrix
- added Built-in Convenience Functions to fieldtypes
- FieldFrame now passes $field_data to save_field as the first argument rather than $field_name
0.9.3
- each fieldtype gets a hidden “field_ft” input placed before its display_field() HTML
- bug fixes
0.9.2
- added Default Settings and Tag Params functionality
- added fieldtype requirements functionality (see Defining Your Fieldtype’s Requirements)
- FieldFrame now passes $field_settings to save_field
0.9.1
- bundled FF Radio Group fieldtype
- added formatting_available and direction_available flags to display_field_settings
