Before and after upgrading DSS site instances to Ingeniux CMS 10.5–10.6, you can take steps to streamline upgrades and catch potential issues ahead of time. However, keep in mind that consulting the checklist below is not necessary in typical upgrade scenarios. In most cases, developers stage content within Ingeniux CMS via DSS Preview prior to deploying it to the DSS runtime site. Consequently, the Ingeniux CMS upgrade process includes DSS Preview and its associated files, provided you build DSS Preview during the CMS upgrade.

Make sure to test the following applicable items after upgrading a DSS (run-time) site to Ingeniux CMS 10.5–10.6. If you encounter issues that you cannot resolve, contact Ingeniux Support.

Ensure the following objects display and behave as expected in the DSS:

• Calendars.
• A-Z index pages.
• Media (flash, video players, any other embedded media).
• Navigations.
• Links entered in XHTML editors.
• Print-friendly page functionality.
• Assets:
  • While verifying that schemas, Functions.cshtml, and Helpers.cshtml display correctly, you may find that they need to be updated to remove images/ and documents/.
  • Make sure that the site renders correctly and that all CSS renders, even on multiple levels of subpages.
• PDF generation:
  • If integrated into the site, ensure pages can be saved and generated as PDFs.
• Forms:
  • Ensure forms can be edited.
  • Test that forms can be submitted without errors.
  • Ensure receipt of notification emails with correct content.
• Custom apps:
  • Ensure that custom apps (e.g., calculators, Cartella, third-party applications) work properly.
• Site rendering (DSS):
  • Test at least one of each page type.
  • Review site for navigation accuracy. Ensure that relevant navigations display (e.g., link text).
  • Check Site Tree redirect components, often called virtual links.
  • Evaluate speed and responsiveness.
  • Verify Start Date and End Date values are enforced.
• External Content:
  • If applicable, ensure that external content (e.g., static HTML and third-party items) works properly.
• Search:
  • Run test queries for each search type.
• Structured URLs:
  • Make sure Publish As works.
  • Ensure the live site works and that all CSS renders, even on multiple levels of sub-pages.
  • Verify pages are using structured URLs instead of xIDs.
  • Change page names and verify they update correctly after executing publishes and replications.
  • Verify that pages with the same structured URLs are appended with the page's xID.
  • Verify that "Previous" structured URLs redirect to the "current" structured URL.
  • Verify that, when browsing to a page's xID, the system redirects to the "current" structured URL.
  • Verify that a removed structured URL displays a 404 error.
  Note

  If broken links or xIDs remain after following these steps, contact Ingeniux Support.
• Redirects:
  • Check a variety of the redirects defined in your CMS to ensure they work as expected.
• Access Control List (ACL) Migration:
  • For sites that use Windows-based or basic authentication for live-site content protection, this functionality should be migrated to Run-Time Authentication (RTA). Contact Ingeniux Support for details.
• InSite Search (ISS) (if applicable):
  • Verify ISS returns results.
  • Compare search results for previous versions and for equivalence.
• Run-Time Authentication (RTA)
  • While not logged in, attempt to navigate to a protected page and confirm that the system redirects you to the login page.
  • Test invalid credentials for both invalid usernames and invalid passwords.
  • Test a variety of users who have access to different items.
  • Ensure that users can log out.
• Alert Module (if applicable):
  • Submit or enable an alert and note how long the alert takes to display.
• Caching (if set):
  • If DSS caching is activated, confirm that the cache expires at publish.