Required functions: Save
When using the standard LEAP™ 5 "Save / Cancel" button pickups, all information in the plugin's admin form will be passed through to the save handler.
There are several ways to process & store this information, a few of these options are outlined below:
1. LEAP_ManageFeatures
LEAP™ 5 has a flexible data map that is specific to the content plugin instance. Using LEAP_manageFeatures is appropriate for configuration data and low-volume content data, but not for larger volume text objects.
LEAP_ManageFeatures can be used either in conjunction with other storage methods or in isolation.
This method is described in detail here.
2. Master_Content & LEAP_MasterContent
LEAP™ uses a generic Master_Content table that can be addresses either through direct SQL inlines or through the LEAP_MasterContent data type.
While direct access via SQL is possible, the preferred method is via LEAP_MasterContent and is described in detail here.