Documentation Center

Known issues

Archive Manager 1.0 SP3 has a number of known issues.

Archive Manager

Configuring profiling
Configuring an identity after an initial publishing action causes navigation to break for records that have not been republished. To solve the problem, republish all content after defining a new identity/profile is defined. In the Archive Manager configuration file you can define an identity to capture Web pages that have been personalized based on the profile of a visitor as defined in a Target Group and set using a Profiling and Personalization Cookie, the authentication credentials required for a user, and HTTP request header information for differentiating responses. You can view the configured identities in the Archive Manager Explorer Profiles view.
Case-sensitive URLs
The capturing of URLs by the Archive Manager is case-sensitive. Using different cases results in the archiving of the same resource more than once under different paths. Although the content is only actually stored once, it results in unnecessary additional path information being stored. It is therefore recommended to use consistent casing.

Archive Manager Explorer

Checking access rights
Earlier checking of access rights to Content Manager items should be performed. In the Artifacts view of the Archive Manager Explorer, you can browse to Content Manager items used to compose a Page. The Content Manager items are displayed as clickable links even if you do not have the necessary Content Manager Publication privileges to access the item. In this case, the message "You do not have permission to perform this action" is displayed followed by "Unable to find reference item (tcm:ID)" and "Error message" when you close the window.
Using a proxy
Accessing the archive via a proxy (such as tcptrace) is not supported. Using a proxy such as tcptrace between your browser and the server on which the Archive Manager Explorer is running may cause the Archive Manager Explorer to incorrectly issue a warning that the content is not coming from the archive.
Printing

Search results print incorrectly if the search string is too long: in the printed document, the right hand border of the table is absent and the search string is cut.