rickjames68

If Plugin “A”, creates a custom post type with it’s own custom fields, it would give those custom fields a unique name, correct? Maybe something like “pf_address”

Just as if I were to create custom fields with WPUF, they would have unique names with “cf_address”, correct?

These would not update the same database table, right? One would update/populate pf_address while WPUF would update/populate cf_address

So now I just need to build a form to include under the WPUF Add Post that mimics the fields found in the back end so that it will populate those fields in the database correctly? Will I also need to include this same form in the WPUF Edit Post so that if they choose to edit a newly submitted form to the database it will update those as well on the WPUF Edit Post page? All from the front end?

=================================================

@tareq Hasan If the above works, by just creating a custom form to include under your shortcodes to update the database tables of other plugins, this may solve the problem many people are facing on this support forum of not being able to edit other plugin custom fields. A simple tutorial on how to do this would be useful to point those users of WPUF to, who want to update custom fields of other plugins that can’t be updated by the custom fields of WPUF.

Hi Tareq,

The plugin creates the custom fields which populates the rest of the plugin in functionality. Wouldn’t there be a conflict of names for the custom fields?

Does your plugin not pull from the back end dynamically? Or do you hard code all the functionality into it?