Upgrading to Version 2.6.1
Version 2.6.1 has introduced one new configuration item. You should unpack the software, and run opupdateconfig first followed by opfixperms:
...
If you want to make use of the new Report Scheduling feature, then you will also want to copy over the example schedule files from install/schedule to conf/schedule, and adjust your cron job to include opReports-scheduler.pl. Details of this new feature can be found on the Scheduling Reports page.
Upgrading to version 2.5.4 - 2.6.0
Versions 2.5.4 to 2.6.0 did not introduce any new configuration items. If your older version is 2.5.2 or newer, then unpacking the software and running opfixperms.pl once is all that is required. If you are upgrading from an earlier version please follow the steps for all intermediate versions as outlined below.
Upgrading to version 2.5.3
Version 2.5.3 did not introduce any new configuration items. Unpacking the software and running opfixperms.pl once are the only required operations if your older version was 2.5.2. If you are upgrading from an earlier version please follow the steps for all intermediate versions as outlined below.
Upgrading from version 2.5.1 to 2.5.2
Version 2.5.2 did not introduce any new configuration items, so unpacking the software will be the primary task to perform.
...
The cron scripts bin/opReports-weekly.sh and bin/opReports-daily.sh have been updated to create archival reports in both CSV and HTML format. You may need to adjust your own cron scripts in a similar fashion if you don't use the ones opReports ships with.
Upgrading to version 2.5.1
Upgrading opReports from version 2.x to 2.5.1 is almost effortless, but to gain access to the new features of version 2.5.1 a few changes have to be made.
...