The Optional Features panel at the site level includes six optional site-specific features. Dependency Manager and Binary Management must first be enabled at the account level to be available for a specific site.
Find and Replace
Select the checkbox to enable the global Find and Replace for Level 10 administrators. When enabled, this is shown in Content > Find and Replace. When enabled, Find and Replace provides the functionality to search content and code within the site and replace it with new values.
For more information, visit the Find and Replace page.
Select the checkbox to enable quick search for the site. Selecting Build Index creates the index of the entire site that is used in both Quick and Advanced Search. Once an initial index has been built, it will be updated automatically when changes are made. If the index has been built manually, the date of the last indexing will be displayed.
For more information, visit the Advanced Search page.
Select the checkbox to enable Dependency Manager, which governs the automated use of links and linking when files are moved or renamed. Dependency Manager must be enabled in the account settings before it can be enabled for a particular site.
For more information, visit the Dependency Manager page for the account level.
Select the checkbox to enable Binary Management, which allows for binary files such as images to be managed on the staging server in a fashion similar to managing file linking with Dependency Manager.
After Binary Management is enabled for the account, it can then be enabled on a per site basis. In other words, it is possible to have Binary Management on for some sites and not for others. Keep in mind that while Binary Management may be used without Dependency Manager, it is recommended that Dependency Manager be enabled so that Dependency tags can be utilized to track file linking. This requires that each site be rescanned in order for all current paths to be updated. Any binaries currently on the production server that should be managed by Binary Manager should be moved to the staging server prior to running the scans.
For more information, visit the Binary Management page for the account level.
Select the checkbox to allow WebDAV to be enabled for specific Level 9 and Level 10 administrators.
For more information, visit the WebDAV page.
OU Insights is an optional module that can be purchased by an institution. When purchased, the feature becomes available for use by clicking the checkbox next to Insights, and administrators may begin to modify the module's settings by clicking the Configure button.
The Insights Configuration modal contains the settings for Insights. Administrators can control the frequency at which Insights scans the site using the Report Frequency and Run Every fields. Changing the Access Group will determine which users will be able to access Insights from the Reports menu (level 9 and 10 administrators are the exception; they can always access Insights). The members of the Access Group will receive emails when Insights completes a scan of the site (or when a scheduled scan fails).
Finally, administrators can determine the default value for an index page using the Directory Index field. With Directory Index, administrators can tell Insights what to add to a URL that ends with a /, such as http://gallena.edu/academics/. When browsers request these links, the server will return a page based on its configuration (e.g., http://gallena.edu/academics/index.html). Users need to tell Insights how the server interprets webpages so it can properly scan those pages.
Common directory index values are index.html, index.php, or default.aspx. Because server configurations allow for multiple directory index values, Insights allows administrators to set a priority for those values by adding comma-separated values in the Directory Index field, which Insights will attempt to find in the order they are written.
As an example, if a server is configured to display index.html first and index.php second, but in a certain directory index.html does not exist, the server will search for index.html first, and finding none, return the content at index.php. In this situation, if Insights has index.html,index.php written in the Directory Index field, Insights will first search for files ending in index.html, and if it does not find index.html in a given directory, it will then search for index.php.
For more information about Insights, visit the OU Insights page.