Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

  • Geoff Beaumont 75 posts 103 karma points
    Mar 01, 2016 @ 12:32
    Geoff Beaumont

    Getting WhereListIterator<IPublishedContent> instead of Picker from property value

    In the project I'm currently working on I have a field which is using a nuPickers Lucene PrefetchList Picker, saving as CSV and linked to a one way relationship.

    Intermittently (I'd guess at around 20% of the time), I'm getting a System.Linq.Enumerable.WhereListIterator

    Obviously, when this happens attempting to return the value as a Picker returns null.

    My initial theory was that there was another property value converter that matched the property, and this was sometimes getting loaded into the PropertyValueConvertersResolver ahead of the nuPickers one. However, I can't find a converter that would match.

    It's also worth noting that when I'm getting the WhereListIterator from this property, another property which should return an SEOChecker.MVC.MetaData object is also throwing an error - however, this behaves slightly differently, throwing a null reference error which suggests it's attempting to convert the value and getting invalid input. That makes me wonder if the nuPickers converter is running, but that it's also getting input which has already been converted by something else and is just handling it more gracefully than the SEOChecker one (arguably, actually falling over with an exception is more useful in this case, though).

    So...I'm thinking this is most likely not as such a nuPickers issue, but something else messing with the property value - but I'm hoping someone on here may have seen something similar?

    Oh, this site is on Umbraco 7.3.4.

  • Geoff Beaumont 75 posts 103 karma points
    Mar 03, 2016 @ 10:36
    Geoff Beaumont

    Just a follow up; after getting no-where trying to track down the cause of this issue I tried upgrading Umbraco to 7.3.8. Bit of a stab in the dark as I couldn't see anything on the change logs that looked relevant, but since the upgrade the issue seems to have disappeared.

Please Sign in or register to post replies

Write your reply to: