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
{{ message }}
This repository has been archived by the owner on Oct 20, 2023. It is now read-only.
Desired: The ability to not duplicate certain fields.
Usecase: We're using Uuid to generate human readable entry ID's for a field called archive_uuid. These supplement the {s} id and are used as a segment in the slug. When an entry is duplicated, I'd like a config option to not duplicate this field as Uuid will generate a new/unique value. As it's used in the URL, the entry won't save again after duplication with an error on slug field: This URI has already been taken. This is not entirely true as the slug is not actually used, but rather that the archive_uuid value is not unique. The archive_uuid field is used across three collections and I have wondered while writing this if this extra config would need to be collection/taxonomy specific.
Is there a workaround you can use in the meantime?
In the meantime, I've set the archive_uuid field to be read_only: false but ideally this would be set to read_only: true to ensure authors do not tamper with it.
With this workaround authors can: duplicate an entry > clear the archive_uuid field > save the entry > Uuid will generate a new value.
Priority wise - where's this feature for you?
Nice to have
The text was updated successfully, but these errors were encountered:
What would you like to see added?
Desired: The ability to not duplicate certain fields.
Usecase: We're using Uuid to generate human readable entry ID's for a field called
archive_uuid
. These supplement the {s}id
and are used as a segment in theslug
. When an entry is duplicated, I'd like a config option to not duplicate this field as Uuid will generate a new/unique value. As it's used in the URL, the entry won't save again after duplication with an error on slug field:This URI has already been taken.
This is not entirely true as theslug
is not actually used, but rather that thearchive_uuid
value is not unique. Thearchive_uuid
field is used across three collections and I have wondered while writing this if this extra config would need to be collection/taxonomy specific.Is there a workaround you can use in the meantime?
In the meantime, I've set the
archive_uuid
field to beread_only: false
but ideally this would be set toread_only: true
to ensure authors do not tamper with it.With this workaround authors can: duplicate an entry > clear the
archive_uuid
field > save the entry > Uuid will generate a new value.Priority wise - where's this feature for you?
Nice to have
The text was updated successfully, but these errors were encountered: