|
| __construct ($name, $filename, $task=null) |
| Constructor - instantiates one object of this class.
|
|
| destroy () |
| Destroy all circular references. More...
|
|
| execute () |
| This function will perform all the actions necessary to achieve the execution of the plan/part/task.
|
|
| get_name () |
|
| get_task () |
| As far as backup structure steps are implementing backup_plugin stuff, they need to have the parent task available for wrapping purposes (get course/context....)
|
|
| log ($message, $level, $a=null, $depth=null, $display=false) |
| This function will be responsible for handling the params, and to call to the corresponding logger->process() once all modifications in params have been performed.
|
|
| set_task ($task) |
|
|
| add_plugin_structure ($plugintype, $element, $multiple) |
| Add plugin structure to any element in the structure backup tree. More...
|
|
| add_subplugin_structure ($subplugintype, $element, $multiple, $plugintype=null, $pluginname=null) |
| Add subplugin structure for a given plugin to any element in the structure backup tree. More...
|
|
| define_structure () |
| Define the structure to be processed by this backup step. More...
|
|
| execute_condition () |
| To conditionally decide if one step will be executed or no. More...
|
|
| get_backupid () |
|
| get_basepath () |
|
| get_courseid () |
|
| get_logger () |
|
| get_setting ($name) |
|
| get_setting_value ($name) |
|
| get_settings () |
| Protected API starts here.
|
|
| setting_exists ($name) |
|
Abstract class defining the needed stuff to backup one @backup_structure.
TODO: Finish phpdocs
backup_structure_step::add_subplugin_structure |
( |
|
$subplugintype, |
|
|
|
$element, |
|
|
|
$multiple, |
|
|
|
$plugintype = null , |
|
|
|
$pluginname = null |
|
) |
| |
|
protected |
Add subplugin structure for a given plugin to any element in the structure backup tree.
This method allows the injection of subplugins (of a specified plugin) data to any element in any backup structure.
NOTE: Initially subplugins were only available for activities (mod), so only the backup_activity_structure_step class had support for them, always looking for /mod/modulenanme subplugins. This new method is a generalization of the existing one for activities, supporting all subplugins injecting information everywhere.
- Parameters
-
string | $subplugintype | type of subplugin as defined in plugin's db/subplugins.json. |
backup_nested_element | $element | element in the backup tree (anywhere) that we are going to add subplugin information to. |
bool | $multiple | to define if multiple subplugins can produce information for each instance of $element (true) or no (false). |
string | $plugintype | type of the plugin. |
string | $pluginname | name of the plugin. |
- Return values
-