PHP Notice: Trying to access array offset on value of type bool in formidable

  • Resolved sinapars

    (@sinapars)


    5 months, 2 weeks ago

    Hi Team,

    in the last Version 6.14.1 i am get this error on debug.log File

    [02-Oct-2024 11:11:38 UTC] PHP Notice:  Trying to access array offset on value of type bool in /wp-content/plugins/formidable/classes/controllers/FrmSimpleBlocksController.php on line 55
    [02-Oct-2024 11:11:38 UTC] PHP Stack trace:
    [02-Oct-2024 11:11:38 UTC] PHP   1. {main}() /wp-admin/post.php:0
    [02-Oct-2024 11:11:38 UTC] PHP   2. require() /wp-admin/post.php:187
    [02-Oct-2024 11:11:38 UTC] PHP   3. do_action($hook_name = 'enqueue_block_editor_assets') /wp-admin/edit-form-blocks.php:272
    [02-Oct-2024 11:11:38 UTC] PHP   4. WP_Hook->do_action($args = [0 => '']) /wp-includes/plugin.php:517
    [02-Oct-2024 11:11:38 UTC] PHP   5. WP_Hook->apply_filters($value = '', $args = [0 => '']) /wp-includes/class-wp-hook.php:348
    [02-Oct-2024 11:11:38 UTC] PHP   6. FrmSimpleBlocksController::block_editor_assets('') /wp-includes/class-wp-hook.php:324
    [02-Oct-2024 11:11:38 UTC] PHP Notice:  Trying to access array offset on value of type null in /wp-content/plugins/formidable/classes/controllers/FrmSimpleBlocksController.php on line 55
    [02-Oct-2024 11:11:38 UTC] PHP Stack trace:
    [02-Oct-2024 11:11:38 UTC] PHP   1. {main}() /wp-admin/post.php:0
    [02-Oct-2024 11:11:38 UTC] PHP   2. require() /wp-admin/post.php:187
    [02-Oct-2024 11:11:38 UTC] PHP   3. do_action($hook_name = 'enqueue_block_editor_assets') /wp-admin/edit-form-blocks.php:272
    [02-Oct-2024 11:11:38 UTC] PHP   4. WP_Hook->do_action($args = [0 => '']) /wp-includes/plugin.php:517
    [02-Oct-2024 11:11:38 UTC] PHP   5. WP_Hook->apply_filters($value = '', $args = [0 => '']) /wp-includes/class-wp-hook.php:348
    [02-Oct-2024 11:11:38 UTC] PHP   6. FrmSimpleBlocksController::block_editor_assets('') /wp-includes/class-wp-hook.php:324

    BR

Viewing 1 replies (of 1 total)
  • Plugin Support Njones35

    (@njones35)

    Hi @sinapars,

    Thank you for reporting this.

    Our developers have taken a look and confirmed that its safe to ignore this warning for now – but they will be introducing a check in the next release to prevent this error from coming up.

    Best,
    Nathanael.

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