Meta Box

Hello Eugene,

I think you can use the WP Query to query posts with the custom field parameter, please follow the documentation https://developer.wordpress.org/reference/classes/wp_query/#custom-field-post-meta-parameters

Note: It's difficult to query posts based on the subfield value in a group field. The purpose of the group field is to store data, not for query. Following this article https://metabox.io/create-group-of-custom-fields-with-meta-box-group/#how-does-the-meta-box-group-save-data

Hello,

You are using the custom query, so you need to add the parameter manually. The fields in the Insert fields area only work with the main query. Please read more about the custom query and main query in the documentation
https://docs.metabox.io/extensions/mb-views/#insert-fields
https://docs.metabox.io/extensions/mb-views/#main-query
https://docs.metabox.io/extensions/mb-views/#custom-query

Hello,

I've escalated this case to the development team. We will consider using cache when getting field value from the custom table with the function rwmb_meta() only and the rest will be queried directly from database.

Thank you.

Hello Nick,

It isn't possible to reset the new form after submitting it. The form will be removed and you need to reload the page to get a new form.

Hello,

The begin HTML is not duplicated, the field wrapper will be duplicated. You can use the Inspect tool of the browser to check the HTML structure, screenshot https://imgur.com/LvoxdxO

I'm not sure if there is a way to also know which numbered clone it is targeting, you can try to use the JS code and append your prefix HTML.

Hello,

This happens because you are in the software_reciprocal loop but output the software post title. I fix that issue with this code {{ software_reciprocal.post_title }}

{% set args = { post_type: 'alternative' } %}
{% set alternatives = mb.get_posts ( args ) %}
{% for alternative in alternatives %}
    {# {{ alternative.post_title }} #}
    <h2>Alternative: {{ alternative.post_title }}</h2>
    {% set software_args = { post_type: 'software', relationship: {id: 'software-cpt-and-software-alternatives-cpt', to: alternative.ID} } %}
    {% set softwares = mb.get_posts ( software_args ) %}
        {% for software in softwares %}
        <h3>Software: {{ software.post_title }}</h3>
        {# {{ software.post_title }} #}
            {% set software_reciprocal_args = { post_type: 'software', relationship: {id: 'software-cpt-reciprocal-relationship', from:software.ID} } %}
            {% set software_reciprocals = mb.get_posts ( software_reciprocal_args ) %}
                {% for software_reciprocal in software_reciprocals %}
                    <h4>Software_reciprocal: {{ software_reciprocal.post_title }}</h4>
                {% endfor %}
        {% endfor %}
{% endfor %}

Hello Benjamin,

A revision actually is a new post, post type revision. If you use those hooks, you can compare two variables:
- $row['ID']: the revision post ID
- $_POST['ID']: the current post ID
to "distinguish between adding a record and modifying an existing one".