Skip Navigation

[Resolved] PHP warning is displayed on post edit screen after updating to WordPress 5.3.1.

This support ticket is created 5 years, 1 month ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 6 replies, has 2 voices.

Last updated by goM 5 years, 1 month ago.

Assisted by: Luo Yang.

Author
Posts
#1409633

goM

After updating to WordPress 5.3.1
When I open a screen to edit an existing post, a PHP warning appears at the top of the screen for a few seconds.This issue only occurs when opening an existing post edit screen. The front end is not affected.

Warning: preg_match() expects parameter 2 to be string, array given in /my-domain-path/public_html/my-sub-domain/wp-includes/class-wp-block-parser.php on line 417

Warning: strlen() expects parameter 1 to be string, array given in /my-domain-path/public_html/my-sub-domain/class-wp-block-parser.php on line 489

Warning: preg_match() expects parameter 2 to be string, array given in /my-domain-path/public_html/my-sub-domain/wp-includes/class-wp-block-parser.php on line 417

Warning: strlen() expects parameter 1 to be string, array given in /my-domain-path/public_html/my-sub-domain/wp-includes/class-wp-block-parser.php on line 489

I tried the following:
1.Changed theme to Twenty Twenty
2.Disable all plugins except Types and Views
But the error did not resolve.

Next, I tried the following.
1.Reverted theme to ASTRA currently in use.
2.Only the Types and Views plugins were disabled, and other plugins were enabled.
PHP warning no longer appears.

Next, I tried the following.
1.The state before the problem occurred (Astra theme and all plug-ins enabled)
2.Downgrade WordPress from 5.3.1 to 5.3
PHP warning no longer appears.

Other things I tried (but did not improve)
1.Local by Flywheel in PHP7.3.2 environment.
2.downgrade to Types3.3.7 and Views 3.0-b2

#1411199

Hello,

Thanks for the details, I can duplicate the same problem with the duplicator package you provided, this problem persists with Toolset Views plugin + 2020 theme.

And I tried these in another fresh WordPress 5.3.1 installation + Toolset Views plugin 3.0, create a new post with the same content of your post "DuplicatorでWordPressを本番と開発環境間で相互に移行する方法", it works fine, there isn't the same problem.

Do you have any clue to duplicate the same problem in a fresh WordPress installation? Otherwise this issue will be taken as an exception.

#1411869

goM

Hellow, Luo

I was able to reproduce the same problem in the following way.

1. New installation of WordPress 5.3.1 site using Local by Flywheel
2.First, install Types 3.3.7 and Views2.9.4.
3. Set Featured Image in post “Hello world!” And save
4.Types plugin updated to 3.3.8 (I used the update method by following Add Plugins> Commercial.)
5.Views plugin updated to 3.0
6.Open the edit screen for the post “Hello world!”

The update process for the Toolset plugin seems to break something.
I don't think this is an exceptional problem.

Newly discovered
Problems occur when a featured image is set on a post.
If I remove the featured image, no warning is displayed.

Working notes:
The theme is Twenty Twenty. And Astra is not installed.
The only plug-ins installed are Types and View.
Post only Hello world!

#1411975

goM
#1412615

Thanks for the details, it is in our to-do list, our developers are working on it:
We have one known recurring issue with WordPress 5.3.1 --> Dynamic Source no longer provides the feature image data. We are aware of it and a fix will be released for it soon.

I will keep on updating here if there is any news.

#1413091

Hello,

Toolset Blocks 1.0.1 is released, please test it and check if this issue is fixed, you can download it here:
https://toolset.com/account/downloads/

#1414765

goM

My problem was solved by an update to Views 3.0.1. Thank you!