WPIntell

Source evidence

incorrect charset used when creating logs table

Optimize Database after Deleting Revisions · support · 2025-10-21T07:42:00+00:00

complaintsentiment
highseverity
0.97relevance
0replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 31 rows with source links

12.9% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

27 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
copytrans unresolved
In the plugin source code, when creating the logs table, the charset used for the wp_odb_logs is utf8 which in the latest versions of mariadb corresponds to utf8mb3 . wordpress uses utf8mb4 when available. You should update the code to use the charset and collation from the wpdb global object instead. $charset = $wpdb->charset; $collation = $wpdb->collation; $sql = " CREATE TABLE IF NOT EXISTS ' . $this->odb_logtable_name . ' ( odb_id int(11) NOT NULL AUTO_INCREMENT, odb_timestamp varchar(20) NOT NULL, odb_revisions int(11) NOT NULL, odb_trash int(11) NOT NULL, odb_spam int(11) NOT NULL, odb_tags int(11) NOT NULL, odb_transients int(11) NOT NULL, odb_pingbacks int(11) NOT NULL, odb_oembeds int(11) NOT NULL, odb_orphans int(11) NOT NULL, odb_tables int(11) NOT NULL, odb_before varchar(20) NOT NULL, odb_after varchar(20) NOT NULL, odb_savings varchar(20) NOT NULL, PRIMARY KEY ( odb_id ) ) CHARACTER SET {$charset} COLLATE {$collation} AUTO_INCREMENT=1; "; In addition, setting the AUTO_INCREMENT to 1 causes issues in instances where the database is load balanced, so that auto increment should be removed. Removing it has no consequences.

Comments

0 shown

No comments were stored for this source.