Error after installing WB

[scheltel]

Hi,

I just have installed Website Baker 2.8.2 on a Windows 2008 with Apache 2.2.16, PHP 5.2.10.10 and MySQL 5.1. After I log in in the admin part of WB I'm getting the following error message:

Fatal error: Call to a member function fetchRow() on a non-object in C:\ApacheSites\mysite\framework\class.login.php on line 135

Is there someone who can tell me what can be wrong? The installation procedure gave no errors at all.

Regards,


scheltel

[ruebenwurzel]

Hello,

it looks like not all tables are installed. Is there a users Table in your database?

Matthias

[scheltel]

Hello,

Yes, there is a users table and it contains one record for username = 'admin'

Regards,

scheltel

[scheltel]

Hello,

I did the query which causes the error manually in the MySQL Workbench:

SELECT * FROM `users` WHERE `username` = "admin" AND `password` = "03843becf17488afe6f cc99dc799e7d4" AND `active` = 1;

The error I'm getting is:
Error Code: 1054 Unknown column 'admin' in 'where clause'

It looks like MySQL does not understand the query. 

Regards,

scheltel

[DarkViper]

can you try following statement in your workbench please?
take care please for the exact syntax.
check, if really no prefix is needed for the tablename.

Code:

SELECT * FROM `users` WHERE (`username`='admin') AND (`password`='03843becf17488afe6fcc99dc799e7d4') AND (`active`=1)

[scheltel]

That query did return a record.

I think problem is caused by the double quotes around the values which are supplied in the query.

Do you know if there is a MySQL server setting to avoid get MySQL working with values which are double quoted?

Regards,

scheltel

[DarkViper]

it looks like your mysqld is running in non ANSI Mode (it often is a problem in a win environment).

Since any time w are working on to make all sql statements in WB SQL-strikt, but unfortunately, there are a lot of them and we need time to make it complete.

please try following (both lines should be sent at once):

Code:

SET SESSION `sql_mode`='ANSI';
SELECT * FROM `users` WHERE `username` = "admin" AND `password` = "03843becf17488afe6fcc99dc799e7d4" AND `active` = 1;

if this works, you need a small patch in the class.database.php - file

Code:

<?php

65                        if(!mysql_select_db(DB_NAME)) {
66                                $this->connected = false;
67                                $this->error = mysql_error();
68                        } else {
69                                $this->connected = true;
++                               mysql_query('SET SESSION sql_mode=\'ANSI\'');
70                        }

?>

[scheltel]

I'm still getting the same error 

Strange... Older versions of WB (2.6.7)  do not have this problem on the same machine.

[ruebenwurzel]

@scheltel

How is your MySQL configured? Is it running on Strict Mode or not?

But as 2.6.7 is running i think it doesn't run in strict mode, as 2.6.7 isn't definately written for strict Mode.

Matthias

[scheltel]

See sql_mode part from the my.ini file.

# Set the SQL mode to strict
sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION"

[scheltel]

The server is already running in ANSI mode:

mysql> SELECT @@global.sql_mode;
+-------------------------------------------------------------+
| @@global.sql_mode                                           |
+-------------------------------------------------------------+
| REAL_AS_FLOAT,PIPES_AS_CONCAT,ANSI_QUOTES,IGNORE_SPACE,ANSI |
+-------------------------------------------------------------+
1 row in set (0.00 sec)

mysql>

I think the ANSI_QUOTES setting is the cause of the problems.

[DarkViper]

ok...  i examinate the SVN back into the past and found that around 2 years ago single-quoting was changed into doublequoting on class.login.php. Don't ask me why please... 

It had no negative effect till now because older versions of mySQL handle it a bit more tolerant then newer ones using strikt mode.

Anyway. I changed all sql statements inside that class into sql-strikt now. Please test with the attached file and give me a note if it works. Then i will move it into SVN.

[scheltel]

The class.login.php works fine now. Thank you DrakViper But know I'm getting an error when I try to add a new page:

Unknown column '_top' in 'field list'

[ruebenwurzel]

Hallo,

ist WB jetzt schon komplett auf die Zusammenarbeit mit MySQL strict Mode umgestellt? Ich glaube nicht, wenn schon, dann müsste ich den Entwicklern ein dickes Lob ausprechen  . Und selbst wenn der Core schon aktualisiert ist, viele Module sind es definitv noch nicht. Deswegen mal hier lesen:
I don't think that the whole core of WB is ready for MySQL strict mode. But even this would be the case, the most modules wouldn't. Read here:

http://dev.mysql.com/doc/refman/5.1/de/mysql-config-wizard-networking.html
http://dev.mysql.com/doc/refman/5.1/en/mysql-config-wizard-networking.html

und dann zum deaktivieren des strict-modes bitte folgendes in der my.ini ändern:
To deactivate strict mode change:

Code:

sql-mode="STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

ändern in:
to:

Code:

sql-mode="NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION

einfach das STRICT_TRANS_TABLES entfernen und dann mysql neu starten.
simply remove STRICT_TRANS_TABLES and restart MySQL.

Danach sollten deine Fehlermeldungen (hoffe ich) weg sein.
After this there should be no more Error messages.

Matthias

P.S.
Didn't realized that I'm in the english Part of the Forum, translated it now.

[scheltel]

@ ruebenwurzel

I have tried to alter the settings using the ' MySQL Server Instance Configuration Wizard'. But after that the MySQL Windows Service did not start at all.

After some research the Windows Service appeared to be started with the parameter '--ansi'. I think this parameter had a conflict with the new my.ini. I have removed the parameter using regedit. And now the service starts OK.

The Strict Mode is totally disabled now,  WebsiteBaker 2.8.2 runs well on my server!

Thank you all for your support.