Meta Box

Both websites use Metabox 3.3.5. Each website is on its own server.

I just tested the import again and I notice when doing a quick edit that the date was off by 5 hours. So instead of being published at 9am this morning that date read 2pm. Changing the time to now allowed me to publish the custom field and enable it (obviously). Not sure why the time gets bumped here when importing.

Both the server and the website are set to the same time and zone. Could MetaBox be using the Universal time here instead of Local? (as Univeral is 5 hours ahead)

Universal time is 2026-01-05 14:12:25.
Local time is 2026-01-05 09:12:25.

I've tried 3 different custom fields group import files.

Here is the json of one of them.

{
    "$schema": "https://schemas.metabox.io/field-group.json",
    "fields": [
        {
            "name": "Image Position",
            "id": "image_position",
            "type": "select",
            "desc": "Image position. Inline (Left to Right) first and then Block (Top to Bottom)",
            "options": {
                "Left Top": "Left Top",
                "Left High-Center": "Left High-Center",
                "Left Center": "Left Center",
                "Left Low-Center": "Left Low-Center",
                "Left Bottom": "Left Bottom",
                "Center Top": "Center Top",
                "Center High-Center": "Center High-Center",
                "Center Center": "Center Center",
                "Center Low-Center": "Center Low-Center",
                "Center Bottom": "Center Bottom",
                "Right Top": "Right Top",
                "Right High-Center": "Right High-Center",
                "Right Center": "Right Center",
                "Right Low-Center": "Right Low-Center",
                "Right Bottom": "Right Bottom"
            },
            "std": "Center Center",
            "select_all_none": false
        }
    ],
    "id": "hero-image-controls",
    "modified": 1764170240,
    "post_types": [
        "page",
        "news"
    ],
    "title": "Hero Image Controls"
}

Thanks for the info. I had done a quick search but missed the report which surprised me since it was so easy to reproduce.

I had waited a few weeks after the major version (3.2) was released to update and I had assumed no show stopping bug (which this one kind of is even though work around is easy once you know it). Teaches me... Always wait for the .1 after a major release.

Anyways I had tried that workaround when I first discovered the bug but couldn't enter any data in the field but rereading your info I see you have to wait until the request happens and then the field becomes editable.

Thanks again

This issue is still happening for every version of Metabox. It happens on Slim SEO as well. For example there is a new version of Slim SEO Schema out and it only shows the change log up to 2.6.4 from Sept 20.

Over the last few days I have checked the change log and it hasn't been updated.

I've cleared the cache rebooted my PC, checked it on my phone etc.

It's not me either. I ran the change log through Google Page Speed and it sees only up to version 2.6.4 as well.

https://pagespeed.web.dev/analysis/https-wpslimseo-com-products-slim-seo-schema-changelog/c0v6z94v54?form_factor=mobile

Also can you include a link to your change logs for your paid products within the WordPress plugins UI. It would save a few clicks.

Thanks

Yes by doing Peter's suggestion of increasing the PHP setting max_input_vars.