Topic: Can't start chat with v2.0

[protodev07]

Installed the latest version 2.0
Setup went fine and i've created an operator with no issues

Unfortunatly I can't start a chat - just get the spinning circle thing.

Turned on firebug and the error log picks up:

Query failed: Incorrect integer value: '' for column 'groupid' at row 1
 

I've also tried creating a group - signing an operator to it but still same error.
Currently this is the only left i need to sort before the site goes LIVE (so i'm kinda desperate to get this out)

[Dmitriy Simushev]

It seems that you're using MySQL in strict mode.

Try to run the following MySQL queries on Mibew's database:

SELECT @@GLOBAL.sql_mode;
SELECT @@SESSION.sql_mode;

and provide the results here.

[protodev07]

Thanks - heres is the info requested:

SELECT @@GLOBAL.sql_mode;
STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION

SELECT @@SESSION.sql_mode;
STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION

How can i get round this?
I cant change the server settings just for mibew! (shared development server)

Thanks

[Dmitriy Simushev]

As I've told you before, your MySQL server is running in strict mode. So you can:

1. Wait until we release the next version of Mibew with the fix. It's not a critical issue because
    it can be fixed by proper MySQL server configuration. Thus I don't think it will be fixed soon.

2. Try to fix the problem by yourself and send us a pool request. If you don't have enough
    developer skills hire somebody who has.

3. Alter MySQL server configurations.

[protodev07]

As mentioned previously - Changing the mySQL setting is not an option.

Its strict for a reason - to prevent sloppy coding and everything else on the server runs perfectly ( even Mibew 1.6 )

I havent got time to fix mibrew 2.0 issues, so I'll just install v1.6 until the issue is fixed - but after the last comment its not going to be done anytime soon.

[Dmitriy Simushev]

so I'll just install v1.6 until the issue is fixed

At the moment Mibew 2.0 was released 1.6.x branch becomes deprecated. But it's up to you to choose a version to use.

but after the last comment its not going to be done anytime soon.

Yep, we have no free hands to solve issues that are not critical right now. I don't even say that there are no third-party developers at all. Just keep waiting, it's the way to go. 

[Dmitriy Simushev]

It seems to be fixed in the main repository of the project. The fix will be included into the next release.