SocialStack Cloud

2024-02-27T14:41:26Z

80.229.4.125: /* Certificates */

Entities

2024-02-05T15:38:12Z

80.229.4.125: /* Field Attributes */

An entity is an object which stores fields of information, usually in your database but can also be in memory only. Virtually everything in a SocialStack API is an entity of some form - roles, pages, menu items and so on.

The quickest way to create an entity is to generate a template of one like so:

<syntaxhighlight lang="bash">
socialstack generate Api/TodoItems
</syntaxhighlight>

Use a plural name here, otherwise you'll be asked if you wanted to make a simple service instead. This is to avoid class naming collisions, i.e. the above ultimately creates an entity class called '''Api.TodoItems.TodoItem'''.

=Fields=

Edit your entity .cs file and you'll see some sample fields. Simply adding a field will allow it to be stored in the database and it will also be editable via the admin panel and appear in your API requests including Loop. Use a C# property instead if you don't want it to be stored in the database but did want it to appear everywhere else.

=Field names=

Some field names are treated specially for convenience. This is the list of all current patterns checked for by AutoFormService.

== Refs ==

'''string {Name}Ref''' - A string field ending with '''Ref''' indicates a file. You'll get a file selector in the admin panel for these. They should be given to the getRef function at UI/Functions/GetRef to either obtain a url or display it directly.

Whilst it's always recommended to end a field with ref so it's clear what data people are working with, you can get the same file selector on a field that doesn't end in ref by setting the type to image or file:

<syntaxhighlight lang="csharp">
[Data("type", "file")]
public string MyFileSelector;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by setting the type to something else (default: text).

== Dates ==

'''DateTime {Name}, DateTime? {Name}''' - You should always postfix your date fields with '''Utc''' to make it obvious what the fields intended timezone is, however, any DateTime or DateTime? field will display a date selector. This is the same as setting the type to datetime:

<syntaxhighlight lang="csharp">
[Data("type", "datetime")]
public DateTime MyDateSelector;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by setting the type to something else (default: text).

== Booleans ==

'''bool {Name}, bool? {Name}''' - Displays a checkbox on any bool field. This is the same as setting the type to checkbox:

<syntaxhighlight lang="csharp">
[Data("type", "checkbox")]
public int ZeroOrOne;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by setting the type to something else (default: text).

== Canvas editors ==

'''string {Name}Json''' - A string field ending with '''Json''' indicates canvas JSON by default. You'll get a wysiwig editor. If you want a regular Json editor instead, use a data attribute, like this:

<syntaxhighlight lang="csharp">
[Data("contentType", "application/json")]
public string ConfigurationJson;
</syntaxhighlight>

To get a canvas editor on a field that does not end in Json, set the type to canvas:

<syntaxhighlight lang="csharp">
[Data("type", "canvas")]
public string Configuration;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by setting the type to something else (default: text).

== Colour pickers ==

'''string {Name}Color, string {Name}Colour''' - Displays a colour picker. To get a colour picker on any other field, set the type to color:

<syntaxhighlight lang="csharp">
[Data("type", "color")]
public string Background;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by setting the type to something else (default: text).

== User selectors ==

'''uint {Name}UserId''', '''int {Name}UserId''' - Displays a user selector. To display the same user selector on some other field, set the module like so:

<syntaxhighlight lang="csharp">
[Module("Admin/User/Select")]
public uint ModeratedBy;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by telling it to render with a regular UI/Input:

<syntaxhighlight lang="csharp">
[Module("UI/Input")]
public uint ModeratedByUserId;
</syntaxhighlight>

== Entity selectors ==

'''uint {EntityName}Id''' - a uint field ending with '''Id''' will be checked to see if you have an entity, i.e. any content type on your site, with the same name. If one exists, a selector for that entity will be used on the admin panel.

<syntaxhighlight lang="csharp">
public uint PageId; // Will display a dropdown of Page entries.
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by telling it to render with a regular UI/Input:

<syntaxhighlight lang="csharp">
[Module("UI/Input")]
public uint PageId;
</syntaxhighlight>

If you would like the same content selector on a field which does not match this pattern, set the module and contentType like so:

<syntaxhighlight lang="csharp">
[Module("Admin/ContentSelect")]
[Data("contentType", "page")]
public uint ParentPageId;
</syntaxhighlight>

As with all Data attributes, contentType here is just a prop of the Admin/ContentSelect component. I.e. we're telling the form system to use a specific component to render this field and giving it some additional props to use as well.

=== Search mode for large sets ===

Because this is a generic content selector component, it makes some best guesses about what field to use as the display text in the dropdown. If you have a very large amount of content, a dropdown would be inappropriate and should display a searchable set instead to avoid listing thousands of things on an awkward dropdown. It has a search mode to help with this:

<syntaxhighlight lang="csharp">
[Data("search", "title")]
public uint PageId;
</syntaxhighlight>

This search Data attribute is a prop recognised by the Admin/ContentSelect component, so you can turn it on wherever you're using that component. The attributes value is the name of the field that is used during the search - in this case, we're searching pages based on if the search term matches anything in the page title.

<syntaxhighlight lang="csharp">
[Module("Admin/ContentSelect")]
[Data("search", "title")]
[Data("contentType", "page")]
public uint ParentPageId;
</syntaxhighlight>

=Field Attributes=

SocialStack conveniences above are often all that is necessary, however, there are certainly times where it is useful to have a field display with a custom editor component, or not display at all. You can add attributes to your fields to customise the field behaviour in a variety of ways:

* [Module("Admin/ModuleName")] - This attribute tells the admin panel to render your field with the given module. The module will receive everything that UI/Input would have, so that's props like label, name and value.

* [Module(true)] - This attribute tells the admin panel to hide your field with the given module.

* [Data("propName", "propValue")] - This attribute passes additional props to the admin panel rendering of your component. Works best with custom modules, but can also be used to override certain default behaviours.

* [Localized] - Often used on names and descriptions, this attribute indicates that the field varies by locale. Works with any field type meaning it can also be used to make, for example, a price vary by locale too. When you use localized fields and there are more than one locale on your site, you'll get a dropdown on the admin panel to switch between editing different locales.

* [Meta("metaFieldName")] - Marks this field as the source of a given named [[Content Type Meta Fields|meta field]].

Entities

2024-02-05T15:22:03Z

80.229.4.125: /* Field Attributes */

An entity is an object which stores fields of information, usually in your database but can also be in memory only. Virtually everything in a SocialStack API is an entity of some form - roles, pages, menu items and so on.

The quickest way to create an entity is to generate a template of one like so:

<syntaxhighlight lang="bash">
socialstack generate Api/TodoItems
</syntaxhighlight>

Use a plural name here, otherwise you'll be asked if you wanted to make a simple service instead. This is to avoid class naming collisions, i.e. the above ultimately creates an entity class called '''Api.TodoItems.TodoItem'''.

=Fields=

Edit your entity .cs file and you'll see some sample fields. Simply adding a field will allow it to be stored in the database and it will also be editable via the admin panel and appear in your API requests including Loop. Use a C# property instead if you don't want it to be stored in the database but did want it to appear everywhere else.

=Field names=

Some field names are treated specially for convenience. This is the list of all current patterns checked for by AutoFormService.

== Refs ==

'''string {Name}Ref''' - A string field ending with '''Ref''' indicates a file. You'll get a file selector in the admin panel for these. They should be given to the getRef function at UI/Functions/GetRef to either obtain a url or display it directly.

Whilst it's always recommended to end a field with ref so it's clear what data people are working with, you can get the same file selector on a field that doesn't end in ref by setting the type to image or file:

<syntaxhighlight lang="csharp">
[Data("type", "file")]
public string MyFileSelector;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by setting the type to something else (default: text).

== Dates ==

'''DateTime {Name}, DateTime? {Name}''' - You should always postfix your date fields with '''Utc''' to make it obvious what the fields intended timezone is, however, any DateTime or DateTime? field will display a date selector. This is the same as setting the type to datetime:

<syntaxhighlight lang="csharp">
[Data("type", "datetime")]
public DateTime MyDateSelector;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by setting the type to something else (default: text).

== Booleans ==

'''bool {Name}, bool? {Name}''' - Displays a checkbox on any bool field. This is the same as setting the type to checkbox:

<syntaxhighlight lang="csharp">
[Data("type", "checkbox")]
public int ZeroOrOne;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by setting the type to something else (default: text).

== Canvas editors ==

'''string {Name}Json''' - A string field ending with '''Json''' indicates canvas JSON by default. You'll get a wysiwig editor. If you want a regular Json editor instead, use a data attribute, like this:

<syntaxhighlight lang="csharp">
[Data("contentType", "application/json")]
public string ConfigurationJson;
</syntaxhighlight>

To get a canvas editor on a field that does not end in Json, set the type to canvas:

<syntaxhighlight lang="csharp">
[Data("type", "canvas")]
public string Configuration;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by setting the type to something else (default: text).

== Colour pickers ==

'''string {Name}Color, string {Name}Colour''' - Displays a colour picker. To get a colour picker on any other field, set the type to color:

<syntaxhighlight lang="csharp">
[Data("type", "color")]
public string Background;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by setting the type to something else (default: text).

== User selectors ==

'''uint {Name}UserId''', '''int {Name}UserId''' - Displays a user selector. To display the same user selector on some other field, set the module like so:

<syntaxhighlight lang="csharp">
[Module("Admin/User/Select")]
public uint ModeratedBy;
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by telling it to render with a regular UI/Input:

<syntaxhighlight lang="csharp">
[Module("UI/Input")]
public uint ModeratedByUserId;
</syntaxhighlight>

== Entity selectors ==

'''uint {EntityName}Id''' - a uint field ending with '''Id''' will be checked to see if you have an entity, i.e. any content type on your site, with the same name. If one exists, a selector for that entity will be used on the admin panel.

<syntaxhighlight lang="csharp">
public uint PageId; // Will display a dropdown of Page entries.
</syntaxhighlight>

If you don't want this behaviour on a field that fits this pattern, override it by telling it to render with a regular UI/Input:

<syntaxhighlight lang="csharp">
[Module("UI/Input")]
public uint PageId;
</syntaxhighlight>

If you would like the same content selector on a field which does not match this pattern, set the module and contentType like so:

<syntaxhighlight lang="csharp">
[Module("Admin/ContentSelect")]
[Data("contentType", "page")]
public uint ParentPageId;
</syntaxhighlight>

As with all Data attributes, contentType here is just a prop of the Admin/ContentSelect component. I.e. we're telling the form system to use a specific component to render this field and giving it some additional props to use as well.

=== Search mode for large sets ===

Because this is a generic content selector component, it makes some best guesses about what field to use as the display text in the dropdown. If you have a very large amount of content, a dropdown would be inappropriate and should display a searchable set instead to avoid listing thousands of things on an awkward dropdown. It has a search mode to help with this:

<syntaxhighlight lang="csharp">
[Data("search", "title")]
public uint PageId;
</syntaxhighlight>

This search Data attribute is a prop recognised by the Admin/ContentSelect component, so you can turn it on wherever you're using that component. The attributes value is the name of the field that is used during the search - in this case, we're searching pages based on if the search term matches anything in the page title.

<syntaxhighlight lang="csharp">
[Module("Admin/ContentSelect")]
[Data("search", "title")]
[Data("contentType", "page")]
public uint ParentPageId;
</syntaxhighlight>

=Field Attributes=

SocialStack conveniences above are often all that is necessary, however, there are certainly times where it is useful to have a field display with a custom editor component, or not display at all. You can add attributes to your fields to customise the field behaviour in a variety of ways:

* [Module("Admin/ModuleName")] - This attribute tells the admin panel to render your field with the given module. The module will receive everything that UI/Input would have, so that's props like label, name and value.

* [Module(false)] - This attribute tells the admin panel to hide your field with the given module.

* [Data("propName", "propValue")] - This attribute passes additional props to the admin panel rendering of your component. Works best with custom modules, but can also be used to override certain default behaviours.

* [Localized] - Often used on names and descriptions, this attribute indicates that the field varies by locale. Works with any field type meaning it can also be used to make, for example, a price vary by locale too. When you use localized fields and there are more than one locale on your site, you'll get a dropdown on the admin panel to switch between editing different locales.

* [Meta("metaFieldName")] - Marks this field as the source of a given named [[Content Type Meta Fields|meta field]].

2023-12-13T16:53:31Z

80.229.4.125: Created page with "== Creating and using apple developer certificates for signing app in devops == === Get openssl === download open ssl 1.x (later versions are not compatible with mac ios see..."

== Creating and using apple developer certificates for signing app in devops ==

=== Get openssl ===

download open ssl 1.x (later versions are not compatible with mac ios see comment below)

If you are using a build system like cordova and receive an error like this one:

security: SecKeychainItemImport: MAC verification failed during PKCS12 import (wrong password?)

It's because "OpenSSL 3.x changed its default algorithm in pkcs12. Which is not compatible with embedded Security frameworks in macOS/iOS. You could alternatively use OpenSSL 1.x."

=== Create a certificate signing request (CSR) ===

<syntaxhighlight lang="bash">
openssl genpkey -algorithm RSA -out d:\4Roads_Distribution.key

openssl req -new -key d:\4Roads_Distribution.key -out d:\4Roads_Distribution.csr -subj "/emailAddress=Robert.Nash@4-roads.com, CN=4 Roads LTD, C=GB"
</syntaxhighlight>

=== References ===

https://help.adobe.com/en_US/air/build/WS5b3ccc516d4fbf351e63e3d118666ade46-7ff0.html#WSfffb011ac560372f284e44b012cd1e700c0-8000

https://gist.github.com/boodle/77436b2d9facb8e938ad

Search Elastic

2023-12-12T15:34:38Z

80.229.4.125: /* Forcing a boolean value to pass both checked and unchecked values */

The elastic search module works alongside the [[Search Crawler]] to extract pages from the site into an elastic search instance to enable site wide search

The module registers itself to listen for the search crawler events and creates locale based indexes in the elastic repo for any pages it receives

When indexing the pages, if there is a primary data type then this will also be indexed against the page in '''primaryObject''', this can then be used in query values as explained below

The indexing process is controlled by execution of the search crawler via the site automations

The module contains a Readme.txt file which gives help for the initial setup of elastic but the creation of the indexes/content are all automated.

== Installation ==

The basic setup steps are

#Install the following socialstack modules
#*Api/SearchCrawler
#*Api/SearchElastic
#*UI/SiteSearch
#Mark any pages not to be indexed
#Install Elastic Search (see '''[https://github.com/socialstack-core/modules/tree/master/Api/SearchElastic Readme.txt]''' in the repo for help and guidance)
#Configure the sizing/scale in the '''elasticsearch.yml''' file (mainly vm memory usage)
#Start Elastic Search for the first time and get the master password and certificate fingerprint
#Add the url, credentials and fingerprint values to the module configuration via the ss admin panel
#Run the automation to index the site, the indexing progress is shown via the console

The module also contains a postman collection which can be used to quick debug/verify the indexed content

Once indexed there is a UI/SiteSearch module which can be used as the basis of the site search

== Social Stack Cloud Install Steps ==

<code>wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | sudo gpg --dearmor -o /usr/share/keyrings/elasticsearch-keyring.gpg</code>

<code>sudo apt-get install apt-transport-https</code>

<code>echo "deb [signed-by=/usr/share/keyrings/elasticsearch-keyring.gpg] https://artifacts.elastic.co/packages/8.x/apt stable main" | sudo tee /etc/apt/sources.list.d/elastic-8.x.list</code>

<code>sudo apt-get update && sudo apt-get install elasticsearch</code>

Remember to get the elastic user password from the output and update the ss configuration

"The generated password for the elastic built-in superuser is : xxxxxx"

Next get the ssl certificate fingerprint value for config

<code>
cd /etc/elasticsearch/certs
openssl x509 -fingerprint -sha256 -in http_ca.crt
</code>

The section you need looks like this (the base64encoded values)
SHA256 Fingerprint=85:AA:9E:19:2F:4C:72:01:01:66:41:87:28:03:52:B7:88:61:9C:93:E8:18:D2:9C:C7:60:92:F9:E0:84:EE:AA

Now elasticsearch is installed, before starting look at the memory and diskspace section below

Finnaly you can now start the elasticsearch service by executing

<code>sudo systemctl start elasticsearch.service</code>

These commands provide no feedback as to whether Elasticsearch was started successfully or not.
Instead, this information will be written in the log files located in /var/log/elasticsearch/ or you can run the command below

<code>systemctl status elasticsearch.service</code>

To configure Elasticsearch to start automatically when the system boots up, run the following commands:

<code>
sudo /bin/systemctl daemon-reload

sudo /bin/systemctl enable elasticsearch.service
</code>

== Configuring memory and diskspace ==

It is recommended to setup the vm with at least 4gb ram, when running 2gb we have run into issues

edit the config file to set diskspace limits

edit /etc/elasticsearch/elasticsearch.yml

<code>
cluster.routing.allocation.disk.threshold_enabled: false

cluster.routing.allocation.disk.watermark.flood_stage: 250mb

cluster.routing.allocation.disk.watermark.low: 2gb

cluster.routing.allocation.disk.watermark.high: 1gb
</code>

To disable geo location, if the project is not using the geolocation extensionsit can be disabled as otherwise an additional index is created and the contents automatically downloaded

<code>
ingest.geoip.downloader.enabled: false
</code>

Set the memory usage (default 4gb) but for dev we have set it to the minimum as below

edit /etc/elasticsearch/jvm.options

Uncomment and set these values

<code>
-Xms128m

-Xmx128m
</code>

To check the heap size

<code>
sudo cat /var/log/elasticsearch/elasticsearch.log | grep "heap size"
</code>

== Admin ==

linux

<code>sudo systemctl start elasticsearch.service</code>

<code>sudo systemctl stop elasticsearch.service</code>

To get the fingerprint

<code>
cd /etc/elasticsearch/certs

openssl x509 -fingerprint -sha256 -in http_ca.crt
</code>which

To reset the user password

<code>
bin/elasticsearch-reset-password -u elastic -i
</code>

== Endpoints ==

=== GET /v1/sitesearch/reset ===

This removes any indexes from elastic to allow a clean start

=== POST /v1/sitesearch/query ===

This is the core search endpoint which currently accepts the following values

;queryString
:The query value entered by the user and/or the '''UI/SiteSearch''' and '''UI/ContentSearch''' components, elastic search uses the Lucene query language so you can build complex queries
:https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html
:e.g.
:<code>Africa AND primaryObject.name:Botswana</code>
:<code>primaryObject.price:(>=1000 AND <5000)</code>
:<code>((quick AND fox) OR (brown AND fox) OR fox) AND NOT dog</code>

;tags
: This expects a list of comma separated tags, if any are supplied the query will only return results which contain all the passed tag values

;contentTypes
: This expects a list of comma separated content types, if any are supplied the query will only return results which contain all the passed content types, these are normally the primary data object for the page

;pageSize
: This expects the page size and will default to 10 if not populated

;pageIndex
: This expects the starting page number and will default to 1

;aggregationFields
: This expects a list of comma separated field names, if any are supplied then aggregations/facets are returned for the fields, a good example of this can be be found in '''UI/ContentSearch''' component

;allFields
: If this is set to true then any indexed content will be searchable, this includes any 'include' files and metadata from the primary object, if you want to restrict the search to the managed text fields then set this to false (the default)

== Search taxonomy and filters/facets ==
You can filter or define facets(aggregations in ElasticSerach terminology) on any field exposed to Elastic from the social stack application, but they work best on metadata type fields such as tags, price etc

A basic example would be the '''tags''' field.

But a better solution is to setup contextual tags using the '''Api/Categories''' component and tags.

This allows you to give some context to a tag, so for example you could create an '''Animals''' category, then when adding a new tag for '''Cow''' or '''Horse''' you would set their category to be '''Animals'''

Any tags linked to a category can be referenced as '''taxonomy.xxxxx''' so in this example '''taxonomy.animals'''

These can then be referenced to show a contextual filter in the UI, the example below will pass back an aggregation of any '''animals''' tags in the result set, '''UI/ContentSearch''' then uses these render an auto generated filter.
e.g.

<syntaxhighlight lang="json">
{
"c": [
{
"t": "UI/ContentSearch",
"d": {
"aggregationFields": "taxonomy.animals",
"contentTypes": "ItineraryPageDataType"
}
}
]
}

</syntaxhighlight>

When tags are assigned to category and indexed, you will expose the core tag values and also some auto generated taxonomy fields.

An example of the indexed data in Elastic looks something like the example below where '''Africa''' and '''Botswana''' are plain tags but '''Horse''' has been linked to the '''Animals''' category

The '''Horse''' value is still exposed in the '''tags''' element as that is used for free text search ranking.

<syntaxhighlight lang="json">
{
"tags": [
"Africa",
"Botswana",
"Horse"
],
"taxonomy": {
"animals": [
"Horse"
]
}
}
</syntaxhighlight>

== UI Components ==
;UI/ContentSearch

This provides a good example with filtering and paging see the amba repo

The component will also allow you to override the default values/titles for any aggregation using the aggregationOverrides property, this can be useful to add grouping to values such as regions/countries etc

The buckets property is optional and by default would normally be an empty array [] but can be used to override labels and the order of options

Some basic examples of how overrides can be used to control the search filters

=== 2 Column example with set items for destination ===

<syntaxhighlight lang="json">
{
"name": "taxonomy.destination",
"label": "Destination",
"columns": 2,
"buckets": [
{
"key": "Botswana",
"label": null
},
{
"key": "Madagascar",
"label": null
},
{
"key": "Scotland",
"label": "Bonny Scotland"
},
{
"key": "Svalbard",
"label": null
}
]
}
</syntaxhighlight>

=== Swapping the default select boxes for radio buttons ===

<syntaxhighlight lang="json">
{
"name": "taxonomy.audience",
"label": "Audience",
"prompt": "",
"inputType": "radio",
"buckets": []
}
</syntaxhighlight>

=== Forcing a boolean value to show as a single checkbox ===

<syntaxhighlight lang="json">
{
"name": "primaryObject.isFeatured",
"label": "Only show featured events",
"prompt": "",
"inputType": "checkbox",
"isBoolean": true,
"buckets": []
}
</syntaxhighlight>

=== Forcing a boolean value to return both checked and unchecked values ===

<syntaxhighlight lang="json">
{
"name": "primaryObject.isCompleted",
"label": "Show completed events",
"prompt": "",
"inputType": "checkbox",
"isBoolean": true,
"returnAllValues": true,
"buckets": []
}
</syntaxhighlight>

=== Forcing a simple select dropdown ===

<syntaxhighlight lang="json">
{
"name": "primaryObject.country",
"label": "Location",
"all": "Any location",
"prompt": "",
"inputType": "select",
"allowAllOptions": true,
"buckets": []
}
</syntaxhighlight>

=== Allow multiple unrelated values to be chosen ===

Override the default functionality which disables any original filter options if the search results no longer contain results containing the values, so a drill down work flow
dog -> spaniel -> english

With 'allowAllOptions' other unrelated documents can be brought into the results so for example when filtering events you could include multiple unrelated types such as "gala" OR "conference" when by default if you choose "gala", conferences would be disabled

<syntaxhighlight lang="json">
{
"name": "taxonomy.event type",
"label": "Event Type",
"prompt": "",
"inputType": "checkbox",
"allowAllOptions": true,
"buckets": []
}
</syntaxhighlight>

A complete example is shown below using separate components for the filters and results (2 column layout)

<syntaxhighlight lang="json">
{
"c": [
{
"t": "UI/ContentSearch/SearchContext",
"d": {
"comment": "SearchContext used to link search engine, results and filters"
},
"c": {

"t": "UI/SiteContainer",
"d": {},
"c": {
"t": "UI/SiteRow",
"d": {},
"c": [
{
"t": "UI/SiteColumn",
"d": {
"width": "sidebar"
},
"c": {
"t": "UI/ContentSearch",
"d": {
"title": "Search insights",
"aggregationFields": "taxonomy.brand,taxonomy.audience,taxonomy.insight category,tags",
"contentTypes": "Insight",
"resultLayout": "list",
"itemRenderer": "UI/InsightResultItem",
"sortOptions": [
{
"name": "Ranking",
"field": "_score",
"order": "desc"
},
{
"name": "Name (asc)",
"field": "title.keyword",
"order": "asc"
},
{
"name": "Name (desc)",
"field": "title.keyword",
"order": "desc"
},
{
"name": "Date (asc)",
"field": "primaryObject.editedUtc",
"order": "asc"
},
{
"name": "Date (desc)",
"field": "primaryObject.editedUtc",
"order": "desc"
}
],
"aggregationOverrides": [
{
"name": "taxonomy.brand",
"label": "View insights by brand",
"all": "Both",
"prompt": "",
"inputType": "radio",
"allowAllOptions": true,
"isExpanded": true,
"buckets": []
},
{
"name": "taxonomy.audience",
"label": "Audience",
"all": "Any audience type",
"prompt": "",
"inputType": "radio",
"allowAllOptions": true,
"isExpanded": true,
"buckets": []
},
{
"name": "taxonomy.insight category",
"label": "View by insight category",
"all": "Any category",
"prompt": "",
"inputType": "checkbox",
"allowAllOptions": true,
"isExpanded": true,
"buckets": []
},
{
"name": "tags",
"label": "Topics",
"all": "Any topics",
"prompt": "",
"inputType": "select",
"allowAllOptions": true,
"buckets": []
}
],
"hideResults": true,
"hideTitle": true,
"pageSize": "4"
},
"i": 4
},
"i": 6
},
{
"t": "UI/SiteColumn",
"d": {
"width": "content"
},
"c": [
{
"t": "UI/ContentSearch/ContentSearchResults",
"d": {
"hideTotal": true,
"searchType": "insights",
"pageSize": "4"
},
"i": 14
}
],
"i": 11
}
],
"i": 12
},
"i": 13
}
}
],
"i": 3
}

</syntaxhighlight>