You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried to use the validation replacements for an entry field (like that: validation_rule:{id}) to get the ID of the entry inside the rule. That works fine if the entry field is on the top level, but I get NULL instead of the entry ID if the field is part of a replicator or grid.
Add an entries field to a replicator or grid with a custom validation rule, and notice that instead of the ID we get a NULL.
Logs
No response
Environment
EnvironmentApplication Name: appLaravel Version: 10.48.10PHP Version: 8.2.7Composer Version: 2.7.2Environment: localDebug Mode: ENABLEDURL: example.comMaintenance Mode: OFFCacheConfig: NOT CACHEDEvents: NOT CACHEDRoutes: NOT CACHEDViews: CACHEDDriversBroadcasting: nullCache: statamicDatabase: mysqlLogs: singleMail: sendmailQueue: syncSession: fileStatamicAddons: 0Antlers: regexSites: 1Stache Watcher: EnabledStatic Caching: DisabledVersion: v4.54.0 PRO
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered:
duncanmcclean
changed the title
[4.x] validation replacements for entry field not working inside replicator and grid
Validation replacements for entry field not working inside replicator and grid
May 14, 2024
Bug description
I tried to use the validation replacements for an entry field (like that:
validation_rule:{id}
) to get the ID of the entry inside the rule. That works fine if the entry field is on the top level, but I getNULL
instead of the entry ID if the field is part of a replicator or grid.I created a PR to fix the issue #10255
How to reproduce
Add an entries field to a replicator or grid with a custom validation rule, and notice that instead of the ID we get a
NULL
.Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Additional details
No response
The text was updated successfully, but these errors were encountered: