Uh oh!
There was an error while loading. Please reload this page.
Migrate nuPickers to v8 - #199
Conversation
bowserm
commented
Nov 7, 2019
Any chance we could change the I forked off of your Thanks for all the hard work on this! |
bielu
commented
Nov 7, 2019
I will look at that's tomorrow morning 😜 |
bielu
commented
Nov 8, 2019
@bowserm changed :) |
joepvtl
commented
Jan 8, 2020
Hey @bielu , the saveFormat of the EnumPrefetchListPicker isn't getting saved. This is because the value is not being assigned. -Joep |
bielu
commented
Jan 8, 2020
@joepvtl I will look into that tomorrow morning :) |
bowserm
commented
Jan 16, 2020
I am seeing what I believe is the saveFormat error on the EnumRadioButtonPicker. When I look in the DB, this is what I am seeing as the prevalues for my datatype when I selected csv as the saveFormat: I'll race you to a fix blielu :). I'll see if the same problem is happening to other editors. |
bowserm
commented
Jan 16, 2020
@bielu I made a PR to the |
Ensure that saveFormat is saved as a string for every property editor
bielu
commented
Jan 17, 2020
@bowserm thanks for the help, I reviewed that and merged code. |
PezCo
commented
Jan 27, 2020
Is this Likely to be the definitive upgrade path for nuPickers? im a bit confused between this and https://github.com/uComponents/Pikachu which says its a v8 rebuild. is there any "official" word on plans for v8 its almost a year old now. |
bielu
commented
Jan 28, 2020
ronaldbarendse
commented
Jan 28, 2020
If you need an alternative to nuPickers for Umbraco 8, you might also be interested in Data List from @leekelleher: https://github.com/leekelleher/umbraco-contentment/blob/master/docs/editors/data-list.md. |
PezCo
commented
Jan 28, 2020
Ideally i want this branch. |
…n render macro by injecting UmbracoComponentRenderer
upgraded to latest version of Umbraco + fixed issue with null check o…
Great work. I have made my own build of your branch to use on an Umbraco V8 installation (v. 8.6.1). But i ran into some problems with PanicExceptions getting thrown in PickerPropertyValueConverter when it tries to access the parent property. My workaround was to surround the failing code with a try/cacth and ignore the PanicException. It solves it in my case, but i have yet to discover if it has any sideeffects. |
bielu
commented
Jun 5, 2020
@jesperbrasmussen can you add which version of v8 are you using? and I will look into that issue when I will have time |
jesperbrasmussen
commented
Jun 5, 2020
Yes it's v. 8.6.1 |
bielu
commented
Jun 5, 2020
@jesperbrasmussen can you also paste exception log as maybe I will be find out that just by exception as I check Umbraco source code and not much change here about ConvertIntermediateToObject and I will need to recreate but would prefer be sure it is same exception if I will cause any :) |
jesperbrasmussen
commented
Jun 8, 2020
I have just tested it on the lastest version of Umbraco which is v8.6.2, and I still get get the same error. This is the first part of the exception: |
bielu
commented
Jun 8, 2020
@jesperbrasmussen thanks that error log is helpful! Will look over weekend how to fix that issue! :) |
bielu
commented
Jun 20, 2020
@jesperbrasmussen I tried on clear umbraco 8.6.2 today and can't reproduce that issue, |
jesperbrasmussen
commented
Jun 22, 2020
Ok. I'll try to find time to do a test on a clean umbraco 8.6.2, and see if i can find a way to reproduce the error |
When a nuPicker is added to a custum MemberType and an instcance of that membertype is loaded through use of the memberservice i.e. Umbraco.Web.Composing.Current.UmbracoHelper.Member(id), the PickerPropertyValueConverter throws an error on line: 117. The check assignedContentItem.Parent != null appears not to be a valid check for IMember eventhough it's successfully cast to IPublishedContent, the fix works around the check by getting the parent id from the Path property.
Fixed issue for nuPickers added to Membertypes
It is an initial version for v8, few things have to be still polished, but works! I am happy to continue to work on UI changes and/code optimizations. I think it is ready to be published as prerelease and check with other Umbraco developers if everything is working as intended