Skip Navigation

[Resolved] Saving CPT returns an error after upgrade to WordPress 5.3

This support ticket is created 5 years, 3 months 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
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

This topic contains 6 replies, has 4 voices.

Last updated by andyS-5 5 years, 2 months ago.

Assisted by: Nigel.

Author
Posts
#1383063

Hi,

I have upgraded to WordPress 5.3 and my CPT created with Toolset is returning error when trying to save it:
Warning: parse_url() expects parameter 1 to be string, array given in /home/www/................../wp-includes/media.php on line 4246
Warning: strpos() expects parameter 1 to be string, array given in /home/www/................../wp-includes/media.php on line 4253

I have upgraded to WP5.3 on other sites where I use CPT created with Toolset and none of them has this problem and the only difference is that with the current site I am using custom field for image (repeating custom fields) which I don't use on those other sites.

I tried to deactivate other plugins and nothing helped, the only thing that helps is downgrade to WP 5.2.4 for the error to disappear. I have spent hours on this problem already. The CPT having problem is called "osobnosti".

#1383135

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Hi David

I checked this and found the same, that the PHP warnings appear when saving a post that has an image field with repeating values.

I've escalated this so that it can be examined further by the developers, and I'll get back to you with their findings.

#1396367

Hey, I'm getting the same error, I also wait for un update about this issue.

thanks

#1399495

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

This will be fixed in Types 3.3.8, which is imminent, possibly later today (it will be bundled with the major Views update).

If after updating you still see the error, please let me know, thanks.

#1402883

I will provide feedback whenever the new version is available, but as of today, 3.3.8 still not available.

#1403067

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

The publish buttons have been pressed by the developers, so it's just a question of the release being handled by the systems team.

If not later this evening, then the morning.

#1406617

I had what appears to be exactly the same issue. I can confirm updating to 3.3.8 fixed it for me 🙂