Holding fields for review

Hi Peter, thank you. It would have to be the latter because some fields will be allowed to process. I'll check out those hooks 🙂

Oh, and the save-to part is fairly important as well. I am using custom tables. When a change is approved, do I just push it to the custom table field, or do I also need to push it to any WordPress tables like wp_postmeta?

Thanks!

So, I did the after_save_post action with fields, and just got these fields:

` [fields] => Array

        (
            [0] => post_title
            [1] => post_content
            [2] => post_excerpt
            [3] => post_date
        )

Is there a way to access the actual custom fields on the frontend submission?

Thank you, it has worked well. I do need one more thing, however.

Could you tell me how to stop the field from actually pushing to database? As I mentioned, I want to hold certain fields for review, so I tapped into 'rwmb_frontend_before_save_post' and have roughly this:

$old = rwmb_get_value($key, '', $id);
$new = $_POST[$key];

if $old !== $new {
   // Here is where I want to take the field and push it off into it's own custom table but NOT save it to the live site. 
}

Is there a command to prevent $new from saving if there is a change? Thanks!

I was worried you were going to say that, so I thought of an alternative. Seeing as there are only a few fields that will be forced to remain the same until review (2-3 out of 30 or so fields), what I may do is just:

- Save changes to a new table
- Overwrite current table with old data for the 3 fields

If changes are approved, overwrite the live table with the changes

So basically, as a workaround, it'll change it and then instantly revert back to old all in same save. Is that ideal? No. But it is better than re-writing a frontend dashboard without metabox which would take significantly longer than this kludge lol