Page 1 of 1

Error in database query (logs.php) after upgrade to r135

Posted: Tue Jan 11, 2011 1:17 am
by zzz0o

Code: Select all

*Error in database query: 'SELECT se_num,se_title,se_trigtype,se_trignum FROM ut_special ORDER BY se_num' 1054: Unknown column 'se_trigtype' in 'field list'

Code: Select all

mysql> describe ut_special; +----------+-----------------------+------+-----+---------+----------------+ | Field | Type | Null | Key | Default | Extra | +----------+-----------------------+------+-----+---------+----------------+ | se_num | smallint(5) unsigned | NO | PRI | NULL | auto_increment | | se_title | varchar(30) | NO | MUL | | | | se_desc | varchar(175) | NO | | | | | se_total | mediumint(8) unsigned | NO | | 0 | | +----------+-----------------------+------+-----+---------+----------------+
And that is true. Column se_trigtype doesn't exsists. I did updatedb from admin page after upgrading and no error reported.

Thanks in advice.

Re: Error in database query (logs.php) after upgrade to r135

Posted: Tue Jan 11, 2011 8:36 am
by Panther
That's because all the new changes have not been fully implemented in the versions of the files currently on the Subversion server. You would either need to stick with the releases, or finish the modifications I started and send in the completed version...

Re: Error in database query (logs.php) after upgrade to r135

Posted: Fri Jan 14, 2011 3:29 am
by zzz0o
Roolbacked to previuosly backup state(3.06) all scriptes and database. Get same error with ereg_replace php-function.
Update only 'includes/main.inc.php' from revision 135. Error is gone, and logs are normally parsing now.

Thanks for help.