Chris Rault

Hi Alex,

Thanks for taking the time to reply, I really appreciate it.

I’m actually bypassing Dokan for the product forms, so my GF form is saving directly to the WC products.

I remembered it working before on my old dev site, so fired it up, tested the form and it updated the fields, but as a new product. I then realized I still had the APC feed enabled, which has the additional setting to select which fields should upload to the media library. Once I removed the APC feed, the updating stops working all together.

Being that it’s working in the APC plugin, I decided to check the media library plugin and noticed it’s using APC’s gform_advancedpostcreation_post_after_creation action hook:

add_action( 'gform_advancedpostcreation_post_after_creation', array( $this, 'apc_custom_field_integration' ), 10, 4 )

and further down:

## ADVANCED POST CREATION

public function apc_custom_field_integration( $post_id, $feed, $entry, $form ) {

    $auto_custom_fields = array(
        '_product_image_gallery' /* WooCommerce product gallery */
    );

    /**
        * Filter which custom fields GP Media Library will attempt to convert to use image IDs.
        *
        * @param array $auto_custom_fields A list of custom field keys that should use image IDs.
        * @param int $post_id ID of the post for which custom fields are being processed.
        * @param array $entry The current entry ID.
        * @param array $form The current form.
        * @param array $feed The current APC feed.
        *
        * @since 1.2.8
        *
        */
    $auto_custom_fields = gf_apply_filters( array(
        'gpml_auto_convert_custom_fields',
        $form['id']
    ), $auto_custom_fields, $post_id, $entry, $form, $feed );

    $mappings = rgars( $feed, 'meta/postMetaFields', array() );

    foreach ( $mappings as $mapping ) {

        $key = $mapping['key'] == 'gf_custom' ? $mapping['custom_key'] : $mapping['key'];
        if ( ! in_array( $key, $auto_custom_fields ) ) {
            continue;
        }

        $field = GFAPI::get_field( $form, $mapping['value'] );
        if ( ! $field || ! $this->is_applicable_field( $field ) ) {
            continue;
        }

        $value = $this->acf_get_field_value( 'id', $entry, $field, true );
        if ( ! $value ) {
            continue;
        }

        if ( is_array( $value ) ) {
            $value = implode( ',', $value );
        }

        update_post_meta( $post_id, $key, $value );

    }

}

Do you think adding an action hook to the update post plugin, combined with duplicating the function call would work?

Something along the lines of:

‘add_action( ‘gform_postupdate_post_after_creation’, array( $this, ‘apc_custom_field_integration’ ), 10, 4 );’

https://www.loom.com/share/ba7f6b71b2a549b39d6e66dbc5f183d1

Thanks again 🙂

Hey Weston,

Sure, will do 🙂

Hi Michael,

Thanks for taking the time to respond 🙂

That’s right. I figured using the taxonomy field types would have a two way sync, outputting as normal meta fields, but still associating the term with the post.

I considered adding a pivot table to handle the association, but that feels somewhat overkill, so I thought I’d check here first.

Cheers,
Chris

No probs. I just wanted to make sure it wasn’t something I was doing wrong in the GA json. Thanks anyways 🙂

Hi Weston,

Thanks for taking a look 🙂

I managed to get around the html attributes issue by using the markup api in Beans to replace the value on the prefix attribute. I then rechecked the posts in the validation list, but all the issues with the og and http attributes are still there.

Would you mind sending me a copy of the alpha, so I can give that a try?

Cheers,
Chris