.svg?format=pjpg&auto=webp){kind=logo}
.svg?format=pjpg&auto=webp)
.svg?format=pjpg&auto=webp)
.svg?format=pjpg&auto=webp)
.svg?format=pjpg&auto=webp)
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
.svg?format=pjpg&auto=webp){kind=icon}
Limitations for Entry Variants
- The Entry Variants feature is currently available as part of an Early Access Program and may not be available to all users. For more information, you can reach out to our support team.
- Deleted entry variants cannot be restored from the Trash.
- Variant groups, variants, and entry variants are only supported on the main branch. When you create a new branch, the entry variants, variant groups, and variants will not be cloned.
- API requests do not support custom queries for entry variants. Subqueries (?query) with query operators only match data from the base entry, not variant-specific data.
- A maximum of 3 entry variants can be merged with the base entry when fetching personalized content from the CDN.
Was this article helpful?
More articles in "More about Entry Variants"
