Tell us what you are trying to do?
I currently have a bunch of wordpress custom fields already filled out in posts so I took them over in toolset. They just retained the same field name. For example TeamMember. I noticed that if I create a toolset custom field, it adds the wpcf- to any new custom field.
Here's my dilemma. If I stop using toolset in the future, it's going to have a bunch of custom fields with the "wpcf-" prefix on them.
If I instead, just create a bunch of wordpress custom fields and then let toolset take them over then if I uninstall types, the custom fields just revert back to word press custom fields without that prefix because they were never toolset custom fields.
(1) Is this good practice and is there any downfalls to doing it this way?
(2) What happens to custom fields created in Toolset with the wpcf prefix if I release them and turn off toolset?
Hello. Thank you for contacting the Toolset support.
If I stop using toolset in the future, it's going to have a bunch of custom fields with the "wpcf-" prefix on them.
==> Yes, this is expected one as each custom field you will create with Types will have 'wpcf-' prefix.
(1) Is this good practice and is there any downfalls to doing it this way?
==> I think there should not be any issue but I suggest you to follow the Toolset standard.
(2) What happens to custom fields created in Toolset with the wpcf prefix if I release them and turn off toolset?
=> there will not be any side effects as the data will be remain stored in database - nothing else.
