Problem updating database in latest version

[josby]

When upgrading to the latest version, 3.20.1, I receive a warning that I have to update the database manually, as I have done in the past.

I do as instructed:

# Dumped update query. https://v3-docs.chevereto.com/setup/update-guide.html#manual-procedure
DROP TABLE IF EXISTS chv_assets;
CREATE TABLE chv_assets (
asset_id bigint(32) NOT NULL AUTO_INCREMENT,
asset_key varchar(255) NOT NULL,
asset_md5 varchar(32) NOT NULL,
asset_filename varchar(255) NOT NULL,
asset_file_path varchar(255) NOT NULL,
asset_blob blob,
PRIMARY KEY (asset_id),
UNIQUE KEY key (asset_key) USING BTREE,
KEY md5 (asset_md5),
KEY filename (asset_filename),
KEY file_path (asset_file_path)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

ALTER TABLE chv_pages ADD page_code text ;
UPDATE chv_settings SET setting_value="default/favicon.png" WHERE setting_name="favicon_image" AND setting_value="favicon.png";
UPDATE chv_settings SET setting_value="default/logo.png" WHERE setting_name="logo_image" AND setting_value="logo.png";
UPDATE chv_settings SET setting_value="default/logo.svg" WHERE setting_name="logo_vector" AND setting_value="logo.svg";
UPDATE chv_settings SET setting_value="default/home_cover.jpg" WHERE setting_name="homepage_cover_image" AND setting_value="home_cover.jpg";
UPDATE chv_settings SET setting_value="default/home_cover.jpg" WHERE setting_name="homepage_cover_image" AND setting_value IS NULL;
UPDATE chv_settings SET setting_value="default/logo_homepage.png" WHERE setting_name="logo_image_homepage" AND setting_value="logo_homepage.png";
UPDATE chv_settings SET setting_value="default/logo_homepage.svg" WHERE setting_name="logo_vector_homepage" AND setting_value="logo_homepage.svg";
UPDATE chv_settings SET setting_value="default/consent-screen_cover.jpg" WHERE setting_name="consent_screen_cover_image" AND setting_value IS NULL;
DELETE FROM chv_settings WHERE setting_name = 'minify_enable';
UPDATE chv_settings SET setting_value = "3.20.1" WHERE setting_name = "chevereto_version_installed";

But I receive this error:

CREATE TABLE chv_assets (
asset_id bigint(32) NOT NULL AUTO_INCREMENT,
asset_key varchar(255) NOT NULL,
asset_md5 varchar(32) NOT NULL,
asset_filename varchar(255) NOT NULL,
asset_file_path varchar(255) NOT NULL,
asset_blob blob,
PRIMARY KEY (asset_id),
UNIQUE KEY key (asset_key) USING BTREE,
KEY md5 (asset_md5),
KEY filename (asset_filename),
KEY file_path (asset_file_path)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4

MySQL has said:

#1071 - Key declaration too long. Maximum key length is 767

How can I solve it?

 

[Rodolfo]

Dear user,

The software will be always drive issues if you don't handle it with care, please take time and note the requirements before jumping blindly to a new release. New releases always carry infra requirements, kindly check before panic.

#1071 - Key declaration too long. Maximum key length is 767

That denotes an old MySQL version, conflict with the indexes when using multibyte strings in table indexes. I'm sure that others will be able to help you from there.

 

[josby]

Dear user,

The software will be always drive issues if you don't handle it with care, please take time and note the requirements before jumping blindly to a new release. New releases always carry infra requirements, kindly check before panic.

Yes thanks, I'm just testing it on a test site... before I do it on my important sites.

That denotes an old MySQL version, conflict with the indexes when using multibyte strings in table indexes. I'm sure that others will be able to help you from there.

In case it happens to anyone else, I have these versions right now on the site

• PHP: 7.3.8 /usr/local/lib/php.ini
• MySQL: 5.6.34

 

[Rodolfo]

MySQL: 5.6.34

System Requirements | V3 Docs

Documentation for Chevereto image hosting software (V3)

v3-docs.chevereto.com

There's a problem there, the current requirement is MySQL 8+ 😉

 

[josby]

There's a problem there, the current requirement is MySQL 8+

Yeee hehe, I saw it later in the documentation, it's already solved... thanks! 👍