• Resolved ashokdesai

    (@ashokdesai)


    After updating to latest version of wordpress gutenberg block of plugin is not working. Getting this error “Your site doesn’t include support for the e-Learning block. You can try installing the block or remove it entirely.”

Viewing 8 replies - 1 through 8 (of 8 total)
  • Hello
    I have exactly the same error. Have you found a solution?

    Thread Starter ashokdesai

    (@ashokdesai)

    Not Yet

    We managed to find the source of the problem.

    You need to include the following JS file in: insert-or-embed-articulate-content-into-wordpress > gutenberg> gutenberg.php

    ??https://cdnjs.cloudflare.com/ajax/libs/regenerator-runtime/0.13.7/runtime.min.js??

    Thread Starter ashokdesai

    (@ashokdesai)

    Thank you very much @niconokaa

    Should I insert this script inside the Gutenberg.php file? Is there a specific point in the code where I should insert it? I inserted it at the beginning and the site encountered problems.

    @matheussilva08 added like this, added surrounding code for context. Can confirm it’s working on my side.

    <?php
    const BLOCKJS = 'gutenberg/build/block.js';
    const BLOCKCSS = 'gutenberg/build/block.css';

    function articulate_enqueue_gutenberg_scripts() {
    wp_enqueue_script( 'jquery' );

    wp_enqueue_script( 'materializejs', WP_QUIZ_EMBEDER_PLUGIN_URL . MATERIALIZEJS, array( 'jquery', 'jquery-ui-core', 'jquery-ui-tooltip' ) );

    // Enqueue the regenerator-runtime library from CDN
    wp_enqueue_script( 'regenerator-runtime', 'https://cdnjs.cloudflare.com/ajax/libs/regenerator-runtime/0.13.7/runtime.min.js', array(), '0.13.7', true );

    wp_enqueue_script( 'articulate-gutenberg-block', WP_QUIZ_EMBEDER_PLUGIN_URL . BLOCKJS, array( 'wp-api', 'wp-i18n', 'wp-blocks', 'wp-components', 'wp-compose', 'wp-data', 'wp-editor', 'wp-element', 'regenerator-runtime' ), filemtime( WP_QUIZ_EMBEDER_PLUGIN_DIR . '/gutenberg/build/block.js' ), true );

    @enoteware It worked perfectly! Thank you very much for your help!

    This issue appears to be fixed in WordPress 6.7 and shouldn’t require the workaround above. Let me know if you have any other issues.

Viewing 8 replies - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.