API Documentation
Interfaces, Classes and Traits
- Footnotes_Activator
- Fired during plugin activation.
- Footnotes_Deactivator
- Fired during plugin deactivation.
- Footnotes
- The core plugin class.
- Footnotes_Admin
- The admin-specific functionality of the plugin.
- Footnotes_WYSIWYG
- Handles the WSYIWYG-Buttons.
- Footnotes_Layout_Engine
- Layout Engine for the administration dashboard.
- Footnotes_Layout_Init
- Handles the Settings interface of the Plugin.
- Footnotes_Layout_Settings
- Displays and handles all Settings of the Plugin.
- Footnotes_Config
- Contains all Plugin Constants. Contains no Method or Property.
- Footnotes_Convert
- Converts data types and Footnotes specific values.
- Footnotes_i18n
- Define the internationalization functionality.
- Footnotes_Loader
- Register all actions and filters for the plugin.
- Footnotes_Settings
- Loads the settings values, sets to default values if undefined.
- Footnotes_Template
- Handles each Template file for the Plugin Frontend (e.g. Settings Dashboard, Public pages, ...).
- Footnotes_Public
- The public-facing functionality of the plugin.
- Footnotes_Task
- Searches and replaces the footnotes and generates the reference container.
- Footnotes_Widget_Base
- Base Class for all Plugin Widgets. Registers each Widget to WordPress.
- Footnotes_Widget_Reference_Container
- Registers a Widget to put the Reference Container to the widget area.
Table of Contents
- activate_footnotes() : mixed
- The code that runs during plugin activation.
- deactivate_plugin_name() : mixed
- The code that runs during plugin deactivation.
- run_footnotes() : mixed
- Begins execution of the plugin.
Functions
activate_footnotes()
The code that runs during plugin activation.
activate_footnotes() : mixed
This action is documented in includes/class-plugin-name-activator.php
deactivate_plugin_name()
The code that runs during plugin deactivation.
deactivate_plugin_name() : mixed
This action is documented in includes/class-plugin-name-deactivator.php
run_footnotes()
Begins execution of the plugin.
run_footnotes() : mixed
Since everything within the plugin is registered via hooks, then kicking off the plugin from this point in the file does not affect the page life cycle.