Bug #3932
closed
Implement API for display and storage of privacy
Description
Add triggers that let other plugins add privacy and store privacy in the same way fields, tabs, and profile do. Usage would basically be the same as CB Captcha by calling its trigger and entire display is handled by trigger.
Updated by krileon almost 12 years ago
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Implemented triggers throughout CB Privacy to extend the privacy selector and its validation function. Also triggers for storage, delete, etc.. of privacy rows.
The API trigger privacy_getPrivacy returns privacy row or rows without having to use the data layer api directly and running the risk of class fatal errors if CB Privacy isn't loaded for whatever reason. This calls cbprivacyData::getPrivacy directly.
The API trigger privacy_getPrivacySelector will call getPrivacySelector and return its result for rendering a privacy selector.
The API trigger privacy_validatePrivacyStore will call validatePrivacyStore and validate the POST or raw value of the privacy selector for proper storage.