Martin Ubank wrote:
To ensure I get the new features of v2.2.5 and the custom changes that were in place for v2.2.0, how would you suggest I go about the integration of the configuration files?
There are minimal new features in v2.2.5. Just upgrade, and everything will continue working.
Should I start with all the v2.2.0 files and ensure the new version works with them, then integrate the v2.2.5 changes, testing them one-by-one?
Or is there a better method?
I already said you could just upgrade.
For v2.2.0, I upgraded from a package install, so everything was in a different location. I added the previous custom changes into the v2.2.0 configuration files and it worked pretty much first time. That approach hasn't worked this time.
I guess the error messages are secret. Alan DeKok.