1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

RM 1.1 Custom Fields Display HTML Markup

Discussion in 'Resource Manager Support' started by MRaburn, Nov 7, 2013.

  1. MRaburn

    MRaburn Active Member

    I cant seem to get this to work. I created a custom field. Chose TEXT and inserted HTML markup in the Value Display so it would display an image from the URL that I paste into the field.

    I am wanting to create URLs and Image call with the custom fields, URL and Image both Hex like example below.

    Using: <img src="{$valueUrl}"> or <img src="{$value}">

    This will not work because Xen is replacing all the url structure with hex...


    Any suggestions?

  2. Donnie La Curan

    Donnie La Curan Active Member

    It looks like {$value} gets converted into a link automatically if the value is a URL and {$valueURL} gets encoded so it can be used in a URL. I'm assuming that {$valueURL} is acting properly and {$value} is not. Why would {$value} just automatically be converted to a link if it's a URL? It should just be the value right?

    http://www.google.com is the value in the field.
    Value Display HTML: <a href="{$value}">Link</a>
    Expected: <a href="http://www.google.com">Link</a>
    Actual: <a href="&lt;a href=" http:="" www.google.com" rel="nofollow" class="externalLink" target="_blank">http://www.google.com</a>">Link</a>
    Last edited: Nov 7, 2013
  3. Jeremy

    Jeremy Well-Known Member

    Converting it to a link is the designed behavior. It came up during beta testing.
  4. MRaburn

    MRaburn Active Member

    Then is it possible to use it the URL with markup by using $valueUrl. Currently its converting it with Hex.

    In the custom fields options, there is a check value to make sure input was a URL. Would be nice to use that variable URL in markup for image calls, or href links.
  5. Donnie La Curan

    Donnie La Curan Active Member

    That doesn't make sense to me, but if that's the way it's supposed to be then I guess would it be possible to have a {$valueRaw} where I actually get the value back that is put in, untouched.
    CallieJo likes this.

Share This Page