In that case, you've probably inherited someone else's failed upgrade. The problem relates to an upgrade query scripted in dbscripts/xml/upgade/2.2.0_localize.xml:
- Code: Select all
INSERT INTO site_settings (setting_name, setting_value, setting_type, locale) SELECT 'title', title, 'string', primary_locale FROM site
This part of the upgrade from 2.1.x to 2.2.0. It sounds to me like this statement has already been run, and your upgrade is attempting to run it again, resulting in duplicate entries. Perhaps someone tried to upgrade to something post-2.2.x earlier and gave up without returning the installation to its previous state properly.
If an upgrade has failed in the past, then your database is already in an indeterminate state somewhere between the two versions. If it has been used for some time since that happened, then the situation will be still more complicated because additional content will have been added using the old database conventions.
Do you have any information about the maintenance history of the installation?
Public Knowledge Project Team