Documentation Center

Troubleshooting Archive Manager Explorer

This topic describes limitations in the Archive Manager Explorer and describes possible solutions, where possible.

Absolute URLs contained inside JavaScript code are not archived.
Solution—use relative paths for URLs retrieved by JavaScript code, such as XmlHttp calls and pop-ups). For example, the following construct using a relative path to load a flash file from JavaScript is not supported:
new SWFObject(‘http://www.mysite.com/flash/myFlash.swf’, ‘top_pos’,
‘400’, ‘130’, ‘4’, '#FF0000');
Instead, use a relative path:
new SWFObject(‘/flash/myFlash.swf’, ‘top_pos’, ‘400’, ‘130’, ‘4’,
'#FF0000');
IFrames
Pages that use IFrames cannot be displayed. Because the Archive Manager Explorer displays a Web site in an IFrame, it cannot display pages that require access to the top frame (via JavaScript) cannot be viewed.
AJAX functionality
AJAX functionality that obtains data based on user input, such as clicking a drop-down list to retrieve the field data, is supported in the following cases:
  • The data to be retrieved is addressable by a relative URL and does not require server-side execution, such as a static list of countries.
  • The data to be retrieved is part of the archive, that is it is either published from Content Manager or configured as inclusion URLs in the Archive Manager config file
  • The JavaScript code used to obtain the data uses a relative path, such as /mydata/countries.xml
Use of base URL construct is not supported
Solution—all relative paths found in a page must be relative to the root of the Web site they address.
URL rewriting
Functionality that causes URL links in a page to be rewritten after the original page load is not supported.
Cookies
Page functionality that requires the use of cookies is not supported.