Skip Navigation

[Resolved] Custom field crashes site

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/Karachi (GMT+05:00)

This topic contains 1 reply, has 2 voices.

Last updated by Waqar 10 months ago.

Assisted by: Waqar.

Author
Posts
#2646189

Hello, Toolset Views Ceashes the website if it is activated. Seems to be related to custom content.
WordPress-Version 6.3.1
Toolset Types (Version 3.4.20) PHP-Version 8.0.30-he.0

I've tried to enter a custom content field "termine". The data has not been stored correctly, since then Toolset Types crashes and deliveres this message. I have have no clou how to get rid of this buggy "Termin". Where can it be found? in a file or in the database?
Thx in advance, Holger

Fehler-Details
==============
Ein Fehler vom Typ E_ERROR wurde in der Zeile 200 der Datei /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-types.php verursacht. Fehlermeldung: Uncaught ValueError: Missing format specifier at end of string in /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-types.php:200
Stack trace:
#0 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-types.php(200): sprintf('Edit %', 'Termin')
#1 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-content/plugins/types/vendor/toolset/types/embedded/includes/custom-types.php(104): wpcf_custom_types_register('termin', Array)
#2 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-content/plugins/types/vendor/toolset/types/embedded/functions.php(117): wpcf_custom_types_init()
#3 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-includes/class-wp-hook.php(310): wpcf_init_custom_types_taxonomies('')
#4 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters(NULL, Array)
#5 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#6 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-settings.php(632): do_action('init')
#7 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-config.php(108): require_once('/is/htdocs/wp12...')
#8 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-load.php(50): require_once('/is/htdocs/wp12...')
#9 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-admin/admin.php(34): require_once('/is/htdocs/wp12...')
#10 /is/htdocs/wp12092123_2S7P4NQATM/www/prorad/zuki/wp-admin/plugins.php(10): require_once('/is/htdocs/wp12...')
#11 {main}
thrown

#2646547

Hi,

Thank you for contacting us and I'd be happy to assist.

From the error that you've shared, I understand that the 'singular name' value for this particular post type wasn't saved properly in the database.

Does the website crash, as soon as you activate Toolset Types or does it allow you to activate Types and access the custom post types management screen?

If it doesn't allow you access to the post type management screen from Types, it will require some database level changes.

Toolset Types stores the custom post type registration data in the WordPress 'options' table with the name/key 'wpcf-custom-types'. ( this data is in a serialized form )

You can share that serialized data with us or unserialize it and adjust the 'singular name' value for this particular post type.

I hope this helps and please let me know if you need further assistance.

regards,
Waqar

#2646733

thx a lot, Wagar. I've deleted the database entry 'wpcf-custom-types' in the WordPress 'options' table and Toolset is now working properly. Regards, Holger

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