Different value for Content picker and custom Content picker problem
I am using examine search and the content I'm searching for has a property of type Content Picker.
When the property is of type of built-in Content picker then the value written to the database is the picked content id.
When the property is of type derived from Content picker - for example I created a custom picker to start from another node - then the value written to the database is the reference to the key:
I am using examine search to find nodes by content picker value and this is causing a big problem because neither I can look by content id or the key, eg. searching for a string $"umb://document/{key}" does not find anything.
Can anyone explain why built-in Content picker and and custom Content picker behaves differently in this case? They still pick the same type of nodes don't they?
Different value for Content picker and custom Content picker problem
I am using examine search and the content I'm searching for has a property of type Content Picker.
When the property is of type of built-in Content picker then the value written to the database is the picked content id.
When the property is of type derived from Content picker - for example I created a custom picker to start from another node - then the value written to the database is the reference to the key:
I am using examine search to find nodes by content picker value and this is causing a big problem because neither I can look by content id or the key, eg. searching for a string
$"umb://document/{key}"does not find anything.Can anyone explain why built-in Content picker and and custom Content picker behaves differently in this case? They still pick the same type of nodes don't they?
is working on a reply...