Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect "field with the handle already exists" error on saving fieldset #9724

Closed
bastihilger opened this issue Mar 13, 2024 · 3 comments
Closed

Comments

@bastihilger
Copy link
Contributor

Bug description

I edited a field in a fieldset and could not save the changes (see "How to reproduce").

How to reproduce

Install a new statamic site (at least 4.53.0) with "statamic new"

Create a Fieldset "Foo" (handle "foo") with a Field "Bar" (handle "bar")

CleanShot 2024-03-13 at 10 38 13@2x

Reload the CMS (important, otherwise the error will not yet show up).

Click the field to edit it and then click "apply".

The error "A field with a handle of foo already exists." will show up.

CleanShot 2024-03-13 at 10 39 07@2x

This does not happen in v4.52.

Logs

No response

Environment

Environment
Application Name: Statamic
Laravel Version: 10.48.2
PHP Version: 8.3.3
Composer Version: 2.7.1
Environment: local
Debug Mode: ENABLED
URL: prove-error.test
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

Statamic
Addons: 0
Antlers: runtime
Sites: 1
Stache Watcher: Enabled
Static Caching: Disabled
Version: 4.53.1 Solo

Installation

Fresh statamic/statamic site via CLI

Antlers Parser

None

Additional details

No response

@bastihilger
Copy link
Contributor Author

Looking throught the updates I guess it was introduced here #9337

@duncanmcclean
Copy link
Member

Duplicate of #9716. Fix will be included in the next release.

@bastihilger
Copy link
Contributor Author

I did search the issues for "handle" - but I left the filter "is:open" on, so I did not find the duplicate, as it was already closed. I'm no pro at Github workflows, so this might make no sense, but maybe an issue should only be closed when the fix is released? You might of course have your reasons to do this otherwise.
¯_(ツ)_/¯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants