Skip to content

Using multiple date fields with the same handle (even if one is nested in a replicator) breaks the validation message #11659

Open
@j3ll3yfi5h

Description

@j3ll3yfi5h

Bug description

We used two date fields with the same handle in our blueprint, one on the top level and one inside a replicator. If the one in the replicator is required and is not filled, the validation message appears on the date field on the top level:

Image

How to reproduce

  1. Create a blueprint with two date fields with the same handle and make them both required. (one e.g. on the toplevel and one inside a replicator)
  2. Fill the one on the toplevel and leave the one inside a replicator empty
  3. Check the validation message, where it appears.

Logs

Environment

Environment
Application Name: Statamic
Laravel Version: 12.7.2
PHP Version: 8.3.17
Composer Version: 2.8.6
Environment: local
Debug Mode: ENABLED
URL: date-handle.test
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file

Storage
public/storage: NOT LINKED

Statamic
Addons: 0
Sites: 1
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 5.52.0 Solo

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions