With the new stylesheet structure it is easy to import the customizations when upgrading to a new QPR version. Keep the following things in mind when customizing Portal to ensure easy and flawless upgrade:
•Store all the customized images in one folder, called e.g. customimages.
•Write all the customizations into the custom.css file
This way the upgrade process is easy, as the only things you need to do is to copy the customimages folder into the new webcontent folder and transfer the customizations in the older custom.css file into the new custom.css file. Note that you should not just overwrite the new custom.css with an older customized version, since the newer file may contain classes not present in the older version. Instead, compare the files and transfer only those classes that are found also in the newer version.
QPR Template Manager
When performing an upgrade from one QPR 2017.1 to a newer maintenance release, the QPR Template Manager is run so that all non-customized template files are upgraded automatically. If any customizations are found in the template files, the file names are written to the QPR_TemplateUpgrade.log file found in the C:\ProgramData\QPR Software\QPR 2017\QPR 2017.1\Servers\Logs folder. The customizations done to the files listed in the log need to be transferred manually.
The QPR Template Manager (located in the <path to QPR 2017.1 Servers installation folder>\Utilities folder) can also be run outside the installation process, for example to check which templates include customizations.
The QPR Template Manager supports the following commands as the first command line parameter:
•Help: Gives information about how to use the manager.
•List: Shows the version information for the current parameters.
•Update: Updates the standard templates from the old versions with the new ones.