Meta Box

Metabox Time Field shows 1.1.1970 in Bricks Builder after clearing value

Support › Meta Box AIO › Metabox Time Field shows 1.1.1970 in Bricks Builder after clearing value

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • February 4, 2026 at 2:48 PM #49727
    Simon EgleSimon Egle
    Participant

    I'm experiencing an issue with a Metabox Time field when using it with Bricks Builder.

    Setup:
    Metabox Time field with timestamp storage
    Displaying the field value in Bricks Builder

    Issue:
    When I clear/delete the content of the Time field and save the post, Bricks Builder displays "1.1.1970" instead of showing an empty value or nothing at all.
    Expected behavior:
    The field should be completely empty after clearing the value.
    Actual behavior:
    It appears that when saving an empty Time field, the value is not fully deleted but instead leaves a "1" in the database, which Bricks then interprets as a timestamp (Unix epoch = 1.1.1970).
    Question:
    Is this a known bug, or do I need to configure something differently to ensure the field value is completely removed when cleared?

    February 4, 2026 at 9:06 PM #49731
    PeterPeter
    Moderator

    Hello Simon,

    Thanks for reaching out.

    The time field doesn't support the timestamp setting; only the datetime field supports it. If you create the field group with code, please remove that setting and recheck the issue. Following the documentation
    https://docs.metabox.io/fields/time/

    February 5, 2026 at 5:35 PM #49734
    Simon EgleSimon Egle
    Participant

    Screenshot Timestamp

    Hi Peter,

    thanks for your reply.

    Thank you — however, I’d like to clarify something: as you can see in the attached screenshot, it is possible to enable timestamp on a regular time field in the UI (I’m using the latest MetaBox version).

    The issue only appears once the field is placed inside a cloneable group — in that case, the timestamp option disappears and can no longer be enabled.

    So to summarize:
    • Time field outside a cloneable group → timestamp option is available
    • Same time field inside a cloneable group → timestamp option is missing

    Could you please check whether this is expected behavior or possibly a bug?

    Thanks a lot for your help.

    Best regards
    Simon

    February 5, 2026 at 8:46 PM #49735
    PeterPeter
    Moderator

    Hello,

    Based on your screenshot, it is the DATE field, not the TIME field. Regarding the timestamp setting in a group field, it is expected behavior and noted in the documentation
    https://docs.metabox.io/extensions/meta-box-group/#data-storage

  • Author
    Posts
Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.