Fresh install "problem importing the database"
Posted: Mon Sep 11, 2023 2:49 am
Just providing this as a reference here in case anyone else encounters this issue while installing the latest Phoenix cart...
Created an empty database and user on the server, uploaded all files, changed permissions on configure files, and started the web install. It got stuck on:
PHP log warnings/notices:
Tried importing the referenced phoenix.sql using PhpMyAdmin... and got an error (only with the action_recorder table, all others got created ok):
That server is using PHP 7.4.26, MariaDB 10.4.20, default_storage_engine variable is MyIsam
Not sure if users can be expected to find or fix that SQL error easily without the help of the install page, maybe errors creating tables should be related back to the install page somehow?
I don't remember having that key length problem with older installs. Posted as an issue on Github.
Created an empty database and user on the server, uploaded all files, changed permissions on configure files, and started the web install. It got stuck on:
Using localhost, correct username and database.. (If the user did not have proper privileges to the database I got a different, more informative warning)There was a problem importing the database. The following error had occured:
Please verify the connection parameters and try again.
PHP log warnings/notices:
Code: Select all
[10-Sep-2023 21:31:52 US/Eastern] PHP Notice: Undefined property: sql_file::$errno in /storetest/includes/system/versioned/1.0.8.9/sql_file.php on line 92
[10-Sep-2023 21:31:52 US/Eastern] PHP Notice: Undefined property: sql_file::$error in /storetest/includes/system/versioned/1.0.8.9/sql_file.php on line 92
[10-Sep-2023 21:31:52 US/Eastern] PHP Warning: DB: [] from </storetest/install/phoenix.sql> in /storetest/includes/system/versioned/1.0.8.9/sql_file.php on line 93
[10-Sep-2023 21:31:52 US/Eastern] PHP Notice: Undefined variable: db_error in /storetest/install/rpc.php on line 89
Code: Select all
CREATE TABLE action_recorder (
id int NOT NULL auto_increment,
module varchar(255) NOT NULL,
user_id int,
user_name varchar(255),
identifier varchar(255) NOT NULL,
success char(1),
date_added datetime NOT NULL,
PRIMARY KEY (id),
KEY idx_action_recorder_module_date (module, date_added),
KEY idx_action_recorder_user_id (user_id)
) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
MySQL said: Documentation
#1071 - Specified key was too long; max key length is 1000 bytes
Not sure if users can be expected to find or fix that SQL error easily without the help of the install page, maybe errors creating tables should be related back to the install page somehow?
I don't remember having that key length problem with older installs. Posted as an issue on Github.