Version 5.11.5 and Database errors

  • Resolved dbyolton

    (@dbyolton)


    5 years, 10 months ago

    Having issues with the latest MEC Lite update, 5.11.5. It works fine on my live site, but when I have it on my desktop staging site in debug mode, I see lots of errors.

    After the upgrade, I first see:
    WordPress database error:[Specified key was too long max key length is 767 bytes]
    ALTER TABLE ‘wp_mec_users’ ADD PRIMARY KEY (‘id’), AND UNIQUE KEY ’email’ (’email’);

    WordPress database error: [Incorrect table definition; there can only be one auto column and it must be defined as a key]
    ALTER TABLE ‘wp_mec_users’ MODIFY ‘id’ int NOT NULL AUTO_INCREMENT;

    in the upper left hand corner of the site.

    then lots of junk with each shortcut.

    I’m an Elementor users, which is having it’s own problems, but I don’t think this is related.

    Looking for similar problems, there was a mention of database unicode methods, but I haven’t changed anything but MEC lite.

    == Server Environment ==
    Operating System: Darwin
    Software: Apache/2.4.37 (Unix) OpenSSL/1.0.2q PHP/7.3.1 mod_perl/2.0.8-dev Perl/v5.16.3
    MySQL version: Source distribution v5.6.41-84.1
    PHP Version: 7.3.1
    PHP Max Input Vars: 1000
    PHP Max Post Size: 512M
    GD Installed: Yes
    ZIP Installed: Yes
    Write Permissions: All right
    Elementor Library: Connected

    == WordPress Environment ==
    Version: 5.5.1
    Site URL: https://www.august30.dev.cc
    Home URL: https://www.august30.dev.cc
    WP Multisite: No
    Max Upload Size: 512 MB
    Memory limit: 1024M
    Permalink Structure: /%postname%/
    Language: en-US
    Timezone: America/New_York
    Debug Mode: Active

    == Theme ==
    Name: Sydney Pro Child
    Version: 1.0
    Author: aThemes
    Child Theme: Yes
    Parent Theme Name: Sydney Pro
    Parent Theme Version: 2.0.22
    Parent Theme Author: aThemes

    == User ==
    Role: administrator
    WP Profile lang: en_US
    User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.2 Safari/605.1.15

    == Active Plugins ==
    Analytify – Google Analytics Dashboard
    Version: 3.1.4
    Author: Analytify

    Analytify Email Notifications
    Version: 1.3.1
    Author: Adnan

    Analytify Pro
    Version: 2.2.1
    Author: WPBrigade

    Elementor
    Version: 3.0.3
    Author: Elementor.com

    Elementor Pro
    Version: 3.0.1
    Author: Elementor.com

    Header and Footer Scripts
    Version: 2.2.1
    Author: Digital Liberation

    Modern Events Calendar Lite
    Version: 5.11.5
    Author: Webnus

    Redirection
    Version: 4.8
    Author: John Godley

    Simple Yearly Archive
    Version: 2.1.2
    Author: Oliver Schlöbe

    Smash Balloon Instagram Feed
    Version: 2.4.6
    Author: Smash Balloon

    Yoast SEO
    Version: 14.8.1
    Author: Team Yoast

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter dbyolton

    (@dbyolton)

    5 years, 9 months ago

    Solved. I had needed to modify the render.php for the lists view to remove the excerpt ellipsis. (I wish this was configurable in the UI.)

    The file was under my child theme, and the 5.11.5 updated needed me to copy the current render.php over from the plugin to the child theme location, and have the ellipsis removed on the new file.

    bjf2000

    (@bjf2000)

    5 years, 9 months ago

    Based on a timestamp in a log, this might have begun with 5.11.0 on Sep 2.

    We also use Elementor but hadn’t updated to the problematic v3 at the time of the errors.

    Since I wouldn’t have any idea what to do with render.php and am unclear what it’s doing in your child theme (btw, we didn’t even have a child theme when this problem started), I’ll not go down that path to try to solve this.

    Probably two of us posting about it will be enough to get them to fix it themselves in an upcoming version.

    Plugin Contributor webnus

    (@webnus)

    5 years, 9 months ago

    Hi All,

    Sorry for the delay in response and thank you for notifying us,

    There is nothing to worry about., we are aware of the issue and we are working on it,

    Best Regards

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Version 5.11.5 and Database errors’ is closed to new replies.