Table des matières
Injecting the Initial Categories
Full LDAP Synchronisation for ENTs
This feature lets the ENT installer build course categories (and make sure they still exist) that must be present on the platform to serve the pedagogical model or certain plugins that rely on it.
In the latter case, the settings of the plugins that will use these categories can be filled in automatically.
Categories can be initialised at several levels of the tree, if their name contains the full path of names with all the parents.
General construction
The general format must be a JSON structure that maps the plugin key (use of the category) to a category descriptor:
{
<pluginkey>:<categorydescriptor>,
...
<pluginkey>:<categorydescriptor>
}
pluginkey
pluginkey ::= <pluginname>\/<pluginconfigfield>
Categories that will not be attached to a particular plugin configuration can be mapped to pseudo attributes of the local_ent_installer component whose name begins with foo_.
In the other cases, the ID of the created category will be placed in the configuration field indicated for the corresponding plugin.
JSON code example
{"local_ent_installer\/foo_admin_cat":{"name":"Administration moodle","idnumber":"ADMIN"},
"local_ent_installer\/foo_archive_cat":{"name":"Corbeille","visible":false,"idnumber":"ARCHIVE"},
"local_ent_installer\/foo_shared_area":{"name":"Cours mutualis\u00e9s","idnumber":""},
"local_ent_installer\/foo_shared_templates":{"name":"Cours mutualis\u00e9s\/Exemples de cours","idnumber":"SAMPLES"},
"local_ent_installer\/foo_shared_courses":{"name":"Cours mutualis\u00e9s\/Cours disponibles","idnumber":"SHARED"},
"local_ent_installer\/foo_shared_workplaces":{"name":"Espaces inter-\u00e9tablissement","idnumber":"WORKPLACES"},
"local_coursetemplates\/templatescategory":{"name":"Gabarits","idnumber":"TEMPLATES"},
"block_publishflow\/deploycategory":{"name":"Arriv\u00e9es","idnumber":"ARRIVALS"}
Back to the technical guide index - Back to the component index - Back to the plugin index