Support Forum ยป User Profile

Forum Replies Created

Viewing 5 posts - 46 through 50 (of 50 total)
  • Author
    Posts
  • in reply to: โœ…select_advanced with Ajax #16555
    wgstjfwgstjf
    Participant

    Ok, so.....an update.

    Just tracked down the following field option:

    
    'sanitize_callback'   => 'none',
    

    With this enabled on our custom select_advanced field the value saves as expected! ๐Ÿ™‚

    My one remaining question is, why is our value being 'sanitized' and thus not stored? Is it because the returned value is not defined as an 'option' when creating the field? If so, how would you recommend getting around this since we cannot define the options as they are pulled in via ajax?

    Thanks in advance,

    Will

    in reply to: โœ…select_advanced with Ajax #16554
    wgstjfwgstjf
    Participant

    On further inspection it seems to be something to do with the following filter action which is called in the process_value function in inc/field.php of the MB plugin.

    $value = self::filter( 'sanitize', $value, $field, $old_value, $object_id );

    Prior to this filter the submitted $value (in this case 'THEREG') is correctly defined. After this filter the $value is empty.

    What sanitizing is happening here and how can we bypass it or meet its conditions?

    Cheers,

    Will

    in reply to: โœ…Clonable select_advanced with ajax #16553
    wgstjfwgstjf
    Participant

    @badabingbreda - Did you figure out why it wasn't storing the value in the end?

    Cheers,

    Will

    in reply to: โœ…MB Custom Table and wp_insert_post #14702
    wgstjfwgstjf
    Participant

    That's great, thanks.

    Are there any knock-on effects when doing WP_Query meta_querys? Does it work as normal?

    Cheers,

    Will

    in reply to: Problem hiding metabox #153
    wgstjfwgstjf
    Participant

    Working perfectly now, thanks for the update!

    All the best,

    Will

Viewing 5 posts - 46 through 50 (of 50 total)