Images and files testing

Prior to upgrading to iMIS EMS, it is important to ensure all images and files have upgraded successfully.

Pre-upgrade considerations

When managing images and files stored in non-standard iMIS locations, establishing an organized and accessible folder structure is essential prior to upgrading to iMIS EMS. Files (e.g., images, PDFs) stored in non-standard locations must be identified and sent to Cloud Services. If content on the site references these files using hard-coded paths rather than relative paths, this will require content to be updated post-upgrade. To minimize post-upgrade content updates, ensure that all file references use relative paths or path variables.

Files stored in non-standard locations must be provided in a zip file and uploaded to Cloud Services for import as part of the upgrade process. Attach this folder when you send all other required elements to Cloud Services.

Note: It is not possible to request specific folders for file uploads.

Testing

Currently, documents cannot be directly uploaded to the $/Common/Uploaded files folder, as the server only supports uploads through the $/images folder. As a result, files need to be manually organized to ensure proper placement.

To maintain consistency and simplify access, clients are encouraged to use Organize > Copy/Organize > Paste methods to transfer files into the correct folder structure for testing. This approach ensures the file hierarchy remains intact and avoids errors that could occur with drag-and-drop.

Testing specifics

During the testing phase, verify that all content is properly loading images and files, which includes the following:

  1. Move uploaded files from the $/images folder to the $/Common/Uploaded files folder (RiSE > Document System):
    • Avoid moving large numbers of files at once, as this can cause iMIS to time out.
    • To reduce errors, use Organize > Copy/Organize > Paste instead of drag-and-drop.
  2. Navigate to all web pages that contain images and files.
  3. Verify the images are loading.
  4. Verify downloadable documents, such as PDFs, are downloading correctly.

Preparing for the live upgrade

If issues arise, determine whether changes can be made within the iMIS 2017 database before the live production upgrade or if scripts are needed to fix path references in the content.

Important! All testing and adjustments should be completed in staging to ensure a clear plan for file handling during the production upgrade. If there is a plan, make sure the plan is written down and assigned to someone to perform post-upgrade. This ensures a smooth go-live process.

Post-upgrade steps

The following may need to be performed post-upgrade:

  • Move uploaded files from the $/images folder to the $/Common/Uploaded files folder (RiSE > Document System):
    • Avoid moving large numbers of files at once, as this can cause iMIS to time out.
    • To reduce errors, use Organize > Copy/Organize > Paste instead of drag-and-drop.
  • Collaborate with Cloud Services to run any necessary scripts to correct file paths.