Backend interface settings

IMPORTANT: This configuration page replaces the config.json file that was used prior to Sitefinity 14.3. In case you upgrade from a prior version, all supported configurations are automatically migrated to this configuration page and the file is no longer considered. .

• Content items per page: Specify the number of items displayed in the page for content items when in List view. The default value is 20, you can show a maximum of 50 and a minimum of 1 item per page. Additional items are displayed with Load more items button.
  
• Media items per page: Specify the number of items displayed in the page for media items when in List view. The default value is 50, you can show a maximum of 50 and a minimum of 1 item per page. Additional items are displayed with Load more items button.
• Display hidden columns: Define hidden columns to be displayed in the list for each content type. You can display Authоr column for each content type, and DateCreated and LastModified for parent types in hierarchical modules.
  For example, if you have a parent content type newsitems , it has the Author column hidden by default. To show it add this value to the Display hidden columns field::

  {   "newsitems": [    "Author"   ]}.

  With the above configuration the column Author is displayed in the page. 

• Child types order: This configuration allows reordering of the child types in the Contains column of hierarchical types with two or more children. 
  
  To order them:
  
  1. Add a parent content type
     
  2. Add a child content type next to the parent
     The child items are ordered according to the order of selection and their module is also displayed.
     

     NOTE: If there are child items that are not selected here, they are ordered randomly in the page.

• Minimum items to display sections menu: By default, the sections menu in the item edit screen is visible only when there are 5 or more field sections. You can control this behavior by changing the number of sections needed for the menu to be visible. 

• Date and time format for fields: Configure the date and time format to use the browser locale or a custom format.
  
  By default, the date and time formats used by the date and time fields, for example the start and end dates of the event content items, are in the format h:mm a for the time component and M/d/yyyy for the date component.
  To use the browser locale:
  
  1. Select Yes under use browser locale.
     
  2. Select the format width, which can be short or long.
     
     
     

EXAMPLE: Example behavior of useBrowserLocale if the browser's language is English (US). 

 

If the browserLocaleFormatWidth is set to long the formats used in the date and time field will be h:mm:ss a and MMMM d, y, which looks like 9:22:13 am and July 10, 2023. 
If the browserLocaleFormatWidth is set to short the formats used in the date and time field are h:mm a and M/d/yy, which looks like 9:22 am and 7/10/2023. 

• Default toolset: The default kendo editor json configuration for every item that does not have a custom configuration.
  The default value is:
  
  If you make changes to the default toolset, these changes are now part of the default toolset everywhere it used. To restore the original default values, you can use the Restore to default button.
  To preview your changes in the rich-text editor, click the Preview button.
  
  
• Custom toolsets: Define a custom toolset for the kendo editor json configuration.
  Click the add  button.
  
  1. Enter a name 
     
  2. Click the edit  button
     
  3. A configuration window appears where you can add custom configurations.
     To preview your changes in the rich-text editor, click the Preview button.
     
  4. Click save.
     
  5. Select the content types that this custom configuration applies to.
     
     
     
• Link styles: Add a name and comma-separated values to specify styles for displaying links in your text. The link styles are available in the rich-text editor and the values are applied as classes in the HTML. For example you can define a style to display a link as button. 

  That means that there are three predefined types of styles called Primary button, Secondary button, and Success button. These appear in the dropdown in the rich text editor when a link is clicked and then the icon drop is clicked. Selecting one of them will apply the values in the Value collection as a class html attribute values. This means that any CSS file that is loaded both on the front end and back end of the application and that has rules for these classes applies the styling for them. This example contains the bootstrap buttons classes so for them to be visually correct, the bootstrap CSS has to be loaded in the rich text editor only because for the front end of the application it is there by default. 

  If your project is based on Bootstrap 5 or Minimal resource packages, you can take advantage of the provided npm script for compiling SASS file to one minified CSS file. 
  
  Perform the following:  

  1. Use @import to include all needed SASS files into editor.scss that is located in ~\ResourcePackages\Bootstrap5\assets\src\project\sass\adminapp 
     In our case, we import the main.scss file that is located in the previous folder (this will include the bootstrap css). To do this, simply type @import “../main.scss” and save the file. 
     
     

  2. Navigate to the ~\ResourcePackages\Bootstrap5 folder open a terminal with administrator rights.

  3. Type npm install - so that you can install the node_modules 
     

  4. Type npm run sass:editor 
     This task will generate editor.min.css file that you can find in folder ~\ResourcePackages\Bootstrap5\assets\dist\css\ 
     
     Include the editor.min.css file in the configuration for the rich text editor by adding it to the Toolset json object: 

Search in fields Select additional text fields that are included in searches.

1. Under Content type, click Add .
2. Select a content type from the list.
   
3. Under Fields, click Add .
   
4. Select the fields that you want to add. The fields are specific to the content type selected in step 2.