cms
cms copied to clipboard
Error when searching in the Link a single field box
Bug description
Only on this one site I have in current development, whenever I search in the Link a single field search box the application crashes, I lose all interactivity and have to reload the page. I can scroll to an item and select it, stuff just breaks whenever I start searching.
How to reproduce
I couldn't reproduce this on another updated website so it must be due to my specific collection of fields and fieldsets for this project. I'm happy to invite you to the repo privately for further investigation.
Logs
No response
Environment
Environment
Laravel Version: 10.40.0
PHP Version: 8.3.0
Composer Version: 2.5.5
Environment: local
Debug Mode: ENABLED
Maintenance Mode: OFF
Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED
Drivers
Broadcasting: log
Cache: statamic
Database: mysql
Logs: stack / single
Mail: smtp
Queue: sync
Session: file
Locales
Installed
LaravelLang\Actions\Plugin: 1.4.1
LaravelLang\Attributes\Plugin: 2.9.1
LaravelLang\HttpStatuses\Plugin: 3.8.0
LaravelLang\Lang\Plugin: 13.12.0
Locales Version: 1.9.0
Protected
Publisher Version: 15.0.2
Livewire
Livewire: v3.3.5
Statamic
Addons: 7
Antlers: runtime
Stache Watcher: Enabled
Static Caching: Disabled
Version: 4.42.1 PRO
Statamic Addons
jacksleight/statamic-bard-mutator: 2.3.0
jonassiewertsen/statamic-livewire: 3.0.0
rias/statamic-color-swatches: 2.2.0
studio1902/statamic-peak-browser-appearance: 3.3.4
studio1902/statamic-peak-commands: 4.0.0
studio1902/statamic-peak-seo: 8.0.0
studio1902/statamic-peak-tools: 4.2.0
Installation
Starter Kit using via CLI
Antlers Parser
Runtime (default)
Additional details
No response
Looks like it's being caused by two fields with the same handle in a fieldset. There should probably be a validation rule introduced to validate against this.
Yeah whoops, trashing/renaming the field with the duplicate handle in one of the fieldsets solves the issue. Thanks Duncan. And I would agree, this should probably be prevented.
Want me to open a new issue for this?
We can keep this one open.
Cool