Does rwmb_outer_html still work?

Weirdly the filters do seem to be called. I guess I'm not searching for the right things in the code.

So here's the question.

If I use the rwmb_outer_html filter to add a beginning div to the outer wrapper of a field, is there a way to prevent it from automatically adding the ending div until I add it manually to the end of another field?

Basically I'm trying to add a div wrapper to a group of fields. But no matter which filter I use, metabox seems to automatically try to clean up the html with matching closing tags which messes up what I'm trying to do.

Thanks.

Hi:

Thanks. I actually want to add a class around a group of fields already inside the metabox. Adding the class on the metabox affects all fields. I want to add the class only around one or more groups of fields inside the metabox.

The only solution I was able to arrive at for this was to directly modify the metabox-columns plugin.

I modified it to accept two more values in the metabox array of fields "column_row_before" and "column_row_after" which allows for injection of the field class before and after any field 'row' without automatically closing up starting div.

I was hoping to be able to submit that as a PR against your repo but it's not a public repo.

There's probably a smarter way to do it - maybe by wrapping things the way the metabox group module works. But didn't want to spend that much time figuring that out.

Here's an image of the code changes for anyone interested.

Thanks.

I think that still automatically closes a div that might be set in the BEFORE setting, right? I believe I tried that a bit ago. If you use a before such as '<div class="xxxx">' something causes the div to close up before we can specify a closing '</div>' of our own in a later field.

Unless that behavior has changed recently?

Thanks.