We have identified the issue. Table row ur_user_configs.value lenght is too short for serialized data, therefore data type should be changed to text instead of varchar(255).
Please execute the following SQL:
ALTER TABLE `ur_user_configs` CHANGE `value` `value` TEXT CHARSET utf8 COLLATE utf8_general_ci NOT NULL;
Note: change the table prefix ur_ to proper if it differs from the default.
This fix will be also available in 2.3.11 within two hours.
Hello, Paul.
We have identified the issue. Table row ur_user_configs.value lenght is too short for serialized data, therefore data type should be changed to text instead of varchar(255).
Please execute the following SQL:
ALTER TABLE `ur_user_configs` CHANGE `value` `value` TEXT CHARSET utf8 COLLATE utf8_general_ci NOT NULL;
Note: change the table prefix ur_ to proper if it differs from the default.
This fix will be also available in 2.3.11 within two hours.
We have identified the issue. Table row ur_user_configs.value lenght is too short for serialized data, therefore data type should be changed to text instead of varchar(255).
Please execute the following SQL:
ALTER TABLE `ur_user_configs` CHANGE `value` `value` TEXT CHARSET utf8 COLLATE utf8_general_ci NOT NULL;
Note: change the table prefix ur_ to proper if it differs from the default.
This fix will be also available in 2.3.11 within two hours.
Hello, Paul.
We have identified the issue. Table row ur_user_configs.value lenght is too short for serialized data, therefore data type should be changed to text instead of varchar(255).
Please execute the following SQL:
ALTER TABLE `ur_user_configs` CHANGE `value` `value` TEXT CHARSET utf8 COLLATE utf8_general_ci NOT NULL;
Note: change the table prefix ur_ to proper if it differs from the default.
This fix will be also available in 2.3.11 within two hours.
Leave a Comment
Login
/ Register
Loading...
Replies have been locked on this page!
No connection
Real-time notifications may not work
Hello, Paul.
We have identified the issue. Table row ur_user_configs.value lenght is too short for serialized data, therefore data type should be changed to text instead of varchar(255).
Please execute the following SQL:
Note: change the table prefix ur_ to proper if it differs from the default.
This fix will be also available in 2.3.11 within two hours.
Hello, Paul.
We have identified the issue. Table row ur_user_configs.value lenght is too short for serialized data, therefore data type should be changed to text instead of varchar(255).
Please execute the following SQL:
Note: change the table prefix ur_ to proper if it differs from the default.
This fix will be also available in 2.3.11 within two hours.
Hello, Paul.
We have identified the issue. Table row ur_user_configs.value lenght is too short for serialized data, therefore data type should be changed to text instead of varchar(255).
Please execute the following SQL:
Note: change the table prefix ur_ to proper if it differs from the default.
This fix will be also available in 2.3.11 within two hours.
Hello, Paul.
We have identified the issue. Table row ur_user_configs.value lenght is too short for serialized data, therefore data type should be changed to text instead of varchar(255).
Please execute the following SQL:
Note: change the table prefix ur_ to proper if it differs from the default.
This fix will be also available in 2.3.11 within two hours.
Replies have been locked on this page!