can the current UI action support metabox setting option field update? the academy/documentation doesn’t really help much and no clear instruction of the fields to update with the form
After several attempts, I am still not figuring out what you are trying to achieve? Could you be more specific? Bascially, you want to use the ProForm form to update a custom field in Metabox. And in your case, your custom field group is being tied to the Metabox Settings page feature (MB Settings Page - Meta Box Documentation) - correct ?
Hey there, thanks for trying to help on this. so basically, there is a phone number field that requires to be change every 2 weeks and instead of letting the team to login to the wordpress backend, i wanted to create a frontend form that allows them to enter the phone number and submit to update/replace the value in the setitng page custom field. so how should i do it? do i use “update post meta” or “update option” or is it something else as the action?
I think you are over-engineering this and using the wrong approach for this case (I also use Metabox). If I were you, I would simply create a WordPress user with minimal capabilities. You can clone basic user capabilities and name the role something like “client,” then use a completely free plugin to limit backend access.
This way, your client can log in to the backend via the standard WordPress login and see only the Settings page. Metabox itself actually supports this concept and allows conditional usage of the form. This means you can restrict the form so that only users with the “client” role can update that phone number field. Or you can limit it to an entire group of fields, a page, or backend view — the choice is yours.
In my experience, this is a better approach because it gives you more detailed insights into logs, changes, timestamps, and most importantly, security. ProForm has basic antispam mechanisms which are sufficient for spam protection, but WordPress login can be hardened with additional security measures, including (free) 2FA. This will also look better to your client.
So basically, I believe you are approaching this the wrong way, but of course, this is just my opinion based on my experience. Without seeing your setup or site in detail, it’s hard to say for sure. However, I would do it this way — without ProForm. Just a nice login for your client through the standard WordPress login, your company logo, backend access limited to specific fields, and everything works smoothly. Later, you can granularly grant more access if needed.