Meta Box

Hi Jason,

I've just checked the heading field and it's all fine. Can you take a screenshot of the console before the closing </form> tag, so we can see which field closes the div incorrectly?

The whole code for that part is available on Github. I'll write a tutorial for that later.

FYI, it's now updated. Please check and let me know how it goes.

No problem.

Here is the process of creating the storage for meta box and its fields:

- When a meta box is created, a storage will be created for it. The function rwmb_get_storage() will handle the creation.
- The rwmb_get_storage() uses a filter rwmb_get_storage that allow extensions to change the storage. That's where the MB Custom Table filters and change the storage to work with post meta to the one works with the custom table. In this filter, the whole meta box settings is passed, so extensions know the storage_type and table name.
- After the creation, this storage will be added to all fields in the meta box via $field['storage'] parameter.
- When working with the meta value (get/save), this storage will be use like $field['storage']->get() and $field['storage']->update().

So, storage is kind of the abstract layer between the code and the database. And that can be changed with filters.

That's how the plugins work. If there's something unclear, please let me know.

Thanks for bug report. It's just fixed on Github.

Hi James,

Great stuffs!

What would I have to do to customize the FacetWP Integrator so that it would loop through the custom fields that I want to use as facets or indices? Is there not a way to have the Integrator do this by using the parameters ‘storage_type’ & ‘my_table_name’?

I forgot about this! The Integrator uses Meta Box's function rwmb_get_value() to get field value and that already handles the storage type. Theoretically, it should work! Can you please just try it and let me know how it goes?

Hello James,

Thanks for asking the great question! You're indeed right about 90%.

Meta Box uses WordPress standard way to store post meta. So it should work in most cases as normal custom fields for FacetWP.

However, there are 2 cases that we need to handle: clone and multiple fields, as you can see in this code: https://imgur.elightup.com/ONbJioO.png

The reason is clone values is saved as serialized array in the post meta, thus, it's not the standard WP way. Actually, WP doesn't have mechanism to save such kind of data yet. So, we have to find a way to work on that. Because FacetWP doesn't process serialized array, we have to do that.

The other case of field with multiple values, although it's the WP's way, but I still pull all the data just for sure.

So, if all of your fields (or the fields you want to filter) is just normal / uncloneable fields, you can just use FacetWP without any problem. In other cases, the extension will help.