After deleting a custom filed group or renaming a custom field group we get a 500 error message when trying to view or create a post.
Here is a sample of the log error when renaming the custom fields.
PHP Fatal error: Uncaught InvalidArgumentException: First argument is not a post. in /mv4-1/wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/field/group.php:60 Stack trace: #0 /mv4-1/wp-content/plugins/types/vendor/toolset/toolset-common/inc/autoloaded/field/group/post.php(41): Toolset_Field_Group->__construct(NULL) #1 /mv4-1/wp-content/plugins/types/vendor/toolset/types/embedded/includes/fields-post.php(158): Toolset_Field_Group_Post->__construct(NULL) #2 /mv4-1/wp-content/plugins/types/vendor/toolset/types/embedded/admin.php(107): wpcf_add_meta_boxes('mot', Object(WP_Post)) #3 /wordpress/core/5.0.2/wp-includes/class-wp-hook.php(286): wpcf_admin_add_meta_boxes('mot', Object(WP_Post)) #4 /wordpress/core/5.0.2/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters('', Array) #5 /wordpress/core/5.0.2/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #6 /wordpress/core/5.0.2/wp-admin/includes/meta-boxes.php(1416): do_action('add_meta_boxes', 'mot', Object(WP_Post))
Is it possible for you to temporarily remove, deactivate or otherwise flush this object caching system on your site? I think this may be related to another one of your tickets as well: https://toolset.com/forums/topic/split-split-table-field-field-group-title-its-not-saved/
Let me know what you find out.
Purging the site cache seems to have solved the issue. Thank you for pointing us in the right direction.
Great, let me know if you have any additional concerns about that.
Purging works fine. No more issues.
One additional question: I created a custom filed/ post reference. The posts I want to reference to (and only show the title) are from the same post type (Mots) but "Mots" is the only post type that is grey out and can't be selected.
How can I go around this?
I've split your new question into a separate ticket, and I will follow up there shortly.
My issue is resolved now. Thank you!
Just checking on the new separate ticket. Thank you.