This error message was just sent to me by wordpress:

This support ticket is created 5 years, 2 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.

Our next available supporter will start replying to tickets in about 2.38 hours from now. Thank you for your understanding.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	-	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00	14:00 – 20:00
-	-	-	-	-	-	-

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Tagged: Types plugin

This topic contains 1 reply, has 2 voices.

Last updated by Beda 5 years, 2 months ago.

Assisted by: Beda.

Author

Posts

September 13, 2019 at 8:32 pm #1340185

markusM-3

I just did my updates and I got this from wordpress:
Error-Details
==============
An Error Type E_ERROR was found in row 13 */wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/field/type/definition.php . Message: Interface 'OTGS\Toolset\Common\PublicAPI\CustomFieldTypeDefinition' not found

September 14, 2019 at 8:35 am #1340313

Beda

Could it be that you are updating from an older Types version?
File locations and names changed, and if case sensitive systems met case insensitive deploy methods, it can happen that the files cannot be found on updates.

Now, to know if this is the cause, and as a first testing step, I would recommend to delete the current Toolset Types plugin from your FTP wp-content/plugins folder, or directly in the WordPress plugins list, if you can access it.

Don't worry about data, we only touch FTP Files here. However, to avoid unwanted complications a backup is always good to perform before such steps.

After deleting the plugin, re-download it from https://toolset.com/account/downloads/, and upload that to the server so to activate it again.
This will almost certainly resolve this issue.

Note, OTGS\Toolset\Common\PublicAPI\CustomFieldTypeDefinition should be at least in the complaining file (/vendor/toolset/toolset-common/inc/autoloaded/field/type/definition.php), but also in vendor/toolset/toolset-common/autoload_classmap.php.
This is used since 2.0, so eventually, you update from a previous version?

Please let me know if after the above steps the issue is resolved.