Hello,
Since 6.2, it seems i have troubles with Web framework views timerange preset being ignored.
The Time Range does not load the preset timerange in 6.2, same views in 6.1.4 (or previous) have no issue and will load the preset time range:
The page always modules always loads to "All time" instead of what is being preset in the view:
The following code for example works with in no issue in 6.x but not 6.2: (django tags)
<tr>
<td>
<p></p>
<h2>TimeRange:</h2>
</td>
<td>
<p></p>
{% timerange id="example-timerange"
managerid="example-search"
preset="Last 30 days"
earliest_time="$earlyval$"|token_safe
latest_time="$lateval$"|token_safe %}
<p></p>
</td>
</tr>
Or:
{% timerange id="timerange"
managerid="search1"
preset="Last 24 hours"
earliest_time="$earlyval$"|token_safe
latest_time="$lateval$"|token_safe %}
Won't load the preset time range anymore.
In 6.2:
With SPlunk prior to 6.2: (ex 6.1.4)
The same issue occurs on every Web framework views, i couldn't find something related in the head logs.
According to the documentation, the code should be fine. (moreover than it works with official releases)
Example (Django tag)
{% block content %}
{% timerange id="example-timerange"
managerid="example-search"
preset="Today"
earliest_time="$earlyval$"|token_safe
latest_time="$lateval$"|token_safe %}
{% endblock content %}
Perhaps am i missing something, but i can confirm my views works as it is with any version but 6.2.
I have tested this with migrated and fresh installations with the same behavior.
Thank for your answer.
