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
When creating a entry within a structured collection, it is automatically added to the correspondig tree YAML file.
When duplicating an entry within a structured collection, it is not automatically added to the correspondig tree YAML file.
This only seems to happen when the parent entry is the root entry of the structure.
While it may look like the duplicated entry is part of the tree (it shows up in the admin tree UI and shows the root entry as it's parent field value), it is not actually stored within the tree YAML file.
This causes an issue where the parent cannot be updated by unlinking the root entry and linking a different entry.
How to reproduce
Setup a project with Statamic
Create a structured collection "test"
Create a blueprint for the collection with title & parent fields
Create a root entry "root"
Create an entry "new parent"
Create an entry "duplication source"
Duplicate the "duplication source" entry (rename it "duplication target").
Notice how this entry is not present in content/trees/collections/test.yml
The text was updated successfully, but these errors were encountered:
Boefjim
changed the title
Duplicated entries do not get added to tree
Duplicated entries do not get added to tree file
Jan 7, 2025
Boefjim
changed the title
Duplicated entries do not get added to tree file
Duplicated entries do not get added to tree file when parent is root
Jan 7, 2025
Boefjim
changed the title
Duplicated entries do not get added to tree file when parent is root
Duplicated entries do not get appended to tree file when parent is root
Jan 7, 2025
Bug description
When creating a entry within a structured collection, it is automatically added to the correspondig tree YAML file.
When duplicating an entry within a structured collection, it is not automatically added to the correspondig tree YAML file.
This only seems to happen when the parent entry is the root entry of the structure.
While it may look like the duplicated entry is part of the tree (it shows up in the admin tree UI and shows the root entry as it's parent field value), it is not actually stored within the tree YAML file.
This causes an issue where the parent cannot be updated by unlinking the root entry and linking a different entry.
How to reproduce
content/trees/collections/test.yml
Logs
No response
Environment
Installation
Existing Laravel app
Additional details
No response
The text was updated successfully, but these errors were encountered: