These fields configure the basic global behavior of RiSE Content. The default text in several of these setup fields includes text enclosed in brackets, such as [WebsiteName], [PageLinkURL], and so on. These are system variables that are replaced dynamically with context-specific information. You can remove them entirely if you do not want to use them, but you must not change them in any way if you plan to use them, or you will see unexpected results.
If you are seeing unexpected results in the items these setup fields create, the cause might be that some of these system variables were changed slightly. You can use the Reset to default value button 
to restore the default text (and therefore the original system variables).
Note: All of these fields are duplicated in the other windows beneath Settings > RiSE > Quick setup. The presence of those fields in the default Quick setup window is meant to ensure that at least these very important basic configuration properties are set.
Go to Settings > RiSE > Quick setup to configure the following settings:
- Panel source prefix - When enabled, all panel sources are prefixed with the defined value.
- The maximum number of results returned for a search - Specifies the maximum number of search results that the system will display.
- The number of results to show per page - Specifies how many search results to display per page. If there is more than one page of search results, links are displayed at the bottom of each page that enable navigation among the result pages.
- Enable share cookies across subdomains - Recommended if your website has more than one URL that uses the same domain. The following table details examples of domains and subdomains:
- Do not include any subdomains, including ‘www’, in the domain listings.
- You cannot share cookies across imiscloud.com subdomains.
- Use simple URLs in sitemap navigation (recommended) - When enabled, the navigation path is excluded from URLs. While this option shortens the length of URLs, any URLs that members and users may have bookmarked on their browser are still active links.
- Use canonical links for SEO (recommended) - Canonical URLs are URLs designed to help search engines rank the amount of traffic your site receives through various methods. When enabled, the canonical URLs are automatically generated and cannot be edited. The URLs use the publish file path of the content and include the first defined URL and website name of the website being visited. All URL parameters are excluded from the canonical link except for ProductCode and EventKey.
- Any content record with a Cache duration of “Default” will use this value (required) - Specifies the default system setting that will be used if Default is selected in the Cache duration field for a content record (Properties tab). Any content record with a Cache duration of Default will use this value.
- Google Maps API key - The Address Mapper and Query Menu content items can be configured to display a physical address in Google Maps. The Address type to display option determines the address purpose that displays in the map. To properly display the Google Map, the content items must be properly configured, this field must contain a Google Maps API Key, and your Google Maps Platform must have the following APIs enabled:
- Address Mapper – Requires that Geocoding API is enabled.
- Query Menu – Requires that Geocoding API and Maps JavaScript API are enabled.
- Allowed attachment file types - Specifies the types of files that can be uploaded as attachments. You can add or remove allowed attachment file types by adding them to or removing them from this field.
- Allow users to see line item details for items and invoices in the cart - When enabled, users can see line item details in the cart. This setting is enabled by default.
Note: The first character must be alphabetic. Spaces, special characters, and accents are not allowed.
| URL | Domain | Subdomain |
|---|---|---|
| example.org | example.org | |
| www.example.org | example.org | www |
| members.example.org | example.org | members |
Enabling this option allows website cookies to be shared among subdomains, making sure users stay logged while navigating between the websites. In the Share cookies across subdomains for these domains text field, enter the domain, such as example.org.
Important notes about sharing cookies across subdomains
Keep the following in mind:
Example: A member visited a page in the Member Site: www.example.com/mbrr/path/to/content.ascx. The member then visited the same page in the Annual Conference Site: www.example.com/imisannualconference/path/to/content.aspx. Visiting the same page from multiple different sources in one site will have one unique link, but the link will be different for each website you visit.
Note: There is no where to define canonical URLs, since they are automatically generated by iMIS.