We have moved to GitHub Issues
Created by Shannon Deminick 16 Apr 2018, 09:19:31 Updated by Robert Copilau 23 Apr 2018, 09:10:19
Is required for: U4-11128
Subtask of: U4-11114
We need to wire up the new APIs for the variant names into :
PR is here: https://github.com/umbraco/Umbraco-CMS/pull/2598
Out of scope: Wiring up the publish states in the language drop down menu when editing content, this will need to come after http://issues.umbraco.org/issue/U4-11250
EntityRepository.GetByQuerymethod when passing in the umbraco object type.
EntityRepository.Getmethod when passing in the umbraco object type.
This doesn't update the EntityRepository to be able to have this functionality for Paging! Paging with regards to this 1:M lookup will have it's own challenges if we need it. This doesn't update the UI to allow/disallow property types to be varied or not varied, this will be something else we need to cater for soon.
Hey @Shandem I get a "Variation CultureNeutral is invalid for property type x" error when I try to create a document.
I commented out the code that throws the error to allow me to test the rest and everything works fine, except for that error. I am guessing that is fine since the focus of this PR is variants names and the CP was there to show that the language dropdown works.
@robertcopilau did you "turn on varying by culture" on the new doc type you created? (I'll re-test)
Yes @Shandem, I made sure it was on.
Moving to fixed as the base functionality works, the error above was due to the X property not having "varying by culture" on as the UI option for it is not currently present.
@Shandem did I understand the above correctly?
Backwards Compatible: True
Affected versions: 8.0.0
Due in version: 8.0.0
Sprint: Sprint 83
Story Points: 1