Skip Navigation

[Resolved] Fatal error after update to Toolset Types 3.3.11

This support ticket is created 4 years, 7 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
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 8 replies, has 3 voices.

Last updated by Florian 4 years, 7 months ago.

Assisted by: Shane.

Author
Posts
#1666715

After Update to Types 3.3.11: As soon as we try to publish or change a (custom type) post that contains custom post fields, a fatal error occurs after pressing the "Save" or "Publish" button. However, only if the own contribution fields contain an image field.

#1667189

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Florian,

Thank you for getting in touch.

Would you mind allowing me to have admin access to the website so that I can have a look at this for you ?

Can you also provide FTP access as well.

The private fields will be enabled for your next response. Also should I need to grab a copy of your website I will be using the Duplicator plugin if that's ok with you.

Thanks,
Shane

#1667819

Unfortunately it is not possible to grant access to our internal networks, which are secured with a stable TFA. However, the problem is easy to reproduce. Are there no messages from other users in this regard?

#1668407

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Florian,

Unforutnately no we are not able to reproduce the issue as on my end the button works fine. Are you able to provide me with a bit more detail on the Fatal Error ?

Are you able to send me the error message itself?

Thanks,
Shane

#1670055

Dev

Hi FWIW -- we had the same error in our environment: Multisite with Ubuntu 18.04 environment -- php 7.2 I turned on debugging but don't see any useful errors when saving. I reverted to 3.3.10 and it works. Should have added: we are still at WP 5.3.2.

#1671755

Thank Rod for finding the same mistake.

And Shane: Have you tried custom fields including a field for images to a custom post type? I can also reproduce the error on a new installation. If a field for images is provided, "Publish" will run into a fatal error.

#1672313

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Florian,

I installed a brand new wordpress installation and a fresh copy of Types.

I've also created a set of custom fields including an image field and attached it to a post type. When I go to the post type and create a new post. I was able to publish with no issues at all.

Are you able to provide a duplicate of the website you are using ? Secondly if not can you provide step by step instructions on what you did on a Fresh installation of wordpress to replicate the issue ?

Thanks,
Shane

#1674369

Hi Shane,

It's a pity you didn't draw my attention to known incidents That would have helped to identify image enhancement processes on the server as the cause. Here https://toolset.com/errata/fatal-error-in-image-optimisation-plugins-when-using-types-3-3-11/ I found an effective hint incl. patch that fixes the bug and makes version 3.3.11 usable again.

Thanks,
Florian

#1674373

My issue is resolved now. Thank you!