Problems after update to the new version

  • Resolved teufel100

    (@teufel100)


    3 years, 10 months ago

    Today I make the update for the plugin and after that, there are some problems with the plugin and my sites. So I activate the debug on 3 Blogs, and this is the output:

    Here some Debug-Infos from my Blog:

    WordPress-Datenbank-Fehler: [Specified key was too long; max key length is 767 bytes]
    CREATE TABLE wp_avatar_privacy_hashes ( identifier varchar(256) NOT NULL, hash char(64) NOT NULL, type varchar(20) NOT NULL, last_updated datetime DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP NOT NULL, PRIMARY KEY (hash, type), UNIQUE KEY identifier (identifier, type) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

    Notice: Undefined property: wpdb::$avatar_privacy_hashes in /var/__/wp-includes/wp-db.php on line 648
    WordPress-Datenbank-Fehler: [Incorrect table name ”]
    SELECT c.*, h.hash FROM wp_avatar_privacy c LEFT OUTER JOIN h ON c.email = h.identifier AND h.type = “comment” WHERE email =

    So, I had to deactivate the plugin now, but I hope, I can activate it again soon.

    (Sorry for my bad English)

    • This topic was modified 3 years, 10 months ago by teufel100.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author pepe

    (@pputzer)

    Hallo @teufel100, wir k?nnen auch auf Deutsch schreiben, wenn das leichter ist.

    Welches Datenbank-Backend verwendest Du? MySQL 5.6 oder 5.5? Ich fürchte, ich habe übersehen, da? MySQL < 5.7 nur 767 Bytes für Unique-Keys zul??t mit InnoDB.

    Thread Starter teufel100

    (@teufel100)

    Hallo Pepe,

    genau auf diese L?sung bin ich gerade auch gesto?en und habe jetzt Mal die MariaDB Version auf dem Server aktualisiert (10.4.17 jetzt), jetzt hoffe ich, dass das funktioniert. Vorher hatte ich noch die Version 10.1.xxx Version aktiv. Melde mich gleich noch einmal, ob das die L?sung ist.

    EDIT: Genau das war das Problem. Ich wei? nicht, ob das für alte Datenbankversionen noch gefixt werden kann, aber im Notfall wird es durch ein Update der Datenbank auf die aktuellste Version gel?st.

    • This reply was modified 3 years, 10 months ago by teufel100.
    Plugin Author pepe

    (@pputzer)

    For everyone else reading this thread: There is an incompatibility in the database definition with MySQL <5.7.7 and MariaDB <10.2.2. I’m investigating whether I can fix this in Avatar Privacy (without breaking anything else). In the meantime, upgrading to a more recent version of the database server would be the best option. (You can find other workarounds online to manually enable innodb_large_prefix in earlier versions, but I have not tested those and there might be side effects.)

    Plugin Author pepe

    (@pputzer)

    I’ve added a workaround (which could theoretically fail for very, very long URLs, but for now will have to do) to Avatar Privacy 2.4.1. Upgrading the DB server is still recommended, though.

    • This reply was modified 3 years, 10 months ago by pepe.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Problems after update to the new version’ is closed to new replies.