Aaron Barraza

Weird.. I was not able to replicate on a blank site on this second round. But nevermind.

The jobfeature_settings_options option (in wp_options table) was corrupted. Using PHP 7.4 I went to Job Board → Settings → Job Features and clicked on Save Changes. Then I updated to PHP 8 and everything was working fine.

Note that as I mentioned before, this only was having issues while on PHP 8.0 and with the Modern Layout enabled. That’s caused because the PHP fatal error was occurring inside a conditional that checks if the v2 layout was active.

I’m curious, did the format of the jobfeature_settings_options option change? See how big is the difference between the options before and after I re-saved the settings (I didn’t change any configuration). Obviosly this was saved as JSON, but I formated it with print_r( maybe_unserialize() ) to make it more readable. So, here’s the diff:

Hopefully this information can be useful.

Thank you again for your support!

Hello @wpmudev-support2

It worked like a charm! Thank you!

I just had to replace the update_field() function with update_post_meta() as we are not using ACF on this site and that caused a PHP fatal error.

Thank you!

Hello!

The error is still in the plugin. The fix from @theschappy is correct, but it was wrongly implemented.

If you see carefully, at the beggining of the lines he has some – (meaning this line should be removed) and + (meaning that line should be added).

So, the intention was to replace this:

$filestr = @fread($f , filesize($file));
if (strpos($filestr , $marker_name) === false)
{
		insert_with_markers( $file,  $marker_name,  $content );
}

with this:

if ($f !== false) {
		$filestr = @fread($f , filesize($file));
		if (strpos($filestr , $marker_name) === false)
		{
				insert_with_markers( $file,  $marker_name,  $content );
		}
}

Or in simple words, wrap the original code inside the if ($f !== false) { } conditional.

@osamaesh Is it possible to make this change public? Because what was implemented was to duplicate the code lol:

$f = @fopen( $file, 'r+' );
                       $filestr = @fread($f , filesize($file));
                       if (strpos($filestr , $marker_name) === false)
                        {
                                insert_with_markers( $file,  $marker_name,  $content );
                        }
                       if ($f !== false) {
                               $filestr = @fread($f , filesize($file));
                               if (strpos($filestr , $marker_name) === false)
                                {
                                        insert_with_markers( $file,  $marker_name,  $content );
                                }
                       }

And the problem with duplicating the code, is that before the validation, the fread() is called, and on the scenarios where $f is false, that causes the php fatal error.

Thank you all!

• This reply was modified 1 year, 11 months ago by Aaron Barraza. Reason: Added additional information

@mfeijoo For any plugin here in the WordPress Plugins, in the right sidebar you will see: “version, last updated, active installations… etc.” Below that there is an “Advanced view” link. Enter to that link and scroll to the very bottom of the page, there is a dropdown with all the versions from that plugin.

We are having the same issue and figure out that the issue starts appearing in version 2.6.19 of PowerPack. So @mfeijoo try downgrading PowerPack to 2.6.18, that temporary solved the issue for us.

Any plugin author that can take a look into this? Looks like the issue is in /modules/display-conditions/module.php on line 443 when the following line of code was changed from:

‘fields’ => $this->_conditions_repeater->get_controls(),

to:

‘fields’ => array_values( $this->_conditions_repeater->get_controls() ),

We are having the same issue. Can you make public the solution please?

Thanks for your reply Nadir.

experimental__woocommerce_blocks-cart-remove-item is useful, but that’s fired at the beggining of the remove item process, before the AJAX call is made. It would be really helpful if you could add an event after the AJAX call is done. Do you think that’s possible on a future version?