...
| Detail | Description |
|---|---|
| Minimum | The "Minimum" date entry shows the oldest timestamp in the database for an object of that type. For example, if the "Minimum" date for "Pages and page sections" is 2/28/2014, then the oldest timestamp for a page or page section is that date. This allows you to monitor the oldest date of a page or page section and gives you the option of manually updating it if you find it too old. |
| Maximum | The date shown as the "Maximum" reflects the newest timestamp in the database for an object or set of objects. |
| Update from | Specifies the beginning of the date period an object's timestamp must be to schedule it for an updated timestamp. |
| Update to | Specifies the end of the date period an object's timestamp must be to schedule it for an updated timestamp. |
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 Software strongly 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. |
...