Not sure this has been asked yet. What are the implications of adding something like {$item.profile_display_name} to the core?
What I did was labelled {$profile_name} as the "Profile URL" (which it is) in the form designer.
and then created {$profile_display_name} labelled as "Profile Display Name" so that artists can have a different profile display name, than their URL.
Example:
{$profile_display_name} = DJ Some Kinda Guy
while {$profile_name} = djsomekindaguy resulting in URL of www.domain.com/djsomekindaguy
instead of www.domain.com/dj-some-kinda-guy
Then discovered (for instance) in Breadcrumbs, when on an item_detail.tpl page {$item.profile_display_name} can't be used.
Is there a way to pass the profile ID on an item_detail.tpl so that I can use a custom field such as {$profile_display_name}?
In JR4, there used to be a feature to "Allow user to change URL" IIRC.
Is it still considered a bad Idea to allow the user to change their profile URL? With the ability to change {$profile_name} in Account Settings, I'm assuming no.
Hope that makes sense.
updated by @ilovehousemusic: 04/20/14 12:26:49PM
JAMROOM
