• Resolved onlineprecision

    (@onlineprecision)


    I receive the following fatal error when activating the plugin:

    Fatal error: Uncaught Migrate.php(259) : WpTesting_Migration_AddComputedVariablesTable – Error executing ‘query’ with: ALTER TABLE olp_t_computed_variables ADD CONSTRAINT olp_t_fk_computed_variable_test FOREIGN KEY (test_id) REFERENCES olp_posts(ID) ON DELETE CASCADE ON UPDATE CASCADE , ADD INDEX fk_computed_variable_test(test_id) , ADD UNIQUE INDEX uq_computed_variable_name_test(test_id, computed_variable_name) Reason: Specified key was too long; max key length is 767 bytes thrown in /home/stic4713/magnitude.nu/www/wordpress/wp-content/plugins/wp-testing/vendor/ruckusing/ruckusing-migrations/lib/Task/Db/Migrate.php on line 259

    What can I do to prevent this issue?

    With kind regards,

    Michael

Viewing 15 replies - 1 through 15 (of 16 total)
  • Plugin Contributor ustimenko

    (@ustimenko)

    Hi Michael!

    Can you run this query in your database and show us output?

    show create table olp_t_computed_variables;

    Plugin Contributor ustimenko

    (@ustimenko)

    Also run this query and show us the results:

    select @@version, @@innodb_version, @@innodb_large_prefix;

    Possible workaround is here: https://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_large_prefix

    vguerrero

    (@vguerrero)

    Same problem here, there is another option without change global MySQL server variables?

    Thanks!

    Plugin Contributor ustimenko

    (@ustimenko)

    @vguerrero can you tell your’s SQL results?

    show create table olp_t_computed_variables;
    select @@version, @@innodb_version, @@innodb_large_prefix;

    To solve the issue I need to repeat it. Currently I can’t repeat it locally.

    vguerrero

    (@vguerrero)

    Sure:

    1) show create table olp_t_computed_variables;

    #1146 – Table ‘atrevete_bd.olp_t_computed_variables’ doesn’t exists

    2) select @@version, @@innodb_version, @@innodb_large_prefix

    If you need more info, tell me!

    Regards

    • This reply was modified 9 years ago by vguerrero.
    Plugin Contributor ustimenko

    (@ustimenko)

    @vguerrero try them something like

    show tables like '%computed_variables';

    It will show you it with correct name.

    Your name could be like “wp_”?

    So something like show create table wp_t_computed_variables; could show more.

    Also run something like show variables; and send me to email [email protected] — I will try to download same DB version to repeat the issue.

    vguerrero

    (@vguerrero)

    Hi Alex,

    That did the trick, this is the info dumped when query show create table wp_t_computed_variables;

    Original size: 384

    I’m going to send you the show variables dump in some minutes by email.

    Regards

    • This reply was modified 9 years ago by vguerrero.
    Plugin Contributor ustimenko

    (@ustimenko)

    @vguerrero pls show the content of “Create Table” cell.

    vguerrero

    (@vguerrero)

    This is:

    Plugin Contributor ustimenko

    (@ustimenko)

    @vguerrero I see charset utf8mb4! May be it’s our issue cause. Anyway it helps more.

    vguerrero

    (@vguerrero)

    It’s the default charset when you add a new database from Plesk Panel, dude! :S

    Plugin Contributor ustimenko

    (@ustimenko)

    Pls upgrade to 0.20.1.

    I think I fixed the issue.

    Enis

    (@enistrevisi)

    Same problem here. The update did fix the issue 🙂

    • This reply was modified 9 years ago by Enis.
    Plugin Contributor ustimenko

    (@ustimenko)

    @enistrevisi did update fixed the issue? Sorry for incovinience ((

    Enis

    (@enistrevisi)

    Yes, it did 🙂

    Thank you!

Viewing 15 replies - 1 through 15 (of 16 total)

The topic ‘Fatal error when activating plugin’ is closed to new replies.