Things to Consider Before Moving or Renaming Cascade Assets
Cascade makes it easy to move and rename assets such as pages, folders, images and documents — but should you? Consider the following factors before moving or renaming:
- Moving or renaming an asset changes its URL.
- External links to the page, image or document will break.
- Internal links will be maintained and only require the publishing of affected pages.
- Changes to a folder impact your page menus and will require some extra publishing.
External Links
When Cascade assets are moved or renamed, external links to that asset are broken. Consider saving these actions for times during the year when your site is not being visited frequently.
Google Search (which also powers our site searches) typically catches up with your changes in about a week, but it can take as long as 30 days.
Internal Relationships
Before moving or renaming, view the asset's relationships to see which other Cascade assets are internally linking to it. This will indicate internal relationships within your same domain such as www.wm.edu, law.wm.edu, education.wm.edu, etc.
If any relationships exist, they will be maintained in Cascade, but the impacted assets will need to be published for the live site to reflect the changes. For example, if you move or rename a file, any page that is internally linking to that file will need to be published.
Note: Once a week all of our sites are published in the overnight hours, as a courtesy.
Listing Folders
If you rename pages within a listing folder (for example, if you change an employee's name in a directory listing) be sure to publish that folder's index page where the pages are automatically listed.
Page Menus
Because folder settings affect your page menus, if you move or rename a folder, you'll need to publish the parent folder to ensure all impacted page menus are properly updated. If you move a folder from one folder to another, you'll need to publish both parent folders.
