wp-config has been modified:
/** Database Charset to use in creating database tables. */ define('DB_CHARSET', 'utf8mb4'); /** The Database Collate type. Don't change this if in doubt. */ define('DB_COLLATE', 'utf8mb4_unicode_ci');
[client] #default_character_set = utf8mb4 [mysql] default_character_set = utf8mb4 no-auto-rehash [mysqld] character-set-server = utf8mb4 collation-server = utf8mb4_unicode_ci character-set-client-handshake = FALSE init_connect = 'SET NAMES utf8mb4'
(fwiw, we're using cPanel packaged MariaDB at a set of LiquidWeb servers)
So, we expected Akeeba to create its tables informed by defines in wp-config (and failing that had hoped that our cnf settings would have forced the matter...)...
What actually happened is that the following tables were created using utf8_general_ci
wp_1_akeeba_common wp_1_ak_params wp_1_ak_profiles wp_1_ak_stats wp_1_ak_storage wp_1_ak_users
We would like to know if
a) it is likely OK to alter these tables post-install and
b) it is possible to have utf8mb4/utf8mb4_unicode_ci autodetected from wp-config (or from server settings, either way...)? (we would rather not have to make changes every time we install AKeeba)