Issue with 3.4.28 upgrade

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.

Same issue here.

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

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?

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.

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

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();

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

Yeah, seeing this on several sites too…. ??

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?

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

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

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

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