On my site, I have a CPT, and for this new type of content, I used ACF to create the custom fields. ACF has more field options, besides being more visually beautiful compared to your creator.
All new fields created are plain text fields.
I need help creating the form. The form itself I have already created, but the ACF custom fields do not work.
It doesn't even work with generic fields, including custom field slug.
And I can't find the fields either, when I enter: "manage third-party fields through Toolset". Can't find the CPT in the list.
My CPT was created with Toolset Types.
Custom fields were created with ACF.
It turns out that when I go to "Manage non-Toolset Post Fields" my CPT doesn't appear in the "show fields for" list. Only appears: pages and posts.
By the way, regardless of the project, when I create a new CPT, it never appears in this list. I just never had any problems before, because I've always managed the fields right in your plugin.
But in this specific project, I decided to create the fields with ACF.
It should display the post type with the "show fields for" dropdown. However, I noticed that the custom post type I've added is not available for selection as option with the dropdown "show fields for" .
However, this is really important for you to know that:
"Manage non-Toolset Post Fields" This option will work for simpler fields, which store data as plain text and numerical values. But for more complex fields that store serialized data or data in a special format, it can result in unexpected results. For complex fields that stores data in different format other than text and numeric, it would be better to use the fields added through Toolset Types.
Can you please confirm you will be ok with text and numeric values.
Ok - I got the workaround can you check if it works for you.
You should navigate to the following URL:
- hidden link
Where:
- replace the domain name and the posttype value from "student" to your original posttype slug.
Then try to load this URL in the browser where you loggedin as admin and do you see the fields now?
There is no fix I've to share with you but fortunately you have workaround for now and you should keep using that until the official fix will be shared.
