Hello. Thank you for contacting the Toolset support.
Yes, please, Can you please share admin access details as well as mention the required steps we should follow that should lead us to reproduce the issue.
*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.
I have set the next reply to private which means only you and I have access to it.
I checked on your install and yes I can see the issue.
But the strange this is that I could not able to reproduce the issue when I checked with clean WordPress site. I just try to install a clean WordPress install and I only install and activated Types plugins.
- I've created the post type Student and I disable the post content (editor) field on this post type
- I've created custom field group and added WYSIWYG field and assigned this custom field group to post type "Student"
- I've tried to add new post and (where there is no content field available) I see only the WYSIWYG field is available and I tried to add content and saved the post and it works just fine.
I see you are using number of third-party plugins including the "Classic Editor" plugin. In order to minimize the cause of the issue and to ensure there is no conflict between third-party plugins or theme:
*** Please make a FULL BACKUP of your database and website.***
Could you please try to resolve your issue by deactivating all third-party plugins as well as with the default theme to check for any possible conflicts with any of the plugins or themes? - Do you see any difference?
As when only Toolset plugins active I do not reproduce the issue and even you shared the update that the issue is when you activate the plugins:
- Advanced Custom Field's Pro
- FontAwesome
Can you please check with the plugin author of "Advanced Custom Field's Pro" and "FontAwesome" to ensure that the issue is from their side or Toolset. If they share that the issue is from Toolset, we are happy to address it.