Learn how to overwrite an existing asset to replace it with a new version in CMS Lite.
Existing assets can be replaced with new versions by uploading a replacement file.
To replace an asset in the production environment, you must upload and publish the replacement asset.
The following asset types cannot be uploaded into the CMS Lite: shtml, html, htm, js, css, php, jsp, json. If an upload contains any of these file types, an error message will be displayed and none of the invalid files will be uploaded.
If a file with the same name is uploaded into two different asset folders, each will be assigned a unique ID (GUID). This is designed to ensure that other files with the same name (i.e. org-chart) are not accidentally overwritten.
If the intention is to overwrite an existing file, upload it into the same folder.
System validation will replace all spaces with underscores and all capitals with lowercase characters. As long as the replacement file has the same name (even if capitals and spaces appear), the overwrite message will be displayed.
If you intend to overwrite a file and you do not get the overwrite message, click Close to cancel the upload.
When replacing assets in CMS Lite with a new version, it is often helpful to use the same file name for the updated version. This approach not only aids users who have bookmarked the asset but also minimizes the chances of a search engine encountering outdated content. To track changes or versions of the document, include the version number within the document itself rather than in the file name.
Always use your best judgement based on the type and content of the file, and make sure you follow the information retention schedule.
You may also upload a single asset to the Asset Settings Pane.
To replace an existing asset: