I have been using MailPoet for more than 4 years without any problems. Now I get the following message after the last update of the plugin:
Some of the MailPoet plugin’s tables are not using the InnoDB engine (“ogrcx_mailpoet_automation_run_logs”, “ogrcx_mailpoet_automation_run_subjects”, and 38 more). This may cause performance and compatibility issues. Please ensure all MailPoet tables are converted to use the InnoDB engine. For more information, check out?this guide.
Does that mean that all tables must now be changed manually?
That can’t really be the point of a plugin!
wp_posts: Unknown storage engine ‘InnoDB’
wp_comments: Unknown storage engine ‘InnoDB’
wp_links: Unknown storage engine ‘InnoDB’
wp_options: Unknown storage engine ‘InnoDB’
wp_postmeta: Unknown storage engine ‘InnoDB’
wp_terms: Unknown storage engine ‘InnoDB’
wp_term_taxonomy: Unknown storage engine ‘InnoDB’
wp_term_relationships: Unknown storage engine ‘InnoDB’
wp_termmeta: Unknown storage engine ‘InnoDB’
wp_commentmeta: Unknown storage engine ‘InnoDB’
Any suggestions about how to fix it?
]]>WP-Optimize – Cache, Clean, Compress kan zo worden ingesteld dat de database automatisch (van tijd tot tijd) wordt geoptimaliseerd. Dat is handig voor websites die regelmatig van nieuwe content voorzien worden, maar ook voor websites die het met wat minder aandacht moeten stellen. De updates van WP en de plugins laten ook hun sporen na.
Wat ik zelf erg handig vind, is de functionaliteit die oude tabellen kan omzetten naar innoDB. Mogelijk verraad ik mijn leeftijd nu, maar ik herinner me hoe spannend het was om het handmatig te doen. Ook geeft WP-Optimize – Cache, Clean, Compress eerst netjes aan als tabellen geen functie meer hebben. Bijvoorbeeld na het verwijderen van een plugin. Je kunt dan zelf kiezen of de tabel weg kan of niet. Het is immers niet ondenkbaar dat een plugin slechts tijdelijk verwijderd is.
Een aanrader!
]]>
The following DB Tables are still missing.?
Table?br_wpmailsmtp_tasks_meta:?Reason?Unknown.
Table?br_wpmailsmtp_debug_events:?Reason?Unknown collation: ‘utf8mb4’
Any suggestion to solve this problem?
]]>I just updated the plugin to version 2.0 and after going to Tools -> Debug Events I got the following error:
Debug Events are Not Installed Correctly
The database table was not installed correctly. Please contact plugin support to diagnose and fix the issue. Provide them the error message below:
Unknown storage engine ‘InnoDB’
My server has disabled InnoDB as a storage engine for performance reasons (a VPS with a low amount of RAM) and this was the main reason I moved from “WP Mail SMTP” to your plugin.
I don’t particularly care about that debug events table but every page load in the admin area adds something like that in my php errors log and it drives me crazy (the other plugin had the same issue).
[16-Feb-2023 06:21:15 UTC] WordPress database error Unknown storage engine 'InnoDB' for query CREATE TABLE IF NOT EXISTS wp_easywpsmtp_debug_events
(
id
INT UNSIGNED NOT NULL AUTO_INCREMENT,
content
TEXT DEFAULT NULL,
initiator
TEXT DEFAULT NULL,
event_type
TINYINT UNSIGNED NOT NULL DEFAULT '0',
created_at
TIMESTAMP NOT NULL DEFAULT CURRENT_TIMESTAMP,
PRIMARY KEY (id)
)
ENGINE='InnoDB'
DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci; made by require_once('wp-admin/admin.php'), do_action('admin_init'), WP_Hook->do_action, WP_Hook->apply_filters, EasyWPSMTP\Migrations\Migrations->init, EasyWPSMTP\Migrations\MigrationAbstract->init, EasyWPSMTP\Migrations\MigrationAbstract->validate_db, EasyWPSMTP\Migrations\MigrationAbstract->run, EasyWPSMTP\Admin\DebugEvents\Migration->migrate_to_1
If this was just one site it would’ve been easy to just replace the plugin again and forget about it, but imagine how much of an annoyance that will be with tens of sites.
I’m also pretty sure that I’m not the only one who doesn’t use InnoDB, so please figure out a way to fix this.
]]>
Zend_Db_Statement_Exception thrown
WP DB Error: [1286] Unknown storage engine 'InnoDB' SQL: CREATE TABLE wp_matomo_user ( login VARCHAR(100) NOT NULL, password VARCHAR(255) NOT NULL, email VARCHAR(100) NOT NULL, twofactor_secret VARCHAR(40) NOT NULL DEFAULT '', superuser_access TINYINT(2) unsigned NOT NULL DEFAULT '0', date_registered TIMESTAMP NULL, ts_password_modified TIMESTAMP NULL, PRIMARY KEY(login) ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4
…and I was getting it every time I tried to access any WP-Admin page until I renamed the /wp-content/plugins/matomo
folder using FTP to force deactivate Matomo.
I think InnoDB should be noted as a requirement of this plugin (e.g. extend the FAQ item “Which MySQL versions are supported?”). The plugin should also check InnoDB availability before trying to create tables using it.
(Since I’ve already purchased a paid hosting plan, I will switch my DB to InnoDB to use Matomo. However, potential future users should be warned to avoid a bad user experience.)
]]>[06-Dec-2021 16:57:42 UTC] PHP Fatal error: Uncaught Error: Call to undefined function _wp_get_current_user() in /home4/ctbirdin/public_html/wp-includes/pluggable.php:70
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/pluggable.php(1072): wp_get_current_user()
#1 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(36): is_user_logged_in()
#2 [internal function]: wpo_cache('<!DOCTYPE html>...', 9)
#3 {main}
thrown in /home4/ctbirdin/public_html/wp-includes/pluggable.php on line 70
[06-Dec-2021 17:29:16 UTC] PHP Fatal error: Uncaught Error: Call to undefined function wp_cache_get() in /home4/ctbirdin/public_html/wp-includes/option.php:143
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/l10n.php(63): get_option('WPLANG')
#1 /home4/ctbirdin/public_html/wp-includes/l10n.php(137): get_locale()
#2 /home4/ctbirdin/public_html/wp-includes/l10n.php(1278): determine_locale()
#3 /home4/ctbirdin/public_html/wp-includes/l10n.php(1240): _get_path_to_translation_from_lang_dir('wp-optimize')
#4 /home4/ctbirdin/public_html/wp-includes/l10n.php(1210): _get_path_to_translation('wp-optimize')
#5 /home4/ctbirdin/public_html/wp-includes/l10n.php(1308): _load_textdomain_just_in_time('wp-optimize')
#6 /home4/ctbirdin/public_html/wp-includes/l10n.php(177): get_translations_for_domain('wp-optimize')
#7 /home4/ctbirdin/public_html/wp-includes/l10n.php(289): translate('Output is too s...', 'wp-optimize')
#8 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(32): __('Output is too s...', 'wp- in /home4/ctbirdin/public_html/wp-includes/option.php on line 143
[06-Dec-2021 17:59:16 UTC] PHP Fatal error: Uncaught Error: Call to undefined function wp_cache_get() in /home4/ctbirdin/public_html/wp-includes/option.php:143
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/l10n.php(63): get_option('WPLANG')
#1 /home4/ctbirdin/public_html/wp-includes/l10n.php(137): get_locale()
#2 /home4/ctbirdin/public_html/wp-includes/l10n.php(1278): determine_locale()
#3 /home4/ctbirdin/public_html/wp-includes/l10n.php(1240): _get_path_to_translation_from_lang_dir('wp-optimize')
#4 /home4/ctbirdin/public_html/wp-includes/l10n.php(1210): _get_path_to_translation('wp-optimize')
#5 /home4/ctbirdin/public_html/wp-includes/l10n.php(1308): _load_textdomain_just_in_time('wp-optimize')
#6 /home4/ctbirdin/public_html/wp-includes/l10n.php(177): get_translations_for_domain('wp-optimize')
#7 /home4/ctbirdin/public_html/wp-includes/l10n.php(289): translate('Output is too s...', 'wp-optimize')
#8 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(32): __('Output is too s...', 'wp- in /home4/ctbirdin/public_html/wp-includes/option.php on line 143
[06-Dec-2021 19:10:57 UTC] PHP Fatal error: Uncaught Error: Call to undefined function wp_cache_get() in /home4/ctbirdin/public_html/wp-includes/option.php:143
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/l10n.php(63): get_option('WPLANG')
#1 /home4/ctbirdin/public_html/wp-includes/l10n.php(137): get_locale()
#2 /home4/ctbirdin/public_html/wp-includes/l10n.php(1278): determine_locale()
#3 /home4/ctbirdin/public_html/wp-includes/l10n.php(1240): _get_path_to_translation_from_lang_dir('wp-optimize')
#4 /home4/ctbirdin/public_html/wp-includes/l10n.php(1210): _get_path_to_translation('wp-optimize')
#5 /home4/ctbirdin/public_html/wp-includes/l10n.php(1308): _load_textdomain_just_in_time('wp-optimize')
#6 /home4/ctbirdin/public_html/wp-includes/l10n.php(177): get_translations_for_domain('wp-optimize')
#7 /home4/ctbirdin/public_html/wp-includes/l10n.php(289): translate('Output is too s...', 'wp-optimize')
#8 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(32): __('Output is too s...', 'wp- in /home4/ctbirdin/public_html/wp-includes/option.php on line 143
[06-Dec-2021 19:11:00 UTC] PHP Fatal error: Uncaught Error: Call to undefined function wp_cache_get() in /home4/ctbirdin/public_html/wp-includes/option.php:143
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/l10n.php(63): get_option('WPLANG')
#1 /home4/ctbirdin/public_html/wp-includes/l10n.php(137): get_locale()
#2 /home4/ctbirdin/public_html/wp-includes/l10n.php(1278): determine_locale()
#3 /home4/ctbirdin/public_html/wp-includes/l10n.php(1240): _get_path_to_translation_from_lang_dir('wp-optimize')
#4 /home4/ctbirdin/public_html/wp-includes/l10n.php(1210): _get_path_to_translation('wp-optimize')
#5 /home4/ctbirdin/public_html/wp-includes/l10n.php(1308): _load_textdomain_just_in_time('wp-optimize')
#6 /home4/ctbirdin/public_html/wp-includes/l10n.php(177): get_translations_for_domain('wp-optimize')
#7 /home4/ctbirdin/public_html/wp-includes/l10n.php(289): translate('Output is too s...', 'wp-optimize')
#8 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(32): __('Output is too s...', 'wp- in /home4/ctbirdin/public_html/wp-includes/option.php on line 143
[06-Dec-2021 19:14:47 UTC] PHP Fatal error: Uncaught Error: Call to undefined function _wp_get_current_user() in /home4/ctbirdin/public_html/wp-includes/pluggable.php:70
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/pluggable.php(1072): wp_get_current_user()
#1 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(36): is_user_logged_in()
#2 [internal function]: wpo_cache('<!DOCTYPE html>...', 9)
#3 {main}
thrown in /home4/ctbirdin/public_html/wp-includes/pluggable.php on line 70
[06-Dec-2021 19:16:55 UTC] PHP Fatal error: Uncaught Error: Call to undefined function wp_cache_get() in /home4/ctbirdin/public_html/wp-includes/option.php:143
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/l10n.php(63): get_option('WPLANG')
#1 /home4/ctbirdin/public_html/wp-includes/l10n.php(137): get_locale()
#2 /home4/ctbirdin/public_html/wp-includes/l10n.php(1278): determine_locale()
#3 /home4/ctbirdin/public_html/wp-includes/l10n.php(1240): _get_path_to_translation_from_lang_dir('wp-optimize')
#4 /home4/ctbirdin/public_html/wp-includes/l10n.php(1210): _get_path_to_translation('wp-optimize')
#5 /home4/ctbirdin/public_html/wp-includes/l10n.php(1308): _load_textdomain_just_in_time('wp-optimize')
#6 /home4/ctbirdin/public_html/wp-includes/l10n.php(177): get_translations_for_domain('wp-optimize')
#7 /home4/ctbirdin/public_html/wp-includes/l10n.php(289): translate('Output is too s...', 'wp-optimize')
#8 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(32): __('Output is too s...', 'wp- in /home4/ctbirdin/public_html/wp-includes/option.php on line 143
]]>Should I do this? What are the advantages and why is this question asked please?
]]>