Most troubels i had was due to my custom template and custom language bundle files. Those are horrid to maintain as there were changes too.
Other than that i didnt face much troubels - fortunately. So i cant tell if there's more issues from 2.1.6 to 2.1.7
What you could do however is - if it tells you there's fields missing, try to check out the 2.1.6 or 2.1.7 create scripts. Somewhere the field definitely is defined and update the database manually and erase error by error.
Though it's best if you do a backup before ;) Just for sure
The errors you posted all look like database dependend errors. What I noticed too is that you use postgre. You could aswell check on the mysql update scripts and try to figure out differences . The mysql files most propably are updated best... as it's the most common used database ... [originally posted on jforum.net by Sid]
Turns out that the real problem is that I don't know my own data server. I had an old database from the 2.1.4 days and, lo and behold, I can't upgrade that from 2.1.6 to 2.1.7. Sorry for the confusion - trying to get something done on a slow week and it turns out my brain is a bit slow too. [originally posted on jforum.net by stdunbar]
I also need to upgrade from 2.1.6 to 2.1.8. You say I need to upgrade to 2.1.7 first, and to do this I have to build 2.1.7 from cvs first. Seeing as 2.1.7 is actually still needed coz you cant just upgrade from 2.1.6 to 2.1.8 it would be nice if you could maintain a link on the downloads page to the older versions to make the upgrade simpler please, dont you think ?