This topic is intended for administrators and developers with administration access rights in Episerver.
In admin view, under Config > Tool Settings you can perform miscellaneous functions for the integration and configuration of Episerver CMS.
Many functions in Episerver CMS are created as plug-ins, which you can manage from the Plug-in Manager. You can activate and deactivate selected parts. If your organization invested in additional plug-ins, you can find them in the Plug-in Manager also. After choosing a plug-in, choose which parts of it are accessible in the Overview tab.
By default, all changes to pages, files and directories are logged in the Change Log system. You can filter the information in the Change Log, making it easier to find relevant information.
- In admin view, select Config tab > Tool Settings > Change Log.
- Select a state:
- Enabled. The Change Log starts automatically when the site starts and is available for read and write operations.
- Disabled. The Change Log does not start when the site starts. Items written to the Change Log are ignored, but items may still be read from the Change Log.
- Auto. The Change Log starts as soon as any dependencies (such as a Mirroring Job) are registered against it. If no dependencies exist, the system does not start. If already running, it stops.
- On the View tab, filter and view change log items by entering one or several of the following values:
- Page to run a query on pages only.
- File to run a query on files only.
- Directory to run a query on pages directories only.
- Check in
- Delete language
- Delete children
- Click Read to run the query. A list of matching change log items appear.
|Change date from||The query is run from the change log from this date.|
|Change date to||The query is run from the change log to this date.|
From the Category drop-down list, select:
You can filter the following actions in the Change Log:
|Changed by||To filter for a specific user, enter the Episerver CMS user name.|
|Maximum number of items per page||Limits the displayed number of items. Click the next and previous arrows to browse through the list of items.|
|Start with sequence number||Enter a specific sequence number to start listing the items in the change log.|
|Read direction||List change log items in either ascending or descending order.|
To remove all Change Log items that are more than one month old and without dependencies, use the Change log auto truncate scheduled job.
Website developers can customize and extend the Change Log. Consult your website developer for assistance.
Rebuild Name for Web Addresses changes addresses in the address field. When a visitor views a page on a website based on Episerver CMS, a path to the page appears in the address field. The address reflects the page's place in the website structure.
The names in the address field are created automatically from the name an editor specified for the page. If an editor changes the page name, the name in the address field does not change. You can manually change name in the address field by changing the Name in URL field on the Settings tab in edit view.
Some pages have no value in the field for names in web addresses, such as pages imported from other Episerver solutions. The Rebuild Name for Web Addresses function lets you create all web addresses for the website at the same time. You also can overwrite all existing addresses with new ones.
The Rebuild Name for Web Addresses function can affect links to the website. All internal links are updated automatically. However, if other websites link to a certain page, that link may be broken. The function also can affect visitors' browser favorites (bookmarks).
- On the Config tab, select Rebuild Name for Web Addresses.
- Select Rebuild all page names in web addresses (overwriting existing links).
- Click Rebuild Links.
Mirroring duplicates content between websites. Episerver CMS can mirror selected parts or an entire website, and can run automatically or manually. This is useful if you wish to create sections in a test environment then publish all information at once to the public section.
Mirroring jobs are executed at time intervals that you set, as described in Scheduled jobs.
To enable mirroring, a mirroring application must be installed and running. The application handles data transfer between websites and is run separately to the Episerver CMS source and target sites. You can configure source and target websites to use separate mirroring applications. You also can install and configure a single mirroring application. See Episerver World for information about configuring and working with mirroring.
To set up mirroring between two websites, create channels in the admin view. Channels define the mirroring jobs from one Episerver CMS to another, or even to an external recipient.
Go to the source site in admin view > Configtab > Tool Settings > Mirroring to create a channel for mirroring as follows:
Click Create and enter the following information:
Setting Description Name Type an unique name for the mirroring channel. Parameters
Optional field that can be used by providers. In this version, there is one parameter which can be handled by the provider:
The TransferAction has two options None and ForceCurrentVersion. By default, the value is None, which creates a new version for each published page on the target site. The ForceCurrentVersion option does not create a new version for each published page. Instead, it updates the page on the target site.
Use default URI Select to use the URI defined in the configuration file (web.config) for the mirroring application. When you select this option, the URI field is disabled. URI
Enter the URI to the destination mirroring application's target service, for example:
The service for the default provider is:
Start page Select the local root page on the source site to be mirrored. Root page on destination Select the page number on the target site where the pages are mirrored to. Include start page Sets whether the start page is mirrored or if only its children are mirrored. Import as anonymous user Sets whether an anonymous user does the export and import of pages and files when the mirroring job is run. Import content as user Sets whether an identified user does the export and import of pages and files when the mirroring job is run. Enable reporting Select to enable reporting for the mirroring job through email. When you select this option, the E-mail address field becomes editable. E-mail address Enter the email address where the mirroring job report is sent. Continue on Error Select to enable a mirroring job to continue even there is problem on the importing side. If this option is not selected, a mirroring job terminates as soon as an error occurs. Enabled Select to enable the channel as active. If this option is not selected, nothing is mirrored for the channel. Enable validation Select to enable validation before items are mirrored. The mirroring job validates that all page types for pages being mirrored are present in the target site and that the page type has the same number and type of page properties as the source site. By default the mirroring job checks all necessary page types and page definitions, which is included in the start page and its descendants.
- Click Save.
- Continue with any of the following options:
|Reset Channel||Select to mirror everything again from the root page of the mirroring channel to the source site next time it is run. To reset the channel, select the name of the mirroring channel and click Continue with Reset.|
|Check System||To validate the created channel, click Check System. The result appears under the Messages tab. It checks both the source and target site to see if all necessary parameters are set up correctly; such as URI, Root page at destination, Mirroring Server binding, and Access to DataBase. See the section about synchronizing mirroring in the Developer Guide under Deployment > Mirroring > Installing and Configuring mirroring.|
|Messages||The result of a check system appears in the Messages tab. Click the arrow to view the result and other information regarding previous mirroring jobs that were run.|
|Monitoring||The status of a mirroring job appears in the Monitoring tab.|
|Target Site Configuration||To use a site as a mirroring target, some configuration is required.|
|Mirror Pages to a Target Site||Create a target page in the editorial interface on the target site and create a page that acts as the root page for the mirrored pages. You also can use an existing page as the mirroring root page. To publish pages, the mirroring application needs to be installed and configuration needs to be implemented.|
|Mirroring in Other Formats||Partners and customers can create mirroring in formats other than Episerver CMS Import/Export format and plug them in using the provider model.|
You can configure different search providers depending on the type of content on your website. A search provider searches across the website for pages, blocks, files, categories, forums or page types, or products on an e-commerce website. Search results are available when searching in the global Episerver menu in edit view.
Enabling search providers
You can decide which search providers you want to enable, and the order in which they appear in the search hit list. To access these settings, go to the admin view and select Config > Search Configuration.
- Blocks. Allows for search in blocks.
- Files. Allows for search in files.
- Pages. Allows for search in pages.
- Jump to. Makes it possible to jump directly from the search hit list to menu alternatives matching your search criteria.
- Products. Allows for search in products if you have Episerver Commerce installed.
- Find files, blocks and pages if you have Episerver Find installed.
You can drag and drop the search provider options to change the order between them. This controls the order in which the results are displayed in the hit list. Clearing a check box disables this search provider option.