Error message after updating PRO

Support
#1

I’ve just updated Pro and have an error showing on the front end. These two…

Warning : preg_match() expects parameter 2 to be string, array given in /home/sunnyda3/public_html/fieldgateflowers.co.uk/wp-includes/class-wp-block-parser.php on line 417

Warning : strlen() expects parameter 1 to be string, array given in /home/sunnyda3/public_html/fieldgateflowers.co.uk/wp-includes/class-wp-block-parser.php on line 489

I’ve tried switching back to X and deleting the unused Cornerstone plugin, but the error remains.

Can you help?

1 Like
#2

I have also had the same error, no fix so far. I also disabled all plugins and deleted additional CSS/JS but no change. That was after I upgraded from Pro 3.2.3 to 4.1.2. I down graded back to 3.2.3 and the errors disappeared.

#3

Same on my end after 4.1.1 to 4.1.2 update:
Warning : strlen() expects parameter 1 to be string, array given in … /public_html/wp-includes/class-wp-block-parser.php on line 489
Warning : preg_match() expects parameter 2 to be string, array given in /public_html/wp-includes/class-wp-block-parser.php on line 417

#4

Same here after update to 4.1.2 Pro theme.

Capture d’écran 2021-01-28 à 15.27.39
Capture d’écran 2021-01-28 à 15.27.392880×320 79.9 KB

#5

How do you downgrade?

#6

Hi everyone,

In wp-config.php you can disabled WP_DEBUG by setting it to false instead of true

define( 'WP_DEBUG', false );

That will stop the errors from outputting. We are looking into what is triggering the warning, but PHP warnings and notice messages can always be avoided in production sites by not leaving WP_DEBUG turned on after using it to troubleshoot issues. If you ever need to troubleshoot a production site there is a way that allows capturing the error output without showing it to users:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_DISPLAY', false );
define( 'WP_DEBUG_LOG', true );
#7

I already have it set to FALSE.

Still getting the error on the front end.

#8

Hi @Lorenmn,

It could be that your PHP configuration is overriding that somewhere. Would you mind if I logged into your site to take a closer look? If this is ok you can add login credentials in a secure note. I’ve actually not been able to reproduce this problem yet but I’ve narrowed it down to a few possibilities. Getting to see how your page is setup would help me find a solution faster. Thanks!

#10

I have updated a different site I manage and I don’t have the same issue. It’s running Wordpress 5.5 not 5.6, that seems to be where the conflict is.

Still no idea how to resolve it.

#11

Do you use a child theme on your site for any custom edits you’ve made? You can upload a previous version of the Pro Theme but there are a couple of steps you need to take first.

  1. Backup site (use a backup plugin)
  2. Go to Pro -> Vaildation -> Export button on Theme Options Manager to download the Theme settings (a .json file)
  3. Activate a different theme.
  4. Delete the current Pro theme you have installed.
  5. Upload the older Stable Release 3.2.3 version of Pro.
  6. Activate it, if your site looks the same (and without the errors) you have successfully downgraded. If things look a little different you will need to upload the Settings file you downloaded in step 2 on the Validation page.

I miss anything @alexander?

#14

Hi.
Here’s the website login details.
Thanks.

#15

Hey @Lorenmn,

A few moments ago, @Alexander, our lead developer has released an update. Could you please update to the latest versions?
Our latest versions are:

  • Pro theme 4.1.3

This latest release contains fixes for several issues so be sure to check out the changelog:

After doing the updates, always remember to clear all caches (if you are using WP Rocket, WP SuperCache or W3 Total Cache) when updating so that the code from the latest release is always in use. This will help you to avoid any potential errors.

Please let us know how it goes.

#16

I have just updated my site from Pro 3.2.3 to 4.1.3 and I have no errors, no issues so far!

Can’t wait to get some loopers implemented!

#17

Glad to hear that, @bluestack

#18

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.