WordPress caught an error with one of your plugins, Toolset Types.

This support ticket is created Il y a 4 années et 7 mois. 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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

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)

Marqué : Types plugin

This topic contains 2 réponses, has 2 voix.

Last updated by Laura Il y a 4 années et 7 mois.

Assisted by: Shane.

Auteur

Publications

septembre 9, 2019 at 2:32 pm #1335355

Laura

I just updated Types to the latest version 3.3.5 and received an email from WordPress stating that it detected a fatal error:

Error Details
=============
An error of type E_ERROR was caused in line 13 of the file /home/204758.cloudwaysapps.com/bpzhjnztgu/public_html/wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/field/type/definition.php. Error message: Interface 'OTGS\Toolset\Common\PublicAPI\CustomFieldTypeDefinition' not found

BUT it seems the site is working ...soooo..... not sure what this means? Just thought it best to let you know just in case.
Thank you!

septembre 9, 2019 at 6:40 pm #1335817

Shane

Supporter

Languages: Anglais (English )

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

Hi Laura,

Thank you for contacting our support forum.

This could be a one off message being generated by the server though some silent update of sort.

Is this the first time you're getting this error in your mail or is it a recurring message?

If it is a one off message and no longer occurs, then it's quite possible something on the server triggered it.

Thanks,
Shane

septembre 9, 2019 at 7:19 pm #1335875

Laura

My issue is resolved now. Thank you! Hi Shane,,,, Thanks for responding... No this seems to be a one-off thing... the site seems to be working fine, so I won't waste either of our time on it now. Unless it becomes a problem again then we can look more deeply into it. For now I can consider this ticket resolved.

Thanks!

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.