CiviCRM Community Forums (archive)

I have just upgraded to 3.2.1, but had not yet installed new localisation files when 3.2.2 came out - users were complaining about various aspects of the new interface so up I go...

First off the version is reported as 3.1.1 - though I upgraded from 3.0.4 and I am sure, sure that I upgraded to 3.2.1... though not only the database but also the version.txt states 3.1.1

After some fiddling about involving attempts and restoring the backup I decided to change the version number in civi_domain...

This time it upgraded - or rather it did not report any errors.

The home page tells me menus have been rebuilt and invites me to set up the dashboard - when I do it shows the acticities list in the left hand side as I left it - on clicking done I get exactly the same invitation to configure the dashboard. Javascript is enabled and this happens in both chrome and firefox

The contact search box in the tool bar does not work and when I fo to the search page I get this:

Database Error Code: Unknown column 'is_tagset' in 'where clause', 1054
Additional Details:
Array
(
    [callback] => Array
        (
           

• => CRM_Core_Error
[1] => handle
        )

   

=> -19
    [message] => DB Error: no such field
    [mode] => 16
    [debug_info] => SELECT id, name, parent_id
                  FROM civicrm_tag
                  WHERE  is_tagset = 0 AND parent_id IS NULL AND used_for LIKE '%civicrm_contact%' ORDER BY name [nativecode=1054 ** Unknown column 'is_tagset' in 'where clause']
    [type] => DB_Error
    [user_info] => SELECT id, name, parent_id
                  FROM civicrm_tag
                  WHERE  is_tagset = 0 AND parent_id IS NULL AND used_for LIKE '%civicrm_contact%' ORDER BY name [nativecode=1054 ** Unknown column 'is_tagset' in 'where clause']
    [to_string] => [db_error: message="DB Error: no such field" code=-19 mode=callback callback=CRM_Core_Error::handle prefix="" info="SELECT id, name, parent_id
                  FROM civicrm_tag
                  WHERE  is_tagset = 0 AND parent_id IS NULL AND used_for LIKE '%civicrm_contact%' ORDER BY name [nativecode=1054 ** Unknown column 'is_tagset' in 'where clause']"]
)

I have rolled back in agony...

If I do try to upgrade from 3.1.1 then I get this error on upgrade:

Database Error Code: Table 'civicrm_entity_financial_trxn' already exists, 1050

retoring then getting trigger happy and dropping the table then results in this error:

Database Error Code: Table 'civicrm_financial_account' already exists, 10

So I figure I did really upgrade to 3.2.1 and it is a version reporting error.

Any pointers would be appreciated.

Thanks, Myles





Thanks Lobo,

I have confirmed that I had indeed upgraded to 3.2.1 even though this reports 3.1.1 - I have several times restored to 3.2.1 and re-attempted the upgrade to 3.2.2, and each time with the same results.

My conclusion is that the upgrade from 3.2.1 to 3.2.2 is not working.

Had I scrolled down to the bottom of the announcement of the release of 3.2.1 I might have seen the notice that there was an error and to wait for 3.2.2.... but I didn't (Where's the emoticon with the guy clocking himself on the head with a hammer!).

Looking through the issues list I see that there was a whole debate about patches prior to the release of 3.2.2 - though I am not clear what to do, I get the impression I should be able to fix 3.2.1 and effectively bring it up to 3.2.2 standard.

Since, as far as I can tell, this latest update is mostly a fix to the upgrade script, what really concerns me is to ensure that we can upgrade cleanly on the next release.

Can you help direct me to an understanding what I need to do from here?

I am fairly competent with databases.

Many thanks