CMS 10.5.146: Site Migrator Imports Asset-Only Packages to Unexpected Folder Locations

Statement of Issue

In CMS 10.5.146, system administrators may encounter the following issues with Site Migrator packages that only contain CMS assets:

• If they pack and import (unpack) the asset-only package within the same CMS site, then Site Migrator unpacks all packaged assets to their original parent folder in Assets Manager. This behavior always occurs, no matter if administrators choose to unpack the assets to a different parent folder aside from the original.

  Site Migrator also generates new IDs for the unpacked assets. If the assets have conflicting names, then Site Migrator will rename them. For example, if the CMS already contains an asset named image.png, then the system changes the unpacked asset of the same name to image_1.jpg.

• If they pack the asset-only package in one CMS site, where the package does not contain original parent asset folder, and unpack that package in a different CMS site, then Site Migrator generates a new Images folder in the Assets Manager. The system unpacks the packaged assets to that folder.

Resolution

As a workaround, move the assets to the appropriate folder in Assets Manager after the package import completes.

Additional Information

A future version of Ingeniux CMS will address this issue.

See Site Migrator for details about asset-only packages.