Saad T.

Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Forum: Plugins
    In reply to: [WooCommerce Blocks] Undefined array key 1 in BlockTemplatesController.php
    Plugin Contributor Saad T.

    (@saadtarhi)

    2 years, 10 months ago

    Thanks for your thorough feedback, @lockoloop! While identifying the exact issue without a consistent way to reproduce it is tricky, we’ll make an effort to address the “Undefined array key 1” error. Hopefully, this will resolve it in this specific scenario. As for the Jetpack-related issue, could you guide us through the steps you took when you encountered it?

    Forum: Plugins
    In reply to: [WooCommerce Blocks] Undefined array key 1 in BlockTemplatesController.php
    Plugin Contributor Saad T.

    (@saadtarhi)

    2 years, 11 months ago

    Hi @lockoloop! Thanks for getting in touch!

    The function get_block_template_fallback is linked to the pre_get_block_template filter hook. It gets activated when WordPress attempts to retrieve a block template. Many plugins and themes, like the Twenty Twenty-Three , have block templates. For instance, its page template activates when you open a page in the admin area. If you remember which page displayed this error, try reloading it. If the error reappears, then to identify the problematic template (from a plugin/theme), you can:

    1. Briefly switch to the Storefront or Twenty Twenty-Three theme.
    2. Deactivate all plugins, keeping only WooCommerce active.
    3. Retake the action that triggered the issue.

    If the problem disappears after these steps, it indicates a conflict with one of the deactivated plugins or themes. To pin down the culprit, reactivate your plugins one by one and test after each. This process will help identify the conflicting plugin. For a step-by-step guide on performing a conflict test, click here.

    Forum: Plugins
    In reply to: [WooCommerce] Missing block titles
    Plugin Contributor Saad T.

    (@saadtarhi)

    3 years, 7 months ago

    Hello @kubiq! 👋

    Thank you for reporting this bug! Our Blocks are registered on the server-side in addition to the client-side registration as recommended by Gutenberg and to apply some dynamic changes to our metadata. WordPress (or Gutenberg) prepare and send server-registered blocks to a specific set of WP core pages (i.e., post.php, site-editor.php, widgets-form-blocks.php) using the function get_block_editor_server_block_settings (For example, see this line). In this instance, the Gutenberg Block Manager plugin is displayed on the wp-admin/options-general.php, which isn’t included in the previously mentioned WP core pages. Hence, this plugin isn’t getting any back-end data about the blocks.

    So, it isn’t only an issue of missing titles; any other modification to the metadata done on the back end is also lost for this Plugin!

    A potential solution for the author is to add a similar line of code used in WP somewhere in his plugin to get the back-end metadata.

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