News:
Bored? Looking to kill some time? Want to chat with other SMF users? Join us in IRC chat or Discord
Recent posts
#21
SMF 2.1.x Support / Re: "You were unable to login....
Last post by Wolpo - Today at 05:36:01 AMUnderstood. Thank you. Well, OK, I'll try again next week. Actually I wanted a transfer that won't deny the forum access for more than a few minutes. Considering that database problem I described above, it may take hours or days. Anyway, I'll try again.
Just in case it's relevant:
My old host's customer panel provides a database backup function (sql and zip). There is a checkbox that reads "Backup with extended inserts". I usually select this checkbox. The host doesn't explain this checkbox. Has anyone any idea what "extended inserts" are? I guess it's related to the DB import later on, in phpMyAdmin.
Just in case it's relevant:
My old host's customer panel provides a database backup function (sql and zip). There is a checkbox that reads "Backup with extended inserts". I usually select this checkbox. The host doesn't explain this checkbox. Has anyone any idea what "extended inserts" are? I guess it's related to the DB import later on, in phpMyAdmin.
#22
SMF 2.0.x Support / Re: Continuous error messages,...
Last post by shawnb61 - Today at 12:31:33 AMThat was explained above. The engine & row format do not support the SMF db using utf8mb4. Index key size problem. (If you need all the background underlying that, Google is your friend.)
There are things you can do to address that, but SMF 2.x doesn't take advantage of utf8mb4, so it's kind of pointless. I mentioned that earlier as well.
To proceed with utf8mb4, despite the fact that SMF 2.x doesn't use it, you'd need to change all your tables to use the InnoDB engine. It's possible you need to alter the row format also. As I mentioned earlier, utf8mb4 is a non-standard configuration, not tested, so you may see issues. You'd be testing it.
Or you could set everything to utf8mb3, the standard config for 2.x. For the reasons stated above, this is my recommendation.
Whichever way you go, it is generally recommended to keep all your tables on the same collation & engine. Inconsistencies can hurt performance.
There are things you can do to address that, but SMF 2.x doesn't take advantage of utf8mb4, so it's kind of pointless. I mentioned that earlier as well.
To proceed with utf8mb4, despite the fact that SMF 2.x doesn't use it, you'd need to change all your tables to use the InnoDB engine. It's possible you need to alter the row format also. As I mentioned earlier, utf8mb4 is a non-standard configuration, not tested, so you may see issues. You'd be testing it.
Or you could set everything to utf8mb3, the standard config for 2.x. For the reasons stated above, this is my recommendation.
Whichever way you go, it is generally recommended to keep all your tables on the same collation & engine. Inconsistencies can hurt performance.
#23
Modifications and Packages / Re: Ad Management mod
Last post by vbgamer45 - Today at 12:26:48 AMwhat ad types do you have installed?
#24
SMF 2.0.x Support / Re: Continuous error messages,...
Last post by parsa - Today at 12:08:57 AMSince I theoretically set all the character sets to utfmb4 using my query, will that be problematic? I didn't see any field in the Operation tab for character set.
By the way, my continuous forum error messages have stopped, so at least I accomplished that much.
Why are those two tables not wanting to go to utfmb4_unicode_ci?
By the way, my continuous forum error messages have stopped, so at least I accomplished that much.
Why are those two tables not wanting to go to utfmb4_unicode_ci?
#25
SMF 2.0.x Support / Re: Continuous error messages,...
Last post by shawnb61 - Today at 12:02:54 AMI pointed out earlier that mb4 may not work, for this very reason... (Engine & row format can blow out the index key length...)
You really need to stick with utf8mb3_general_ci.
Get them all to utf8mb3_general_ci.
You really need to stick with utf8mb3_general_ci.
Get them all to utf8mb3_general_ci.
#26
SMF 2.0.x Support / Re: Continuous error messages,...
Last post by parsa - Yesterday at 11:53:15 PMThanks. Too bad I didn't know about that general operations tab earlier. However, it wouldn't have worked as two of the tables returned errors (see below).
For procedures #4–6, those already had those settings.
Everything went fine for all but two tables. Since the database was set to "utf8mb4_unicode_ci", I set everything to that. I actually used a query of the form:
Two tables persistently wanted to stay in "latin1_swedish_ci": smf_members and backup_smf_messages.
I managed to change them to "latin1_general_ci".
Then after they were in that form, it was possible to change them to "utf8mb3_unicode_ci"
However, when I tried to change them to utf8mb4_unicode_ci", I would get the following messgae for both tables:
It did the same thing when I tried to use the Operations tab. I could actually change individual rows to utf8mb4_unicode_ci, but the "real_name" column (in smf_members) would not change. It just gave the error message above. The same happened with about three rows in the backup_smf_messages table.
I'm not sure if having one regular table as utf8mb3, while all the others are utf8mb4, is going to cause a problem....
For procedures #4–6, those already had those settings.
Everything went fine for all but two tables. Since the database was set to "utf8mb4_unicode_ci", I set everything to that. I actually used a query of the form:
Code Select
ALTER TABLE smf_tablename CONVERT TO CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;That worked the same as using the Operations tab for each table.Two tables persistently wanted to stay in "latin1_swedish_ci": smf_members and backup_smf_messages.
I managed to change them to "latin1_general_ci".
Then after they were in that form, it was possible to change them to "utf8mb3_unicode_ci"
However, when I tried to change them to utf8mb4_unicode_ci", I would get the following messgae for both tables:
It did the same thing when I tried to use the Operations tab. I could actually change individual rows to utf8mb4_unicode_ci, but the "real_name" column (in smf_members) would not change. It just gave the error message above. The same happened with about three rows in the backup_smf_messages table.
I'm not sure if having one regular table as utf8mb3, while all the others are utf8mb4, is going to cause a problem....
#27
SMF 2.0.x Support / Re: Continuous error messages,...
Last post by shawnb61 - Yesterday at 11:32:39 PMQuote from: Sir Osis of Liver on Yesterday at 10:51:18 PMphpmyadmin allows you to change all table collations in one go, in Operations > Collations. There's a checkbox for 'Change all tables collations', I believe that also changes column collations.
Yep... Never saw that before. Just tried it, & it seems to work, too...
Note the 2nd checkbox doesn't appear until after you check the first checkbox. Both must be checked.
You cannot view this attachment.
#28
Modifications and Packages / Re: Ad Management mod
Last post by Sir Osis of Liver - Yesterday at 11:30:17 PMNow it's offscreen right -
You cannot view this attachment.
You can see it here
Looks like it inherited content from ver. 3.3a. Forum was upgraded from 2.0.19 > 2.1.4, ver. 3.5d was installed after upgrade to replace 3.3a.
You cannot view this attachment.
You can see it here
Looks like it inherited content from ver. 3.3a. Forum was upgraded from 2.0.19 > 2.1.4, ver. 3.5d was installed after upgrade to replace 3.3a.
#29
Modifications and Packages / Re: Ad Management mod
Last post by Sir Osis of Liver - Yesterday at 11:09:51 PMInstalled version 3.5d in 2.1.4 install, it breaks the login window in phone view, username field is offscreen top so it's impossible to login. Global Headers Footers 2.1a and Automatic Attachment Rotation (and Resize) 6.25 are installed. Just reinstalled it and all I see in phone view is two ads, nothing else.
#30
SMF 2.0.x Support / Re: Continuous error messages,...
Last post by Sir Osis of Liver - Yesterday at 10:51:18 PMphpmyadmin allows you to change all table collations in one go, in Operations > Collations. There's a checkbox for 'Change all tables collations', I believe that also changes column collations.