171 | 171 | Upgrade from 4.2.x to 4.3.5 worked smoothly on localhost test machine. However before this could be repeated on live, 4.4.0 was released. This did not upgrade smoothly on the test server - the new word_replacements code imposes a case-insensitive uniqueness constraint which does not work well with our data. There is a patch, and 4.4.1 will be OK. The test system was restored to full functionality with the word replacements being entered manually, but for the live system, we should patch the upgrade before applying it. The patch was installed manually, and the upgrade reported completed successfully. |