Multi Url Picker - Content Node selections


If I have a Multi Url Picker and pick items using the CMS content picker, then save+publish one of these picked content items with a new url, then this doesn't trigger the Multi Url Picker items to have their Urls updated.

has this been reported before?



shearer3000 wrote Apr 9, 2013 at 6:48 AM

(btw I'm using ucomponents 5.4 and Umbraco 4.9.1)

leekelleher wrote Apr 9, 2013 at 11:47 AM

Hi Andrew, thanks for reporting this.

There is a pull-request that resolves this - just waiting on @diachedelic to approve it :-)

shearer3000 wrote May 21, 2013 at 12:35 AM

hi guys - was this pull-request approved yet? thanks

leekelleher wrote May 21, 2013 at 9:15 AM

@shearer3000 - Yes, the pull request has been merged in. We'll put out a v5.4.2 release very soon (aiming for the end of this week)

leekelleher wrote Jun 5, 2013 at 11:28 AM

Pull request merged in. Fix implemented, due in uComponents v5.4.2

** Closed by leekelleher 06/05/2013 3:28AM

shearer3000 wrote Jun 26, 2013 at 12:59 AM

this doesn't appear to be fixed in

shearer3000 wrote Jun 26, 2013 at 1:22 AM

My test case:

Create a “homepage” doctype that has a ‘multi Url picker’ (in this case for determining menu hyperlinks that are displayed on the homepage.)
  1. Add an item to the multi url picker of type “content” i.e. another umbraco node.
  2. Note the “Url” element stored in the umbraco.config file for the multi url picker.
  3. Change the url of the umbraco node picked in the multi url picker and ‘Save & publish’
Expected: the “Url” element within the ‘multi Url picker’ structure stored in the umbraco.config has been updated with the new umbraco node url.

Actual: no change.

leekelleher wrote Jun 26, 2013 at 9:07 AM

@shearer3000 - how do you propose this issue could be fixed?

shearer3000 wrote Jun 26, 2013 at 9:46 AM

Hi Lee
I think the problem was that we were using our own library to provide umbraco.config ‘multi url picker’ data back to our app. I’ve updated this to use the uComponents extnesions for this datatype instead.

Maybe this is a non-issue and can be closed again, but one small improvement I would still recommend is that the ‘url’ property isn’t saved by the datatype when the mode is ‘Content’ because as per the changeset that resolved this issue the Url is always obtained on the fly from the corresponding Node, not the umbraco.config file any longer.

diachedelic wrote Jun 26, 2013 at 11:48 AM

The problem is, for this datatype to work with the utmost simplicity (not robustness...) it must always return a URL. This applies to people using XSLT, Razor and whatever other renderers there are. We have a fix for this issue which applies to people using modelbinding with Razor, but we haven't been able to think of a fix for other renderers.


shearer3000 wrote Nov 13, 2013 at 11:29 PM

@shearer3000 - how do you propose this issue could be fixed?
my first thought was that you'd have to traverse the umbraco cache file (umbraco.confg) and update the media values stored against multi url picker datatypes. Is that possible?

diachedelic wrote Nov 19, 2013 at 1:07 PM

Yeah but it would have to check every single url picker property field on every node when any node is published...I dunno how practical that is