...
| Table of Contents | ||||
|---|---|---|---|---|
|
Redirects
Alias redirects route URL requests for nonexistent URLs to a valid target URL. The target URL for an alias redirect can be a page in the current web initiative(s) as well as an external URL. Redirects allow you to make available simple, easy to remember URLs to direct visitors to pages on your website in cases where your tree structure is complicated or the target URL contains a difficult to remember path structure. URL aliases can only be a single identifier that contains no hierarchical structure. The address of the alias URL is relative to the root URL of your website. For the website www.gxsoftware.com,, for example, any alias URL you create can only be reached in a browser via a URL that adds the identifier to the root address, www.gxsoftware.com/<alias> for example, where <alias> is an identifier such as "Products", "Services", "Developer Support" and so forth.
...
Language Labels
Using the :Language Labels" panel, you can manage the labels that appear in the XperienCentral front-end for all your channels. This includes labels that appear in content elements and all informational and error messages for all the languages supported by your website. You can also copy all labels from a language and then create support for a new language.
To access the Language Labels panel, navigate to Configuration > Language Labels:
Select the channel for which you want to maintain language labels from the "Select Channel" drop-down list at the top of the panel and then select the language containing the label(s) you want to modify from the "Select Language" drop-down list.
For each supported language, the following properties are shown:
| Property | Description |
|---|---|
| Order | In the far left column, a number is assigned to each language. This affects the order that they appear in the "Select Language" drop-down list. To change the order select a new number for the language(s) and then click [Apply]. |
| Active | When this checkbox is selected, the language is active and available to be used in XperienCentral. |
| Language Code | The internal ID of the language in XperienCentral. |
| Name in XperienCentral | The string that appears in drop-down lists in XperienCentral when you select the language property for a page and in the Language Widget. |
| Delete | A checkbox for deleting a language. You can only delete a language that you have added. Because English and Dutch are the two standard languages supported in XperienCentral, they cannot be deleted. |
| Copy | A button for copying all the language labels for a language. You use this functionality to add new languages. |
In this section
Modifying a Language Label
Copying a Language
Deleting a Language
...
Modifying a Language Label
To modify a language label, expand the section containing it by clicking the plus [+] sign next to it. The language labels appear. On the left side of the list is the internal identifier for the language label and in the text field next to it is the current label being used for it in the current language. To modify a label, click in the field and change the text.
In the example below, the string for the "Author" line in the Downloads content element is changed to "Publisher":
After clicking [Apply], the label is modified. In the Editor, the label in the Download content element now appears as "Publisher":
Perform these steps for all labels that you want to modify for the selected language. Click [Apply] to submit your modifications.
...
Copying a Language
You can copy all of the labels for a language in one operation. This makes it possible to create support for a new language. You simply have to change the labels in the copied language to the new one you want to support. To copy a language, click [Copy] next to the language. For example:
XperienCentral will then prompt you to provide a code for the new language. For example:
Click [Apply]. The new language will appear in the list. Enter the translation of the language's name in Dutch and English. For example:
Modify the labels for the new language. Once copied, the new language is available in the Language Widget. For example:
The new language is now also available in the default language drop-down list for a page. For example:
Back to top
...
Deleting a Language
To delete a language, follow the steps below. You can only delete a language that you have added. Because Dutch and English are the default supported languages in XperienCentral, neither of them can be deleted. When you delete a language, any pages based on that language will also be deleted therefore you should exercise extreme caution when performing this operation.
To delete a language:
- Select the checkbox for the language in the "Delete" column in the list of languages.
- Click [OK] to confirm the operation:
The labels for the language are deleted.
To create an alias redirect, follow these steps:
...
Deleting a Redirect
To delete a redirect, follow these steps:
...
Dumped Content
...
| Info |
|---|
The extension given to the dumped HTML file should be different from the extension of the friendly URLs. Apache determines, based on a fixed pattern in the URL, where the page data should come from. By default, Apache transfers those URLs beginning with |
For performance reasons, XperienCentral will always use the static variant of a page if one exists. For example, a page with the title "Economy" has the corresponding friendly "Economy.htm" URL and is also dumped to "Economy.html". When "Economy" is requested, XperienCentral will refer to "Economy.html" because it can be loaded faster. Requests to "Economy.htm" will also work but the response could be somewhat slower because the web server has to generate the page.
Dumping Pages to Static HTML Files
To dump a dynamic page in XperienCentral to a static HTML file, follow these steps:
...
| Note |
|---|
The relative URL that you specify must match the friendly URL listed under "URLs used by active versions" in the "SEO" tab of the Properties Widget. |
...
Caching
Caching is essential for high traffic websites. It will handle the load created by the many page requests by using an intelligent mechanism that returns pages without having to regenerate them completely. The XperienCentral caching module is also tailored to not interfere with interaction and personalization, therefore visitors to your site will not notice that they are looking at a largely static website.
This topic explains the options available in the Server Configuration. For a complete discussion of caching in XperienCentral, see Caching.
Cache Settings
Under normal conditions, XperienCentral manages the cache when content is changed, added or removed. When an editor adds an element to a page, the timestamp for the page will be set to the current date and time. The next time that the modified page is requested, the caching mechanism will regenerate the page.
There are more complex situations, for example when several page sections are involved or situations where a lot of caching timeouts are set for individual parts of a page or when the load on the server is very high and there's no time to regenerate pages. Content is normally regenerated automatically, however, in some situations, you do not want to wait until a visitor requests the content, but instead you want to manually force all the content to be regenerated.
Navigate to Configuration > Server Configuration > Caching. The Caching tab appears as follows:
...
Updating the Timestamps
To immediately update the timestamps to the current date and time, click the [Update Timestamps] next to the specific content type. When this action is performed, each content item will be regenerated and placed in the cache the next time it is requested. If your website contains a large number of the specific type that you update, use caution because this action could put a large load on the server.
Updating all Timestamps
To update the timestamps for all content types on your website, click [Update Timestamps] next to "General Timestamp". Updating the timestamps in this manner is a relatively safe action to perform on all environments. After activating the "General Timestamp", requests from the front-end trigger two actions. The first action is that the requested content is directly served from the cache without first being updated. The second action is that the backend is requested to regenerate the content in the background. When this has finished, the cache is updated with the latest version of the content.
Initializing the Cache
| Warning |
|---|
GX highly recommends that you do not use this command on production environments. This command immediately sets the timestamp for all content (pages, articles, database objects, etc). If you have a site with a lot of content, this process could take a long time and will put a heavy load on the server. The effect of executing this command is that each request on the front-end may not be served from the cache, which leads to a request on the backend. In most cases, this has a negative impact on the performance of your website(s) and on the XperienCentral Workspace. |
...