• Resolved Rafael Fischmann

    (@rfischmann)


    I’ve just installed WP Word Count for the first time, but can’t activate it because of a fatal error.

    Here’s my log:

    php[error] [30-Aug-2017 12:42:32 UTC] Erro de banco de dados do WordPress Unknown character set: 'iso88591' para a consulta CREATE TABLE wp_wpwc_posts (
    php[error] ??post_id bigint(20) NOT NULL,
    php[error] ??post_author bigint(20) NOT NULL,
    php[error] ??post_date datetime NOT NULL,
    php[error] ??post_status varchar(20) NOT NULL,
    php[error] ??post_modified datetime NOT NULL,
    php[error] ??post_parent bigint(20) NOT NULL,
    php[error] ??post_type varchar(20) NOT NULL,
    php[error] ??post_word_count bigint(20) NOT NULL,
    php[error] ??UNIQUE KEY post_id (post_id)
    php[error] ?) DEFAULT CHARACTER SET iso88591 COLLATE utf8 feita por activate_plugin, do_action('activate_wp-word-count/wpwordcount.php'), WP_Hook->do_action, WP_Hook->apply_filters, activate_wp_word_count, Wp_Word_Count_Activator::activate, wpwc_create_plugin_tables, dbDelta
    php[error] [30-Aug-2017 12:42:32 UTC] Erro de banco de dados do WordPress Table 'gopagoda.wp_wpwc_posts' doesn't exist para a consulta DELETE FROM wp_wpwc_posts feita por activate_plugin, do_action('activate_wp-word-count/wpwordcount.php'), WP_Hook->do_action, WP_Hook->apply_filters, activate_wp_word_count, Wp_Word_Count_Activator::activate, wpwc_populate_plugin_tables
    php[error] [30-Aug-2017 12:42:45 UTC] PHP Fatal error:  Allowed memory size of 859832320 bytes exhausted (tried to allocate 20480 bytes) in /data/wp-includes/wp-db.php on line 1841
    php[error] [30-Aug-2017 12:42:51 UTC] Erro de banco de dados do WordPress Unknown character set: 'iso88591' para a consulta CREATE TABLE wp_wpwc_posts (
    php[error] ??post_id bigint(20) NOT NULL,
    php[error] ??post_author bigint(20) NOT NULL,
    php[error] ??post_date datetime NOT NULL,
    php[error] ??post_status varchar(20) NOT NULL,
    php[error] ??post_modified datetime NOT NULL,
    php[error] ??post_parent bigint(20) NOT NULL,
    php[error] ??post_type varchar(20) NOT NULL,
    php[error] ??post_word_count bigint(20) NOT NULL,
    php[error] ??UNIQUE KEY post_id (post_id)
    php[error] ?) DEFAULT CHARACTER SET iso88591 COLLATE utf8 feita por do_action('activate_wp-word-count/wpwordcount.php'), WP_Hook->do_action, WP_Hook->apply_filters, activate_wp_word_count, Wp_Word_Count_Activator::activate, wpwc_create_plugin_tables, dbDelta
    php[error] [30-Aug-2017 12:42:51 UTC] Erro de banco de dados do WordPress Table 'gopagoda.wp_wpwc_posts' doesn't exist para a consulta DELETE FROM wp_wpwc_posts feita por do_action('activate_wp-word-count/wpwordcount.php'), WP_Hook->do_action, WP_Hook->apply_filters, activate_wp_word_count, Wp_Word_Count_Activator::activate, wpwc_populate_plugin_tables

    Any help?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Hey Rafael,

    Do you have other plugins that create their own database tables? If so, are those working correctly? WP Word Count makes its own table to store data and the character set and collation are pulled automatically with the built-in get_charset_collate() function provided by WordPress.

    So I’m not sure if it’s a hosting issue (out of date mySQL install, maybe?) or something else. This is the first I’ve heard of someone having such an issue with free or the Pro release.

    – Brian.

    Thread Starter Rafael Fischmann

    (@rfischmann)

    We have quite a few plugins installed and running that have their own database tables, yes. Never had such issue before.

    We’re running MySQL 5.6, I believe.

    When you get some time can you check your wp-config.php file and let me know what the values for these two variables are: DB_CHARSET & DB_COLLATE

    Thanks for your help tracking this down.

    Thread Starter Rafael Fischmann

    (@rfischmann)

    Sure, here you go:

    define('DB_CHARSET', 'iso88591');
    define('DB_COLLATE', 'utf8');

    I’m not sure what to make of that. Typically your wp-config should look “something” like this:

    define(‘DB_CHARSET’, ‘utf8’);
    define(‘DB_COLLATE’, ”);

    The DB_CHARSET can sometimes be a variation like ‘utf8mb4’ but I’m pretty sure that’s dependent on your host.

    Right now I don’t see anything in the plugin code that would create those database errors. WP Word Count, like I mentioned above, is just pulling those values from your wp-config.

    I’ll look into it more when I get some time this week but right now I’m at a loss.

    – Brian.

    Thread Starter Rafael Fischmann

    (@rfischmann)

    So good and bad news, Brian.

    I’ve looked into my database and noticed all the tables were already in utf8, so I felt free to change my wp-config.php file like you said and nothing broke.

    That fixed those errors we were seeing when trying to activate WP Word Count.

    However… I still can’t go through.

    Once again I’ve got a fatal error, but because of low memory. Then I resized my server (we run on the cloud), didn’t work:

    php[error] [31-Aug-2017 00:43:10 UTC] PHP Fatal error: Out of memory (allocated 1638637568) (tried to allocate 4096 bytes) in /data/wp-includes/wp-db.php on line 1841

    Then I resized it again, going for 8x the RAM we usually run on. Then I’ve got this:

    php[error] [31-Aug-2017 00:46:20 UTC] PHP Fatal error: Maximum execution time of 30 seconds exceeded in /data/wp-includes/taxonomy.php on line 738

    Does the plugin run its calculation/stats as soon as it’s activated?

    I believe the issue here is that our site is so huge. We’re getting close to 50,000 published posts, since 2006.

    You might be on the side of having too much content to process with the free version. Can you email me (support at linksoftwarellc.com) and I’ll help you out.

    – Brian.

    Same issue for me. 4,457 posts, all software up-to-date.

    Fatal error: Allowed memory size of 671088640 bytes exhausted (tried to allocate 20480 bytes) in /home/site/public/wp-includes/wp-db.php on line 1896

    @deltahf Would you mind emailing me (support at linksoftwarellc.com) and I can see about helping you out?

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Can’t activate plugin, fatal error’ is closed to new replies.