Re: [Simple XML] Token not substituted within href...

punkle · ‎11-25-2013

I defined the following HTML element within one row of my dashboard (which is called with the GET parameter '?tsmserver=TSM512'):

  <html>
   <h2>Other Server Information</h2> 
   <ul>
    <li><h3><a href="DR-9-1?tsmserver=$tsmserver$">$tsmserver$ Data Stats</a></h3></li>
   </ul>
  </html>

However only the second occurrence of the $tsmserver$ token gets substituted with "TSM512" while the first one (the one within the href attribute) does not, therefore making the link unusable. Is this a bug or is this done on purpose? In case it is done on purpose, how can I put a link (containing a URL variable) within an html element in simple XML?

Thank you very much for your help,

Dan

guilmxm · ‎10-30-2014

Hi,

I confirm for having tested it that is has been definitively solved with the 6.2 version.
Same not working simple xml interfaces works now as expected, tokens are subsituded with success.

Great new!

Guilhem

SreeragM · ‎06-11-2015

Hi,

'&' character inside html href is still causing issue in my dashboards. is there a workaround of this?
I'm trying to add html link to another form at the botton of a table.

dfoster_splunk · ‎11-26-2013

Thanks for reporting this. It does actually look like a bug, as all $token$ values inside an <html> block are supposed to be replaceable.

For the moment it appears that token values inside elements like <a href="$token$"> will not work, although tokens outside of elements like <a>$token</a> will work.

I don't think you can work around this using Simple XML. If you upgrade your Simple XML dashboard to an HTML dashboard using Edit > Convert to HTML, you can modify the resultant HTML so that the %24 values in the <a href="DR-9-1?tsmserver=%24tsmserver%24"> are replaced with $ correctly.

Note that HTML dashboards can no longer be modified with the visual dashboard editor.

dfoster_splunk · ‎05-09-2014

It looks like this item was pushed out of Splunk 6.1, as you observe. -- You might ask your support contact about the issue, which shows up internally as SPL-77044.

alexiri · ‎10-24-2014

I've just been told that this is solved in version 6.2, we'll see if it's true in a few days.

alexiri · ‎05-09-2014

This is still not fixed in 6.1, and I don't see it listed in the release notes' known issues page[1]. Is there any update on this?

[1] http://docs.splunk.com/Documentation/Splunk/6.1/ReleaseNotes/KnownIssues

dfoster_splunk · ‎02-07-2014

The bug is still open. Based on its prioritization it is unlikely to get fixed in the Splunk 6.0.x timeframe.

ErikRothman · ‎02-07-2014

Any updates on this? Is the bug resolved yet? Seems like it still doesn't work in the latest version:

Splunk Version
6.0.1
Splunk Build
189883

dfoster_splunk · ‎12-02-2013

This bug has already been opened and prioritized, so you shouldn't need to do anything else.

alexiri · ‎11-28-2013

Hello @dfoster_splunk,

Has this already been opened as a bug internally, or should we report it through our support contract?

Cheers,
Alex

[Simple XML] Token not substituted within href attribute

.conf24 | Registration Open!

ICYMI - Check out the latest releases of Splunk Edge Processor

Introducing the 2024 SplunkTrust!