Meta Box

We added support for FontAwesome in the version 1.2.0, see this changelog and documetation.

Hey guys, can you help me to test the fix before releasing a new version? Please try changing parse_conditions function to:

private function parse_conditions( $conditions ) {
    $output = [];
    if ( ! empty( $conditions['visible'] ) ) {
        $output['visible'] = $this->parse_condition( $conditions['visible'] );
    }
    if ( ! empty( $conditions['hidden'] ) ) {
        $output['hidden'] = $this->parse_condition( $conditions['hidden'] );
    }
    return $output;
}

The previous code does JSON-encode all field settings, which contains something like field description and value, which might break the JSON. The new code only encodes the conditions, which eliminate this issue and might improve the performance as well.

Hi Brian, Aart and Austin,

I've debugged with your code and still can't reproduce the error. Although I can add code as Austin suggested, but am not sure the root cause. I also tried Aart's code above, and Austin case with taxonomy and still see nothing.

Can you guys provide me a full code that shows the error?

Hi Amanda,

That's right. For groups, the data is sent as raw, similarly to what you get via the helper function.

Hi Robert,

TailwindCSS is not included in MB Views. We use it in the video for building the HTML quickly (otherwise, we have to write a lot of CSS). You can use any theme, any CSS framework with MB Views. Think like MB Views provides you the HTML only.

Hi prafgon,

The clone_as_multiple is available for all fields, not just group. So it's nice to make query for those fields. But due to the fact that group already store group value as a serialized array of all sub-fields, this option doesn't change the serialization issue.

I'm afraid we haven't got a plan for moving from serialization for group in a near future. I'll check the ACF repeater to see if we can learn from them. Thanks a lot for the reference.

Hi guys,

Rao pointed some valid point over the decision.

I want to clarify that:

sanitize_textarea_field is the best for textarea field from the developer point of view and I agree with that. However, there are some reasons we consider using wp_kses_post as the default sanitize callback:

First: from user point of view, as David said, they don't know what happen behind the scene. And in fact, they do use textarea for storing HTML a lot! Something like footer credit or some text for the top bar. Some even use it for embeded videos. We see this behavior all the time. So we decide to use wp_kses_post to bring more comfort to users. Note that, this doesn't mean less secured! Both wp_kses_post and sanitize_textarea_field are secured (and that's the main point of the sanitization). We need to keep balance between comfort and strictness.

Second: as Rao said, backward compatibility is important. Being activated on 500k sites, we don't want to get thousands of complaints and support topics for the same broken textarea. In fact, there are many topics here and on wordpress.org forums asking why their textarea field not working as expected (because they store embeded videos HTML code).

I can say, if I build Meta Box again from scratch, sanitize_textarea_field might be the best choice. But at this time, wp_kses_post is a better choice.

And remember, they're both secured. That's the main point.

That's a good idea, Drake. I'll add to the plugin.

Updated: Added to version 1.0.11.