The dashlets don't seem to refresh unless you manually refresh the whole Dashboard page? Is this by design? It's a bit of a problem as agents don't necessarily get to see new tickets immediately.
I'm aware of the Cache TTL setting for each dashlet, but that just affects whether or not they display the latest or cached content after a refresh.
I suppose I can put in an http refresh in a custom version of the page, but this feels like a bit of a hack?
[SOLVED] Dashboard/Dashlet refresh?
Moderator: crythias
[SOLVED] Dashboard/Dashlet refresh?
Last edited by Mothra on 11 Jan 2011, 13:54, edited 2 times in total.
OTRS 3.2.11 on Centos 6.4 with MySQL 5.0. Agents and internal customers authenticate via Active Directory.
Re: Dashboard/Dashlet refresh?
EDIT: Ignore the above, I was being stupid. When I looked in the source for the page, I found that there is already an HTTP-EQUIV refresh, set to 1800 (30 minutes).
I haven't yet found where/how this is calculated and whether or not I can override it to something shorter. If anyone can enlighten me, I'd be most grateful. I think it's something to do with Framework -> Frontend::Agent::ModuleMetaHead but, unfortunately, there's no documentation telling me how to configure this.
As a workaround, it is simplest to copy HTMLHead.dtl from the Standard theme and set the http-equive refresh manually in there (replacing $QData{'Refresh'} with the desired value).
I haven't yet found where/how this is calculated and whether or not I can override it to something shorter. If anyone can enlighten me, I'd be most grateful. I think it's something to do with Framework -> Frontend::Agent::ModuleMetaHead but, unfortunately, there's no documentation telling me how to configure this.
As a workaround, it is simplest to copy HTMLHead.dtl from the Standard theme and set the http-equive refresh manually in there (replacing $QData{'Refresh'} with the desired value).
OTRS 3.2.11 on Centos 6.4 with MySQL 5.0. Agents and internal customers authenticate via Active Directory.
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: [SOLVED] Dashboard/Dashlet refresh?
I've more or less come to the same conclusion as you. There's a
Looks like we may need Time Object (from MetaHttpEquivRefresh)
After that ... I know that HTMLHead is called from
Output/HTML/Standard/Header.dtl:$Include{"HTMLHead"}
The rest is not so easy.
Code: Select all
<!-- dtl:block:MetaHttpEquivRefresh -->
<meta http-equiv="refresh" content="$QData{"Refresh"}" />
<!-- dtl:block:MetaHttpEquivRefresh -->
Code: Select all
for (qw(ConfigObject LogObject LayoutObject TimeObject)) {
$Self->{$_} = $Param{$_} || die "Got no $_!";
}
Output/HTML/Standard/Header.dtl:$Include{"HTMLHead"}
The rest is not so easy.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
-
- Znuny newbie
- Posts: 15
- Joined: 25 Dec 2010, 03:11
- Znuny Version: 2.4.7
- Location: Europe/Kiev
Re: [SOLVED] Dashboard/Dashlet refresh?
I failed doing complex way to allow controlling it from sysconfig and just did a workaround. Simple and fast. Thank you.Mothra wrote:As a workaround, it is simplest to copy HTMLHead.dtl from the Standard theme and set the http-equive refresh manually in there (replacing $QData{'Refresh'} with the desired value).
OTRS 3.0.11 (RPM) + ITSM with PostgreSQL 8.1 on Centos 5.7 x86_64 on both production and testing machines.