Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#1 2009-12-06 02:46:43
- dreamer
- Member
- Registered: 2007-06-08
- Posts: 242
Getting error messages upon upgrading to 4.2
I get these messages on the admin-side. What did I do wrong? I followed everything correctly when upgrading.
Warning: Unknown column ‘user_name’ in ‘where clause’ select name, val from txp_prefs where prefs_id=1 AND user_name=’‘ in /home/gdpnorg/public_html/textpattern/lib/txplib_db.php on line 85
Notice: Undefined variable: language in /home/gdpnorg/public_html/textpattern/index.php on line 70
Warning: Cannot modify header information – headers already sent by (output started at /home/gdpnorg/public_html/textpattern/lib/txplib_db.php:85) in /home/gdpnorg/public_html/textpattern/include/txp_auth.php on line 169
Warning: Cannot modify header information – headers already sent by (output started at /home/gdpnorg/public_html/textpattern/lib/txplib_db.php:85) in /home/gdpnorg/public_html/textpattern/include/txp_auth.php on line 170
Offline
Re: Getting error messages upon upgrading to 4.2
You did read readme and release notes:
NOTE: Upgrades from versions below 4.2.0 will present this warning upon your very first login to the admin-side:
Warning: Unknown column 'user_name' in 'where clause' select name, val from txp_prefs where prefs_id=1 AND user_name='' in /path/to/your/site/textpattern/lib/txplib_db.php on line xxThis is expected behaviour for the very first login after an upgrade. Every further move in the admin side must not throw any error message.
And you did try to move on, right? And after that you did go to update your language file and set your new tz preferences (if on php5, to avoid errors when calling tz settings).
Offline
#3 2010-06-19 15:42:40
- neilbag00
- New Member
- Registered: 2006-03-11
- Posts: 9
Re: Getting error messages upon upgrading to 4.2
I’ve just had this error. The trick for me was to delete all relevant cookies so that I could log in properly. I did have to try to log in a few times like this until all the error messages finally died down. I almost gave up but thought I’d try loggin in one more time and it was all ok!
Offline
Offline