Meta Box

Oh, I should have made it clear. It's the JavaScript code, so you should put it in your theme main script file. Or better, create a JS file (assume its name is custom.js) in your theme folder, and put this content inside:

$( function() {
    // Snippet goes here.
    var total = 0;
    $( '.like input:checked' ).each( function() {
        total += $(this).val();
    } );
    // Output total somewhere
    $( '#selector' ).text( total );

    // More snippet goes here.
} );

And then in your functions.php file of the theme, add the following code:

add_action( 'wp_enqueue_scripts', function() {
    wp_enqueue_script( 'custom-handle', get_template_directory_uri() . '/custom.js', array( 'jquery' ), '', true );
} );

This thing is quite technical, though.

I'm afraid it's not available for select field type. But you can do that with select_advanced. See this option on select2 docs.

Let me update the extension to remove the post_type rule. People still can set the post types anyway.

Update 1: Done! Version 1.3.1 is available.

Update 2: I was too rush. The 'post_type' seems to be related to many things. I have to revert it to the previous version.

Hi,

Are "Tampa" and "St Pete" terms of the "office location" taxonomy?

If so, you have some ways to store the actual address of each location (each term):

• Use the default WordPress term's description for actual address (https://imgur.elightup.com/GIU2Bbb.png). If you don't use the description for any purpose, it's good to use it for address, cause it doesn't require any coding.
• Or you can use the MB Term Meta extension to add a text field "Address" for "office location" taxonomy. You can use the MB Builder to create that field for you if you're not familiar with coding. Just remember to go to Settings tab and select "Terms" & "Taxonomy" for the setting "Show meta box" for.

After that, you'll be able to enter address for each location ("term") when you edit them.

To show the office address, you can use this snippet:

$locations = wp_get_object_terms( get_the_ID(),  'office_location_taxonomy' );
if ( ! empty( $locations ) && ! is_wp_error( $locations ) ) {
    $location = reset( $locations );
    echo 'Address: ', $location->description; // If you use term description.
    echo 'Address: ', rwmb_meta( 'address_field_id', array( 'object_type' => 'term' ), $location->term_id ); // If you use MB Term Meta
}

Hi Doug,

I've worked with the map field and Geolocation in the last couple of days and made some improvements. I've just released a new version of Geolocation extension with a better compatibility with the map field. Previously both Geolocation and map field try to enqueue their own Google Maps scripts, which causes some kind of conflict. This conflict was fine until recently, it prevents some autocomplete for the address field.

Can you please update it or the Meta Box AIO and let me know how it goes?

Regarding the "Find Address" button, I also added some small improvements if the map is inside a group. The change is not in the new version of Meta Box yet. It's on Github and you can download it here:

https://github.com/wpmetabox/meta-box/

I'm making some other improvements and will release new version of Meta Box when they're done.

Hi,

To make things easier, I'd suggest adding a common CSS class (like) for all the radios. You can do that with the class attribute of the field.

Then, you can perform some JS code like this:

1. Get total value:

var total = 0;
$( '.like input:checked' ).each( function() {
    total += $(this).val();
} );
// Output total somewhere
$( '#selector' ).text( total );

Anyway, as all the radio have values 1 or 0, the total value is equal to the number of "likes", which can be done with the following code.

1. Get number of likes:

var total = $( '.like input:checked' ).length;
// Show an error message
if ( total > 30 ) {
    alert( 'You have selected more than 30 likes. Please select again' );
    // or
    $( '.error-message' ).text( 'You have selected more than 30 likes. Please select again' );
}

You can:

• Get the author of the submitted post (via post_id)
• Get the current user ID

And just compare them. When they match, output the shortcode. Otherwise, output some error message.