Just to note- it’s always a good idea to have php errors shown to superadmins. I flipped that on in ‘Admin- System Prefs- Output and debug’ and we get a mysql error:
Description: Unknown column 'last_author_id' in 'field list'
Query: SELECT group_id, template_name, save_template_file, template_data, template_notes, template_type, edit_date, last_author_id FROM exp_templates WHERE template_id = '14'
That field is added in the 1.6.5 update. (On the plus side, there were no db changes in 1.6.6, so if we can fix anything that was missed in 1.6.5 you’ll be good to go.)
To see what changed in 1.6.6, open up system/updates/ud.165.php. We need to check all the queries and make sure the changes went through.
Do you have access to phpmyadmin? That’s likely the easiest way to approach this.
Go in- and see if the first db change was made:
$Q[] = "ALTER TABLE `exp_search` CHANGE `query` `query` MEDIUMTEXT NULL DEFAULT NULL";
Look at the structure of exp_search in phpmyadmin. Is the ‘query’ field set to mediumtext? If so, that query went through. If not, it failed.
Now- if it was changed? I would comment out that query a la:
//$Q[] = "ALTER TABLE `exp_search` CHANGE `query` `query` MEDIUMTEXT NULL DEFAULT NULL";
Do that until you get to where the db change didn’t happen. At that point, you could either put up a backup config.php from 1.6.4 or edit your config.php file back to version 164 and then run the updates to 1.6.5 and 1.6.6.
Make sense in general?
We can walk you through it, but the first step will be to find where the db changes failed.
Oh- and I’m going to shift to ‘Install’ since the core issue is really the failed update.