Skip Navigation

[Resolved] Toolset Types + Gutenberg Editor => “Missing or invalid field data” error

This thread is resolved. Here is a description of the problem and solution.

Problem: I am unable to edit a post and I see an error "Missing or invalid field data"

Solution: In this case, a required field in one of the collapsed field groups was empty. That field must be filled in to edit the post successfully.

This support ticket is created 4 years, 5 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
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 3 replies, has 2 voices.

Last updated by GamX 4 years, 5 months ago.

Assisted by: Christian Cox.

Author
Posts
#1763815
Screen Shot 2020-09-01 at 3.09.08 PM.png

Editing a post in Gutenberg visual block editor.
Post contains Toolset conditional blocks, field and text block, form block.
When I click "Update" button to save changes, I get the following error at the top of the editor with a red background:
"Missing or invalid field data."
So I am unable to save any changes to my post.
BUT if I deactivate the Toolset Types plugin, I am able to update my post with no problem. Of course this deactivates my Toolset information so errors appear to user on the front end.
If you cannot solve with this information, let me know and I will provide access. Thank you!

#1764343

Hi, I'll be glad to log in and take a closer look if you provide login credentials. Can you tell me if this error occurs on all posts in this post type, or if it is limited to one specific post? If it's a specific post, please tell me which post so I can run some quick tests. I may need to delete some of the Toolset-specific blocks in a process of elimination to determine the source of the issue, so I would suggest making a backup or duplicate of this post if you don't want to lose your work.

I have added private reply fields to your next reply so you can share login credentials securely.

#1764587
Screen Shot 2020-09-02 at 5.15.14 PM.png
Screen Shot 2020-09-02 at 5.03.27 PM.png

It looks like there is a required field in the Players-Field-Group field (screenshot attached). It is called "player-first-name" and it must be filled out because the field is marked "required" in field settings. After I add some text in the player first name field, the post can be published successfully. See my update here: hidden link

What concerns me is that the field group was not set to be displayed on the Post post type, so I'm not sure why this field group appeared in the standard Post editor. I changed the settings for the field group to be displayed when ALL conditions are met instead of ANY, and now the field group does not appear in the standard Post editor any longer. It's odd...it seems like ANY would work just like ALL here because there is only one condition. Maybe there was some caching at play, but regardless, it seems to be working better now. Can you confirm?

#1764749

Hi Christian! Took another round but eventually got it to work, thank you! I had created a new custom post type "Players" that I was trying to link with the user profile as a result of another ticket. Couldn't get it to work which is probably why you found errors, and it also caused these other problems.

So even though the regular post update did work when you fixed some of those details, updating a LearnDash custom post type post did not work (resulted in the same error) until I got rid of everything associated with that new post type "Players" that I was experimenting with. So I deleted the "Players" post type along with all of its relationships and custom fields. Hoping I won't need to go down that road again, it was complex. So for now I'm good! Thank you!