This section describes the properties in the configuration JSON file for an editor.
Within the
editors directory, every editor included with your Experience Manager
installation is identified by a folder with the name of the editor. For
example, the MediaEditor configuration JSON is contained in a folder named
MediaEditor:
<app-dir>/config/import/editors/MediaEditor
Properties in the JSON file:
|
Property |
Value |
Description |
|---|---|---|
|
ecr:type |
editor |
Required. |
|
config |
See examples below for sample contents. |
Optional. Configuration content for an editor. |
The following sections contain examples of some of the JSON files for editors included with the Discovery Electronics reference application.
Example 13. Sample JSON content for MediaEditor
{
"ecr:type":"editor",
"config": {
"useMediaBrowser": "false",
"mediaRoots": {
"default": "http://EXAMPLE-LAP:8006/ifcr/sites/Discover/media/",
"mediaSource": "http://EXAMPLE-LAP:8006/discover-authoring/images/"
},
"mdexPort": "17000",
"mdexHost": "EXAMPLE-LAP",
"videoFormats": "flv|f4v|3pg|mov|mp4",
"imageFormats": "jpg|jpeg|png|gif",
"mediaURI": "/ifcr/sites/Discover/media/"
}
}
Example 14. Sample JSON content for BoostBuryRecordEditor
{
"ecr:type":"editor",
"config" : {
"resourcePath": "/configuration/tools/xmgr/services/endecaBrowserService.json"
}
}
Example 15. Sample JSON content for SpotlightSelectionEditor
{
"ecr:type":"editor",
"config" : {
"resourcePath": "/configuration/tools/xmgr/services/endecaBrowserService.json"
}
}
Example 16. Sample JSON content for LinkBuilderEditor
{
"ecr:type":"editor",
"config" : {
"resourcePath": "/configuration/tools/xmgr/services/endecaBrowserService.json"
}
}
