channel export - use a selected list of functional data categories to export; this allows one to export single data sets instead of always exporting everything we know about
This commit is contained in:
10
doc/hook/get_default_export_sections
Normal file
10
doc/hook/get_default_export_sections
Normal file
@@ -0,0 +1,10 @@
|
||||
[h3]get_default_export_sections[/h3]
|
||||
|
||||
The get_default_export_sections call returns the basic functional groups of data to export using channel_export_basic().
|
||||
|
||||
The hook is passed an array
|
||||
[
|
||||
'sections' => [ 'channel', 'connections', 'config', 'apps', 'chatrooms', 'events', 'webpages', 'mail', 'wikis' ]
|
||||
]
|
||||
|
||||
If you desire the export to contain three months of items, add 'items' to the 'sections' array
|
@@ -1 +1,10 @@
|
||||
[h2]identity_basic_export[/h2]
|
||||
|
||||
Called when exporting data for a channel
|
||||
Passed array contains
|
||||
|
||||
[
|
||||
'channel_id' => channel_id being exported
|
||||
'sections' => array of functional export sections which are being exported
|
||||
'data' => the export data array which has been generated
|
||||
]
|
||||
|
Reference in New Issue
Block a user