Live Helper Chat support forum.. Forum is locked. New place for questions - Github Discussions
You are not logged in.
Hi,
I did an upgrade from 2.64 to 3.39.
I did everything written on this site: "doc.livehelperchat.com/docs/upgrading/"
My database was updated before I overwrote the files as suggested.
After this I saw that there is another need to update again, what I did.
After this I stuck with this screen :
lh_departament -
[name] column type/collation is not correct,
[ email] column type/collation is not correct,
[xmpp_recipients] column type/collation is not correct,
[xmpp_group_recipients] column type/collation is not correct,
[inform_options] column type/collation is not correct,
[inform_close_all_email] column type/collation is not correct,
[product_configuration] column type/collation is not correct,
[bot_configuration] column type/collation is not correct
ALTER TABLE `lh_departament`
CHANGE `name` `name` varchar(100) COLLATE 'utf8mb4_unicode_ci' NOT NULL,
CHANGE `email` `email` varchar(100) COLLATE 'utf8mb4_unicode_ci' NOT NULL,
CHANGE `xmpp_recipients` `xmpp_recipients` text COLLATE 'utf8mb4_unicode_ci' NOT NULL,
CHANGE `xmpp_group_recipients` `xmpp_group_recipients` text COLLATE 'utf8mb4_unicode_ci' NOT NULL,
CHANGE `inform_options` `inform_options` varchar(250) COLLATE 'utf8mb4_unicode_ci' NOT NULL,
CHANGE `inform_close_all_email` `inform_close_all_email` varchar(250) COLLATE 'utf8mb4_unicode_ci' NOT NULL DEFAULT '0',
CHANGE `product_configuration` `product_configuration` varchar(250) COLLATE 'utf8mb4_unicode_ci' NOT NULL DEFAULT '0',
CHANGE `bot_configuration` `bot_configuration` text COLLATE 'utf8mb4_unicode_ci' NOT NULL DEFAULT '0';
When I look into my datebase I dont see this mentions tables. Is this the error?
I just this this tables with the prefix lh_departament. Has this something to do with it?
lh_departament
lh_departament_availability
lh_departament_custom_work_hours
lh_departament_group
lh_departament_group_member
lh_departament_group_user
lh_departament_limit_group
lh_departament_limit_group_member
I´ve read that the database update should do its work by itself, maybe someone can help?
Offline
It’s fine in general in new versions i also check encoding type. Clicking update after files replacement should fix those. If not just leave as is.
Offline
I did this after file replacement, but nothing change.
So you mean just leave this error. It has no effect on the operation? But it do not look so good. Is there any way to fix this for me?
Offline
Try to copy queries and execute them in some database management tool Like phpmysql and see why it fails
Offline
ok...
when I erased the last line : CHANGE `bot_configuration` `bot_configuration` text COLLATE 'utf8mb4_unicode_ci' NOT NULL DEFAULT '0';
there was no error in the phpmyadmin.
But the last line seems to be mistaken:
ALTER TABLE `lh_departament` CHANGE `bot_configuration` `bot_configuration` text COLLATE 'utf8mb4_unicode_ci' NOT NULL DEFAULT '0';
the error is: #1101 - BLOB/TEXT-Feld 'bot_configuration' darf keinen Vorgabewert (DEFAULT) haben
in english it means that for 'bot_configuration' there should be not a default value.
Offline
Right, I check this one tomorrow. In any case it does not have any influence on operation itself.
Thanks for detailed report in any case
Offline
thank you for your quick response!
This is the error on the datebase upgrade within the backend of LHC : lh_departament - [bot_configuration] column type/collation is not correct
So I wait if you find a solution.
Thx in advance.
Offline
Here is your change.
In general should not write any error anymore
Offline