Project

General

Profile

Wiki ยป

Data Storage

Creative Commons Configurator uses the WordPress API to store its data.

Options

All Creative Commons Configurator settings are stored in a single array, which is stored as the cc_settings option. To programmatically retrieve the Creative Commons Configurator settings array, please use the following code:

$bccl_stored_options = get_option('cc_settings');

Custom Fields

Creative Commons Configurator uses the following internal Custom Fields to store data related to the content:

  1. _bccl_license - Contains the license slug (see the bccl-licenses.php file for the available license slugs. The currently supported values are: manual, arr, cc__by, cc__by-nd, cc__by-sa, cc__by-nc, cc__by-nc-nd, cc__by-nc-sa, cc0. Please note that the _bccl_license custom field is set only if its value is different than the slug of the default license, as it has been set in the plugin settings (Settings->License). Also, please note that the current implementation may, under very specific circumstances, lead to some problems if the default license changes, but in most cases it should be fine. We are evaluating the underlying mechanism and intend to improve it in future releases.
  2. _bccl_perm_url - The URL to a page containing custom license permissions.
  3. _bccl_perm_title - The title of the page containing custom license permissions.
  4. _bccl_forced_creator_url - The enforced URL to a web page about the author.
  5. _bccl_forced_creator_name - The enforced name of the author.

Data clean up after uninstall

Creative Commons Configurator contains an uninstall script which cleans the plugin settings from the database when the plugin is deleted via the WordPress administration interface. This clean up process does not take place if the plugin is remove by other means.

The extra data, which might have been entered by the user in the License box in the post editing screen and has been stored in Custom Fields, is not cleaned automatically by the uninstall script. This is by design so as to prevent users from losing all their custom data.