Meta Box

Hello Tom,

I can understand the issue. I'm going to escalate it to the development team to enable an option to publish the field group in this case.
You can temporarily set the local time to UTC +0 and import field groups to publish them, then set the local time back to your original setting.

Thanks.

Hello,

Thanks for reaching out.

If the field value saved to a custom table works with Bricks builder, that means there isn't an issue on the Meta Box side. Also, I recheck the Rest API on your site and it shows the custom field value as well
https://test-etch2.touchdowntech.dev/wp-json/wp/v2/service/352

screenshot https://imgur.com/T3nQnuG

Hello,

I don't see any post field in your field group. Could you please recheck this and share 2 field groups that are assigned to one settings page? Or share a screen record of steps you take from the beginning so I can reproduce the issue on my site?

Thank you.

Hello Michael,

Thank you for your feedback.

I've forwarded the deprecated notice message to the development team to update Google map field. Let me know if you have any questions.

Hello Leo,

1. I've not implemented any performance benchmarking for these options. However, Meta Box won't affect the performance because you just get the field values and show them in the frontend.

2. Depending on your requirements but I think using Meta Box AIO will be better if you want to use some other extensions later.

Hello Tobias,

Thanks for reaching out.

This happens because the setting timestamp is still applied to the time field.

        {
            "id": "event_time_start",
            "type": "time",
            "label_description": "Um wie viel Uhr beginnt das Event?",
            "placeholder": "09:00",
            "timestamp": true,
            "inline": false,
            "columns": 3,
            "prepend": "Beginnt um:",
            "tab": "tab_event_details"
        },

You can remove it from the JSON file or add the field setting timestamp -> false to fix the issue, screenshot https://imgur.com/ZkRFC2f

Hello Clint,

Thanks for your feedback.

After regenerating the CSS cache, can you please reload the Field Groups page and enable/disable the field group to see if it helps? I think the issue happens when you don't reload the page and enable/disable the field group after regenerating the CSS cache.