Hi Trish,

This is most likely due to the XPath used to select the items - you can only lookup published content in XML; but, you can use a couple of variables to be able to circumvent this behavior.

What does your XPath look like?

/Chriztian

Hi Chriztian,

Thanks for the very quick reply!

This is one of the XPaths

$ancestorOrSelf/ancestor-or-self::Homepage/Configuration/StaffSpecialismList/StaffSpecialism[@isDoc]

Thanks, Trish

Hi Trish,

Can you post your configuration XPath, and example tree ?

The Xml data-source (defaults) to using the Umbraco cached XML data of published content, so if the XPath query uses the current unpublished page, then it won't yet be in cache.

However, you can use the $ancestorOrSelf token to find the nearest published node - or you could swap to a different data-source such as the Lucene CheckBox Picker, as the Lucene index can contain details of unpublished Pages.

HTH, Hendy

Our Xpath (given by trish above), works fine on new pages before they are published, and the xpath uses $ancestorOrSelf to get to the homepage which is published (as are the other pages mentioned in the xpath).

If we were to try a different picker e.g. the LucenePicker, is the data stored in the db differently i.e. would our client have to update their pages everywhere this is used?

Thanks very much for your help!!

Hi Jonny,

Not sure I understand - if the XPath is working fine on pages before they are published, then all's good right ?

The Lucene pickers use Lucene as their data-source instead of the Umbraco XML cache. I think the default Lucene indexes created by Umbraco contain all nodes whether they are published or not.

Thanks, Hendy

When you create a page the checkboxes appear, but as soon as you save the page for the first time (& don't publish it), then the checkboxes dissappear and you can no longer set any values.

If you create a new page & then do a "save and publish", then you can continue to use the checkboxes.

Thanks!

ooh, that shouldn't happen - hopefully it's something we can fix - any chance you could post a structure of your tree ?

Thanks, Hendy

Where 'en' is of doctype Homepage. The checkbox pickers are on the nodes underneath "Our People".

Oviously in the shots trish sent above, we had more entries in staff specialisms.

Thanks very much!

Hi,

I'm getting this behaviour as well. XML Dropdown NuPicker works when creating the page, ie the page is unpublished - (but the NuPicker is presenting options from published pages), once the page it is on is published the picker no longer works.

Hi, I think this is being caused by a saved (but not published) page having an id greater than 0, so when using the $ancestorOrSelf token, the picker is expecting to find this id in the cache (which it isn't) - should be an easy fix (for v.1.5.3)

https://github.com/uComponents/nuPickers/issues/123

Thanks, Hendy

Brilliant! Thanks very much Hendy :)

is working on a reply...