PHP conflict with WP Estimation Form?

[ULinn]

Hi there,

after Upgrading PHP from 7.2 FPM to 7.3 FPM the WP-Estimation form causes a 500 error after confirming the last step (POST to admin-ajax.php):

[01-Oct-2020 10:06:22 UTC] PHP Warning: preg_split(): Compilation failed: invalid range in character class at offset 4 in /html/wordpress/wp-content/plugins/WP_Estimation_Form/includes/dompdf/include/text_frame_reflower.cls.php on line 89

[01-Oct-2020 10:06:22 UTC] PHP Warning: count(): Parameter must be an array or an object that implements Countable in /html/wordpress/wp-content/plugins/WP_Estimation_Form/includes/dompdf/include/text_frame_reflower.cls.php on line 90

The error is written again and again, several millions of entrys within a few minutes.

After downgrading again to WP 7.2 everything works fine again.

What do I have to do, to use WP Estimation Form with PHP 7.3 or higher?

Best regards

Uli

[christian]

Hey Uli,

Regretfully, the only thing you can do for now is staying on PHP 7.2 while the devs of WP Estimation investigate the case and hopefully release a fix in the next version of the plugin.

Please also copy your live site to a staging server and give us the following details in a Secure Note so we could replicate your setup and we’ll have more details to report.

• Name of the form if it’s happening only on 1 form
• Staging WordPress Login URL
• Admin username and password

You can find the Secure Note button at the bottom of your posts.

Thank you for understanding.

[ULinn]

Staging is now ready, see Secure Note.

[marc_a]

Hi Uli,

Thanks for sharing your credentials.

Since you switch it back to PHP 7.2, we can’t replicate the issue in your staging area that you are facing to. Then I tried to replicate the issue on my dev website to check if the error due to the PHP upgrade from 7.2 to 7.3. I export the E&P form builder and import it to my dev website but I couldn’t replicate the issue you are facing to.

I guess it was a plugin conflict that causing the ajax error then I recommend you upgrade your PHP version again to 7.3 and do the plugin conflict.
TESTING FOR PLUGIN CONFLICT

Regarding the warning, your WP_DEBUG is set to true and it should be set to false because WP_DEBUG is just intended for PHP Debugging and Developers. To do that, you need to use FTP or CPanel and access your file manager then go to the root directly. After locating the root directory, you need to find the wp-config.php file and edit it. Then inside the file find the WP_DEBUG and set it to false.

See the secure note for more details.

Hope that helps and let us know how it goes.

Thank you.

[ULinn]

Hi cramaton, thank you for your help.

I don’t think my WP_DEBUG is set to true, in my wp-config.php line 78 is:

define('WP_DEBUG', false);

Can the debugging have been set to true anywhere else?

Unfortunately, the staging and the live environment are on the same shared hosting, so I can’t switch PHP version for only one of them. And I don’t want the live environment to stop working again. So I’ll have to find a way to reproduce the error …

Uli

[tristup]

Hi Uli,

There is no other place to set the debugging true in WordPress. As there is no option to replicate the error you are having, you can try once by updating the PHP version to 7.3 in your server once again,
and add the below-given code into your wp-config.php for debug setup, which will log the error into the file name debug.log inside the wp-content folder.
And send us the error logged into the file name debug.log inside the wp-content folder to check the logged error, before degrading the PHP version to 7.2 again. It may help us to recognize the issue from the debug.log file.

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );

// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
//SET PHP INI DISPLAY ERROR FALSE
@ini_set( 'display_errors', 0 );

Please find the video will help you to edit wp-config.php and add the above code: https://www.youtube.com/watch?v=3SDPTafEM8o

Thanks