@rickjames68
I will try to answer your query here and from the email you sent me.
If a plugin can create the custom fields found underneath a custom post type, why can’t those fields be included in the front end?
this plugin, as its current version can create custom post field, but not read the custom post fields under your custom post type.
why is that so?
first, the plugin has it’s own record on what input your custom post field will use… example: checkbox, textbox, radio buttons, etc…
now, your theme might have custom post field but might be limited to textbox only… well, depends on how the field was coded.
the plugin “can” get those fields, but assuming what kind of input would be the hard part. currently, the plugin is not capable of doing so.
Maybe soon this plugin will evolved to that..
talking about conflict, it won’t… why? the plugin is using a prefix for all it’s custom post field. there’s a possibility of conflict, but just a little…
for example, if you add a custom post field in the plugin, you’ll have something like cf_teacher. -that is if you are adding a teacher as custom post field using this plugin. Conflict will occur if you’ll add a custom post field under your custom post type with a key cf_teacher. But if you’ll intend to add custom post field cf_teacher, the custom post field under your custom post type and the custom post field under this plugin will now somewhat sync.. thus, editing at backend or frontend will result to update cf_teacher.
I may have missed some points.. please let me know…
automatic backend to frontend fields? answer is no. not automatic. you have to build the frontend.