• Resolved jimithing007

    (@jimithing007)


    Hello,

    When I upgrade to 3.4.28 I get the below error at the top of the screen when in the WP Admin dashboard. There’s also a similar error visible on the webpage. I’m currently rolled back to the previous version. Here’s what I see in the WP Admin dashboard:
    homepages/11/d341550515/htdocs/unamilighting/wp-content/plugins/ninja-forms/blocks/form/block.json): failed to open stream: No such file or directory in /homepages/11/d341550515/htdocs/unamilighting/wp-content/plugins/ninja-forms/blocks/bootstrap.php on line 12

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/11/d341550515/htdocs/unamilighting/wp-content/plugins/ninja-forms/blocks/bootstrap.php:12) in /homepages/11/d341550515/htdocs/unamilighting/wp-includes/functions.php on line 6270

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/11/d341550515/htdocs/unamilighting/wp-content/plugins/ninja-forms/blocks/bootstrap.php:12) in /homepages/11/d341550515/htdocs/unamilighting/wp-admin/includes/misc.php on line 1310

    Warning: Cannot modify header information – headers already sent by (output started at /homepages/11/d341550515/htdocs/unamilighting/wp-content/plugins/ninja-forms/blocks/bootstrap.php:12) in /homepages/11/d341550515/htdocs/unamilighting/wp-admin/admin-header.php

    The page I need help with: [log in to see the link]

Viewing 15 replies - 1 through 15 (of 29 total)
  • I have the same problem. I tried commenting out line 12 in bootstrap.php, but then another error occurs at line 29:

    Warning: array_merge(): Expected parameter 1 to be an array, null given in wp-content/plugins/ninja-forms/blocks/bootstrap.php on line 29

    It looks as though the directory /ninjaforms/blocks/form doesn’t exist and is what’s causing the error.

    David

    (@dkomando)

    Same issue here.

    Looks like QA/QC dept. needs to install the WP plugin ‘Query Monitor’ before pushing updates live.

    morgykat

    (@morgykat)

    Same issue here.
    What’s the solution to this, roll back to previous version?
    Sorry if this is a daft question, but how do you actually do that, there doesn’t seem to be an option on the backend?

    Jason

    (@greenhome)

    This is a huge issue because once I logged out of admin, the error was stopping execution so I couldn’t log back in to roll back the plugin.

    In my case, it was complaining about a missing .json file.

    I ended up going into file manager in CPanel, created a “form” directory and created an empty .json file:

    /wp-content/plugins/ninja-forms/blocks/form/block.json

    I don’t know if this will fix the problem for everyone, but it fixed it for me.

    willemb2

    (@willemb2)

    We’re getting the first error the OP reported above *all* pages:

    Warning: file_get_contents(***/wp-content/plugins/ninja-forms/blocks/form/block.json): failed to open stream: No such file or directory in /home/lvbhb/public_html/wp-content/plugins/ninja-forms/blocks/bootstrap.php on line 12

    David

    (@dkomando)

    I changed line 12 to this and the error is gone.

       $block = ( file_exists ( __DIR__ . '/form/block.json' )  ) ? (array)json_decode(file_get_contents(__DIR__ . '/form/block.json'), true) : array();
    
    willemb2

    (@willemb2)

    Hello @dkomando, for us less PHP savvy creatures, could you explain what that change is doing?

    WPMuse

    (@wpmuse)

    Yeah, seeing this on several sites too…. 🙁

    tinpeas

    (@tinpeas)

    Yep, this update has broken all my sites that use Ninja Forms, NOT GOOD!!

    Jason (@greenhome) the fake file creation worked for removing the error messages. How’s the functionality for you now?

    tinpeas

    (@tinpeas)

    I am rolling back as we speak, this needs fixing ASAP.

    WPMuse

    (@wpmuse)

    3.4.29 is out and seems to have corrected the issue. 😉

    willemb2

    (@willemb2)

    Yes, 3.4.29 fixed the problem for us too. Thanks, Ninja team.

    jimithing007

    (@jimithing007)

    I have also updated all of my sites to 3.4.29, and that seems to have fixed the issue for me

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