v3.5-20231001 to v3.5-20240520

xpx

v3.5-20231001 to  v3.5-20240520

vot

Did you tried the /utility/update.php ???

xpx

vot 2024-06-11 21:59
Did you tried the /utility/update.php ???

Yes,
utility update.php
Copy to install
Execute *****/install/update.php

vot

I see no problems in the code.
That table is created ok!
You have provided too little info about this situation.
Can you show a full backtrace of this bug?
Try to check the database integrity!

xpx

vot 2024-06-18 09:02
I see no problems in the code.
That table is created ok!
You have provided too little info about thi ...

The database is intact.Before the upgrade, there was a "common_setting" table.After the error, the "common_setting" table disappeared.A new table "common_setting_bak" was added.

vot

Try simply re-creating the common_setting table.
To do this, simply execute a piece of code from the install/data/install.sql file:
(Do not forget to change the table prefix!!!)

1. DROP TABLE IF EXISTS pre_common_setting;
   
2. CREATE TABLE pre_common_setting (
   
3.   skey varchar(190) NOT NULL DEFAULT '',
   
4.   svalue text NOT NULL,
   
5.   PRIMARY KEY (skey)
   
6. ) ENGINE=InnoDB;
   
7. 
   

Copy the Code

And after that just insert all the corresponding data from the file /install/data/install_data.sql
like this:

1. INSERT INTO pre_common_setting VALUES (......);
   
2. ....
   
3. INSERT INTO pre_common_setting VALUES (......);
   

Copy the Code

vot

I have a guess:
perhaps the database type before the upgrade was MyISAM,
and after the upgrade it should become INNODB.
These two engines are not compatible
If my guess is correct,
then before upgrading your database, you should convert it to InnoDB type!

xpx

Thank you very much for your reply.
Before upgrading, the data was already InnoDB type.

vot

Was your problem solved?