Plugin could not be activated

  • Resolved jlapitan

    (@jlapitan)


    4 years, 1 month ago

    Tried to test the latest version of the plugin(v2.8) and I can’t activate, it returns the error below

    Fatal error: Uncaught Error: Class ‘WP_Block_Supports’ not found in /var/www/wpfolderOnMySite/wp-content/plugins/coblocks/src/components/gutter-control/gutter-wrapper.php:91 Stack trace: #0 /var/www/wpfolderOnMySite/wp-content/plugins/coblocks/class-coblocks.php(123): require_once() #1 /var/www/wpfolderOnMySite/wp-content/plugins/coblocks/class-coblocks.php(64): CoBlocks->includes() #2 /var/www/wpfolderOnMySite/wp-content/plugins/coblocks/class-coblocks.php(214): CoBlocks::instance() #3 /var/www/wpfolderOnMySite/wp-content/plugins/coblocks/class-coblocks.php(221): coblocks() #4 /var/www/wpfolderOnMySite/wp-admin/includes/plugin.php(2297): include(‘/var/www/actual…’) #5 /var/www/wpfolderOnMySite/wp-admin/plugins.php(191): plugin_sandbox_scrape(‘coblocks/class-…’) #6 {main} thrown in /var/www/wpfolderOnMySite/wp-content/plugins/coblocks/src/components/gutter-control/gutter-wrapper.php on line 91

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Milos Vlaisavljevic

    (@gdmilos)

    Hey @jlapitan,

    Thanks for reaching out!

    CoBlocks version 2.8.0 causes the mentioned error on WordPress prior to version 5.6.

    The latest plugin version works fine on WP 5.6 and 5.6.1 so I highly recommend you to update the core.

    I’ve just created a new issue on GitHub, please see:
    https://github.com/godaddy-wordpress/coblocks/issues/1827

    Hope the issue will be fixed soon! ??

    Kind Regards,
    Milos | GoDaddy

    Plugin Author Anthony Ledesma

    (@paranoia1906)

    Hi @jlapitan,

    Thank you for this report! CoBlocks 2.8.1 has just been released which will resolve this issue for you. We appreciate your help in reporting these errors. They help us to react quickly when something unexpected happens. Please do not hesitate to reach out again if something else comes up.

    Best regards,

    Anthony

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Plugin could not be activated’ is closed to new replies.